D
And why not?I'm not sure why the community should know this.
I just personally think its nice to know oh hey that's cool you work on skins or ah that's nice you build the maps ect.I'm not sure why the community should know this.
Ngl thats a good point.This would mean we need a different role for every design position, which is a lot.
Is this a real argument against the suggestion though? I suppose it'd be worth a little bit of time if it'd help people understand a designer's specific role on the team.This would mean we need a different role for every design position, which is a lot.
They can find the specific roles if they really need them, we dont need to complicate our forums rank system simply to explain something to players that they realistically do not need to know and they can find elsewhere.Is this a real argument against the suggestion though? I suppose it'd be worth a little bit of time if it'd help people understand a designer's specific role on the team.
There’s a difference between a completely separate rank and an indication for what they do (eg I don’t have QA or partner team rank because there’s no point in it) byt ges because people can contact me for helper applications stuff (plus it makes some perms stuff easier). There’s not really a reason for a community member to know who’s a builder or a skin artist as like they don’t directly work together with the community. Like story said, people can find out by checking a thread, we really don’t have to make our roles system more complicated.Then why would you have the Sr Moderator rank? Should we know you're a senior mod?