Default player.communityname value

[xXziroXx]

When new accounts are made, their communityname variable equals to ""/NULL/0 (etc.) which breaks quite a lot of scripts. Example accounts: Graal750231, Graal750233

My request is that all accounts have their player.account as player.communityname UNTIL they chose a community name of their own. This would stop it from showing as ""

Pre-Graal###### accounts (such as xXziroXx) have their player.account match player.communityname, so that's no a problem.

[fowlplay4]

Indeed, but until then...

Workaround:

PHP Code:

function getName(obj) {
  return (obj.communityname ? obj.communityname : obj.account);
} 


[cbk1994]

Agreed, I think it's supposed to be like that anyhow. I tend to use this in player classes:

PHP Code:

public function niceName() {
  return ((this.communityname == null || this.communityname == "guest") ? this.account : this.communityname);
} 


[WhiteDragon]

The idea is that community name is actually suppose to be treated as a semi-permanent nickname. In order, it'd be account (permanent), community name (semi-permanent), nickname (mutable).

So, in my opinion (just thinking about this right now really), things should behave something like this:

• All data should be stored by account name, because you have the guarantee that it will never change.
• Important references to the player should be by community name (or the hybrids introduced in the last two posts), because you have the guarantee that it is unique at that specific point in time. e.g., "xyz said: whatever", or "xyz joined the CTF game".
• Any colloquial references to the player can be by nickname. e.g., "Congrats Big Fat Joe you just earned 30g for smashing the pumpkin head!"

Overall, community name was a bit stupid and probably should have not been introduced.