pg=0 is the identifier for the leaderboards. Some leaderboards are disabled for this, and not all will work.

Moving on, let's cover the meaning of the json values from login and UID data, as some are not very straight forward.

"uid" - The Universal Identifier of a user. Used in profile links and leaderboard data.

"s_kills" - The number of kills the player has.

"s_deaths" - The number of deaths a player has.

"vector_kills" - Not completely understood yet.

"vector_deaths" - Not completely understood yet.

"xmpp" - The data in a players "XMPP" profile field.

"icq" - The data in a players "ICQ" profile field.

"skype" - The data in a players "Skype" profile field.

"web" - The data in a players "Website" profile field. When viewed on profile, it will be have the same HTML as a hyperlink.

"slogan" - The data in a players slogan profile field.

"nickname" - A players set nickname.

"login" - The players login name. They type this in the login field, and it is also in their profile link.

"mdl" - The user's deathmatch character. There is extra logic required, and this can be used to have a function returning a link to a players character for an avatar. (Will update later with logic.)

"mdl2" - The user's selected Team Deathmatch character value. Not sure where the character pictures for this are hosted, will update later.

"location" - The data in a player's location field. Player's choose this, and it may not be accurate to their real location.

"gender" - A player's gender, which will return usually male or female with some exceptions.

"clan" - A field for clans that was going to be used when/if a clan system is implemented. This shouldn't ever contain data as far as I am aware.

"birth" - The data in a player's birthdate field.

"register" - The player's register date stored as a unix timestamp. May conflict with real_register. Whichever of these is older, is the closest to the actual register date. Most players will be accurate, but there are some inconsistencies with older players.

"real_register" - The player's register date stored as a unix timestamp. May conflict with register. Whichever of these is older, is the closest to the actual register date. Most players will be accurate, but there are some inconsistencies with older players.

"superuser" - Unknown

"banned" - Will return 0 if the player is not banned, will return 1 if the player is banned.

"points" - Unknown

"rec_from" - Unknown

"rec_bf_from" - Unknown

"max_reached_place" - Not completely sure, but I believe this value is the highest rank you achieved in either the top 1000 or 200 players. When they haven't reached this yet, it just returns 1000.

"reached_when" - Will return 0 if the above value is 1000, and otherwise, a Unix timestamp of when the player reached the place in "max_reached_place"

"dev_rank" - A players Level Developer Rank.

"player_rank" - A players PPP.

"chat_admin" - A value used to tell if a player has admin powers on the PB2 chat. If 1, the player is an admin. Otherwise, they are not.

"chat_moderator" - A value used to tell if a player has a chat moderator rank on the PB2 chat. If 2, the player is a head moderator. If 1, the player is a player moderator.

"chat_owner" - Unknown

"multiplayer_moderator" - Used to tell whether or not a player has in game moderation powers. Trial staff and Supports will not have this, other staff will.

"country_code" - The user's country code. May be more accurate than the location field, as it seems this is calculated server side.

Hopefully planning to soon release some libraries to pull data easily and return values so people don't need to learn all this to do things with it.

Will update soon probably with a node js library with a lot of these values being used. Haven't experimented with the leaderboards much yet.