@Cooldown is incompatible with @Confirmation on the same command

[Galapen]

Versions used:

• Cloud core 2.0.0
• Cloud paper 2.0.0-beta.10
• Cloud annotations 2.0.0
• Cloud minecraft-extras 2.0.0-beta.10
• Cloud cooldown 1.0.0-rc.1
• Cloud confirmation 1.0.0-rc.1
• Cloud requirements 1.0.0-rc.1
• Paper 1.20.4 #499

@Confirmation and @Cooldown work correctly independently, but when applied to the same command, only @Confirmation works. It is reasonable to expect both to work in tandem because they serve different purposes. A command with a confirmation exists to ensure the player wants to execute it, and the cooldown ensures they do not spam the command.

If they were working together, I would assume that the cooldown would be checked first, and if it passed, the confirmation would be invoked and the cooldown started.

I have not tested the issue with these processors via the builder configurator, only with annotations.