Command cooldown not useful for tpr
Type of bug
Other unexpected behaviour
/ess dump all output
https://essentialsx.net/dump.html?bytebin=OJI20dcksD
Error log (if applicable)
No response
Bug description
When adding a cooldown to the command tpr, if the user moves/cancels it accidentally, they can no longer use the command
Some players aren't aware there are teleport delays, sothey are running the command and then moving This is causing frustration and players to leave as they can no longer use the command for 2 hours
Steps to reproduce
- Configure the
tprcommand - Configure
teleport-delayto5seconds - Configure command cooldown
command-cooldowns: tpr: 7200 # 2 hour cooldown on /tpr command - Use the command (without cooldown bypass)
- Move before it executes
- Try reusing the command (it does not work)
Expected behaviour
The cooldown for the command shouldn't be triggered unless the command is successful
Actual behaviour
The cooldown is applied, preventing re-use of the command even though they never teleported
Additional Information
No response
I've also had the same issue where players complained that they moved during the 3-second teleport delay, and it cancelled their random teleport - putting it on cooldown even though they did not teleport.
I agree with @No1InParticular that the cooldown should only apply if the teleport is successful.