Closed DontCallMeChicken closed 10 months ago
I have now found the cause: It is due to the “Toggle Command” effect. If this is activated, the cooldown does not work. As soon as I deactivate or delete the effect, the cooldown works. And only the first effect that activates the other command. The "Toggle Command" effect at the end of the effect list, which deactivates the other command again, does not prevent a cooldown.
Since this command is used to activate the other command for a certain time, but this doesn't work now, the whole thing doesn't work for me.
I also assume that this is not what the developers intended and therefore it is a bug.
@DontCallMeChicken
I have now found the cause: It is due to the “Toggle Command” effect. If this is activated, the cooldown does not work. As soon as I deactivate or delete the effect, the cooldown works. And only the first effect that activates the other command. The "Toggle Command" effect at the end of the effect list, which deactivates the other command again, does not prevent a cooldown.
Since this command is used to activate the other command for a certain time, but this doesn't work now, the whole thing doesn't work for me.
I also assume that this is not what the developers intended and therefore it is a bug.
what version of firebot?
@CKY-
what version of firebot?
Firebot v5.58.1 OS Ubuntu 20.04.6 LTS
This is an issue related to the way we currently refresh the command cache after modifying commands (including their enabled state). Folding this into #1947.
Help Request I don't know why, but with this command that I created with some effects, the cooldown function doesn't work. I can set whatever I want as a cooldown, the command can always be triggered. I don't know what to do now, so I'm turning to you, the nice development team.