I’m obviously going to be biased here because I write Nucleus, but I’ll throw my tuppence in anyway.
I’d like to just see weighted options or meta, so that each option is given a weight and the highest weight wins in case multiple groups has the same option. I feel that chat plugins should control how it displays prefixes and what options it uses, so you shouldn’t worry about special treatment of prefix options, that should be left to the chat plugin in question, because if you throw your own handling in there, it could just make things more confusing for the server owner. Besides, I don’t think what you suggest would give the control a server owner would like.
The way Nucleus works to provide multiple prefixes/suffixes is to just allow any option to be a prefix or suffix. If you look under “Custom Prefixes” at http://nucleuspowered.org/docs/modules/chat.html, you should be able to see that Nucleus can display any option/meta as a prefix.
So, setting the Nucleus chat “prefix” to {{o:rank:s}}{{prefix}} {{displayname}}&f>:
would try to read both the “prefix” meta and the “rank” meta (ignore the o:
and :s
for now). If one of @Rasgnarok’s players (let’s pretend that it’s me, because why not?) was in the Mod group (with “prefix” meta set to [Mod]
) and the Builder group (with “rank” meta set to [Builder
]), I would expect Nucleus to output the following when I said “hi”:
[Builder] [Mod] dualspiral>: hi
In this case, no weighting would be needed.
If @Rasgnarok now has a BuilderPlus rank, with “rank” meta set to [Builder+]
, but for some reason doesn’t like inheritance, then what would be good is to be able to set a weighting to the meta/option too, where the highest weight wins. So, if the rank meta for Builder had a weight of 1, and BuilderPlus gave a weight of 2, then the result of getting the “rank” meta/option for a player with both groups would be [Builder+]
. Not sure what you’d do in the edge case of the same weights being assigned, but as long as it’s predicitable, that should be good enough.
When I originally asked for Support permission options other than prefix/suffix · Issue #23 · lucko/LuckPerms · GitHub it was to support chat and other things in Nucleus. It would be cool if you’d consider weighting options/meta, even outside of this use case, I think it would be incredibly useful for bother server owners and developers, who have to worry less about what the permissions plugin might return, which can be a headache sometimes!