MultiChat
Features and suggetions
- JSON support for global chat
- JSON HEX support
- Sentence first later capitalization and end periods
- Anti Caps
- Anti Link whitelist section
- Spy Commands
- Network join message cooldown with anti flood and it also should respect bans and mutes
- Regex actions should work like regex rules and actually check if the keyword is after irrelevant words
- Regex rules for books and signs
JSON support for global chat
This is planned, I can't say if this will be implemented in 1.10 or 2.0 yet
JSON HEX support
JSON supports HEX by default. "color":"#rrggbb"
Sentence first later capitalization and end periods
I know ChatManager offers this, but I hate enforcing rules like these on players. Is this really necessary?
Anti Caps Anti Link whitelist section
1.10
Spy Commands
These already exist partially (/socialspy and /group spy all), the local spy is implemented in 1.10.
Network join message cooldown with anti flood and it also should respect bans and mutes
Already respects bans. If it doesn't on your end, consider switching to a BungeeCord ban plugin that supports server scopes. (LiteBans does for example.) I don't think join messages are something a mute should prevent.
Regex actions should work like regex rules and actually check if the keyword is after irrelevant words
Agreed. 1.10
Regex rules for books and signs
Can be looked into, but can't promise anything yet.
In the future, please open one issue per request. Issues/Comments like these are really hard to work with in regards to a workflow. I will close this issue once 1.10 release.
Thank you for taking the time to write this and i am looking forward to future versions.
JSON HEX support
JSON supports HEX by default. "color":"#rrggbb"
JSON supports HEX that is true if you decide to just use one color code for everything , but it doesn't work with prefixes or display name placeholders that get its format from luckperms (maybe because it uses '&#' instead of the json '#'). So if I wanted to make hover/clickable events on usernames, I would have to make them all the same color or at least make sure no ranks or groups have HEX prefixes.
Sentence first later capitalization and end periods
I know ChatManager offers this, but I hate enforcing rules like these on players. Is this really necessary?
You are right, it's not really necessary even though I kind of like that format in sentences.
Network join message cooldown with anti flood and it also should respect bans and mutes
Already respects bans. If it doesn't on your end, consider switching to a BungeeCord ban plugin that supports server scopes. (LiteBans does for example.) I don't think join messages are something a mute should prevent.
Ah yes that makes sense, I am using litebans on all backend servers but not on bungee because the author said it's not recommended (I might be wrong). But even that won't help with players that spam leaving and joining the server.
In the future, please open one issue per request. Issues/Comments like these are really hard to work with in regards to a workflow. I will close this issue once 1.10 release.
I understand.