search

kangarko / ChatControl-Red

Issue tracker and documentation for the next generation ChatControl Red, the most advanced chat management plugin.
49 stars 23 forks source link

1.18.2: Chat Format Issue #1859

Closed Suinalk closed 2 years ago

Suinalk commented 2 years ago

Minecraft Version: 1.18.2 MySQL: true BungeeCord: false

Basically, I have a lot of ranks in "chat.yml" and the problem is that I need to go to luckperms and negate "Sender_Permission: rank.admin or rank.vip and so on" if I don't... It literally spams the whole chat. I have to like negate everything on every new rank I make which is a pain... Am I doing something wrong? debug.zip

Suinalk commented 2 years ago

image If I don't do that on myself... It would look like this... image

ElBananaa commented 2 years ago

Hey, This is most likely caused by the fact that you either have the * permission and/or because your rank inherits from all the other ranks. In both cases, negating the permissions of the previous ranks as you did will solve the issue.

TheIntolerant commented 2 years ago

You could also choose to manage prefixes/suffixes in LuckPerms itself instead of using a format file in chatcontrol to manage prefixes, for more info read prefix meta. That way you don't need to go thru this process of negating the permission nodes.

If you do opt to manage prefixes via LuckPerms and you have mutiple types of prefixes that a user should have, you may want to also read prefix/suffix stacking.

Suinalk commented 2 years ago

I feel like it gives more control when I do it in chatcontrol...

Suinalk commented 2 years ago

Omg so negating is something I'll have to do omagash

Suinalk commented 2 years ago

That's going to be annoying o man

Suinalk commented 2 years ago

Well I guess there is no other way around it so :I

TheIntolerant commented 2 years ago

While it is possible to make a workaround with the "sender_condition" this would require you have some knowledge with JavaScript to create a variable that works effectively for this particular case.

Otherwise, yes, negating each permission is the only way around this. Closing this issue since it's been resolved but feel free to comment below if you have any additional questions.