You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[WARN] [Essentials] Command cooldown error: Unclosed group near index 14
^ban([^ip])?(
[WARN] [Essentials] Command cooldown error: 'MemorySection[path='command-cooldowns.^^ban([^ip])?( ', root='EssentialsConf']' is not a valid cooldown
[WARN] [Essentials] Command cooldown error: Unclosed group near index 14
^ban([^ip])?(
[WARN] [Essentials] Command cooldown error: 'MemorySection[path='command-cooldowns.^^ban([^ip])?( ', root='EssentialsConf']' is not a valid cooldown
EssentialsX config:
command-cooldowns:
'^^ban([^ip])?( .*)?': 30
Details
Description:
EssentialsX produces multiple errors when attempting to use the example regex in the Command Cooldowns documentation at https://github.com/EssentialsX/Essentials/wiki/Command-Cooldowns . Any similar regex also results in errors. I can't get any regex ending with ( .)? to work.
Steps to reproduce:
Enter the regex from the documentation for highly technical users, as shown in the above config file excerpt.
Expected behavior:
I expected that EssentialsX would work with the regex given in the official EssentialsX documentation. (It's almost like nobody ever tested this.)
The text was updated successfully, but these errors were encountered:
My whole reason for going down the regex path was to have a unified cooldown for command aliases, which I see is being handled by #2058. So feel free to close this, or keep it open to keep track of the general regex bug and documentation.
Information
Full output of
/ess version
:Server startup log:
EssentialsX config:
Details
Description:
EssentialsX produces multiple errors when attempting to use the example regex in the Command Cooldowns documentation at https://github.com/EssentialsX/Essentials/wiki/Command-Cooldowns . Any similar regex also results in errors. I can't get any regex ending with
( .)?
to work.Steps to reproduce:
Enter the regex from the documentation for highly technical users, as shown in the above config file excerpt.
Expected behavior:
I expected that EssentialsX would work with the regex given in the official EssentialsX documentation. (It's almost like nobody ever tested this.)
The text was updated successfully, but these errors were encountered: