Type of bug
Other unexpected behaviour
/ess dump all output
https://essentialsx.net/dump?bytebin=787fK7IL5m
Error log (if applicable)
No response
Bug description
There is a minor typo/copy-paste error in the default config.yml for EssentialsChat around line 1006. The comment lists normal: as a format configuration key, but it should actually be local:.
Steps to reproduce
- Open the Essentials configuration file (config.yml).
- Scroll down to the EssentialsChat section (line 1006).
- Modify the local chat format string to any custom layout.
- Save the file, type /ess reload or restart the server.
- Send a message in the local chat in-game.
- Observe that the chat formatting completely ignores the config changes and stays default.
Expected behaviour
When changing line 1006 to customize the local chat formatting, EssentialsChat should recognize the configuration and apply the changes to the in-game local chat.
Actual behaviour
EssentialsChat ignores the changes made to line 1006. The local chat format remains completely default (as if no changes were made in the config file).
Additional Information
Here is the exact part of the config.yml where the issue occurs (around line 1006):
# normal: '{WORLDNAME} {DISPLAYNAME}&7:&r {MESSAGE}'
Even if changed, EssentialsChat completely ignores this format and keeps using the factory default style for local chat.
Type of bug
Other unexpected behaviour
/ess dump alloutputhttps://essentialsx.net/dump?bytebin=787fK7IL5m
Error log (if applicable)
No response
Bug description
There is a minor typo/copy-paste error in the default
config.ymlfor EssentialsChat around line 1006. The comment listsnormal:as a format configuration key, but it should actually belocal:.Steps to reproduce
Expected behaviour
When changing line 1006 to customize the local chat formatting, EssentialsChat should recognize the configuration and apply the changes to the in-game local chat.
Actual behaviour
EssentialsChat ignores the changes made to line 1006. The local chat format remains completely default (as if no changes were made in the config file).
Additional Information
Here is the exact part of the
config.ymlwhere the issue occurs (around line 1006):# normal: '{WORLDNAME} {DISPLAYNAME}&7:&r {MESSAGE}'Even if changed, EssentialsChat completely ignores this format and keeps using the factory default style for local chat.