EssentialsX

EssentialsX

2M Downloads

Command cooldowns not persistent

Opened this issue ยท 0 comments

commented

Information

Full output of /ess version:

[08:50:57 INFO]: Server Version: 1.13.2-R0.1-SNAPSHOT git-Spigot-1a3504a-e7700ab (MC: 1.13.2)
[08:50:57 INFO]: EssentialsX Version: 2.17.1.0
[08:50:57 INFO]: LuckPerms Version: 4.0.80
[08:50:57 INFO]: Vault Version: 1.7.2-b107

Server log: https://gist.github.com/GummiBoat/3bed337305e18d7c876f5c736ae24a98

EssentialsX config: https://gist.github.com/GummiBoat/b19899553bc6f899aa7748f544952913

Details

Description
I have a requirement for a relatively long cooldown of 48 hours on the /nick command. The cooldown works just fine while the server is still running, however, seems to be ignored once the server has been restarted, or the config has been reloaded. I checked my userdata .yml and there is an entry with the nick command and a correct timestamp.

Steps to reproduce
1 - Set a command on a cooldown (in my case nick: 172800)
2 - Enable command persistence if not already applicable and reload
3 - Execute that command
4 - Execute it again to confirm that the cooldown works
5 - Restart the server
6 - Execute the command again, notice that the cooldown got ignored, but gets set again properly

Expected behavior
That the cooldown does persist through server restart with the respective option enabled