So, currently, the way chat formatting is, you need to /permissify player setmain <player> <group> and with the integration of promotion/demotion ladders (#32) it should use the prefix/suffix of the highest grouping in that ladder.
example ladder:
administrator -- &a &f &f
moderator -- &a &f &f
user -- &5 &f &f
pleb -- &c &f &f
Format: GroupName -- [prefix] [suffix] [colour]
.
.
So like, let's say that a user get's defaulted to the pleb group, they would then get the chat format of [pleb] {username}: {message} (so it would auto-assign the "main" group as the pleb group) then let's say this pleb is not as plebish anymore so they get a promotion to user their chat prefix would then, automatically changing the "main" group, be changed to [user] {username}: {message} and then if the user was being plebish again and got a demotion, it would reset the chat format to [pleb] {username}: {message} and it would do that for all of the groups in the ladder system. (Although there would need to be a setmain for the ladders if there is more than one ladder (should only be required if there is more than one ladder in the database))
So, currently, the way chat formatting is, you need to
/permissify player setmain <player> <group>and with the integration of promotion/demotion ladders (#32) it should use the prefix/suffix of the highest grouping in that ladder.example ladder:
Format:
GroupName -- [prefix] [suffix] [colour].
.
So like, let's say that a user get's defaulted to the
plebgroup, they would then get the chat format of[pleb] {username}: {message}(so it would auto-assign the "main" group as the pleb group) then let's say this pleb is not as plebish anymore so they get a promotion tousertheir chat prefix would then, automatically changing the "main" group, be changed to[user] {username}: {message}and then if the user was being plebish again and got a demotion, it would reset the chat format to[pleb] {username}: {message}and it would do that for all of the groups in the ladder system. (Although there would need to be asetmainfor the ladders if there is more than one ladder (should only be required if there is more than one ladder in the database))