Main/core config guide
You can access the below settings in the config.yml file within the plugin's root folder.
Config excerpts taken from v4.4.0 and may not be completely up-to-date with the latest changes. To see the most up-to-date file, see below:
check-for-updates
Should ChatSentry notify operators (and players with the permission "chatsentry.admin") when new plugin updates are available?
Keeping this on is highly recommended as otherwise you won't be able to take advantage of new features and fixes as quickly!
check-for-updates: truebungeecord
Experimental: Using BungeeCord? ChatSentry offers various cross-server synchronization options below.
For information on how to set up the plugin to work with BungeeCord, see the guide here: https://wiki.chatsentry.xyz/bungeecord-bridge-setup-guide
The below settings are global and non-exclusive to this instance. Any changes made here will be applied to all other ChatSentry configs on your network.
bungeecord:
enable: false
sync-configs: true
sync-playerdata: true
global-admin-notifier-messages: trueprocess-commands
Should ChatSentry's modules filter commands as well as chat? Unless otherwise stated in their descriptions, modules require this option to be enabled in order to filter commands. Almost all modules support processing commands.
process-signs, process-anvils, process-books
Should ChatSentry's applicable modules filter through writing on signs, renaming items in anvils, and writing in books?
context-prediction
Context prediction aims to increase positive detections and decrease false positive detections through acting as a safenet for supported modules with sophisticated logic that dynamically adjusts thresholds and options real-time to react more precisely based on predicted context of messages. Adjustments are temporary & unique to messages; they do not permanently change any config options.
disable-vanilla-spam-kick
Should ChatSentry disable Minecraft's built in "Kicked for spamming" / "disconnect.spam" kick? There is no way to disable these kicks in the server configuration, however with a workaround ChatSentry can override it and prevent it from occurring. It's recommended to keep this enabled to give the auto punisher full punishment priority.
enable-violations-log
Should chat detections and violations be logged for future reference? This is required to be enabled in order to make use of the lookup command.
enable-logging-for
Below is which violations and detections are logged. Requires the above option to be enabled.
It's recommended you keep these as they are by default to prevent unnecessary detections being logged and taking up useless storage space.
override-bypass-permissions
You can disable the functionality of particular module and restrictions' bypass permissions and force modules to apply themselves to players even with bypass permissions or op by enabling the overrides below
It's recommended you do this per-player/group with permissions by simply negating/disabling the bypass permission for modules/restrictions you'd like to apply to them if they have the bypass all permission. However, this option is available as a hard override
This option is also useful for testing purposes if you don't want to have to deop yourself to test a module or restriction
enable-<module>
Below you can enable the modules you'd like to use. Go in to the modules config files in the modules folder to adjust their settings.
Last updated
Was this helpful?