Add "cooldown timer pools" where any command in that "pool" can only be run during the cooldown perion. For instance, if I have the following "Spawn Pool" set up for 10 minutes, I could create a bunch for spawn commands where people in chat can spawn zombies on me in my game (I currently have this set up for 7 Days to Die), but I only want one person to be able to run a spawn command every 10 minutes. I thought about creating a single command with a 10 minutes cooldown called (!10mincd), renaming my "!spawn_bear" command to "!xspawn_bear", then having new "!spawn_bear" command immediately run the "!10mincd !xspawn_bear" command as "user", and then have the "!10mincd" command set to run "@target@" as "user". I think this would work. Now, if we could just get a generic "time left on cooldown" message for commands on cooldown that say "You must wait 4 minutes before running this command..." or "You must wait 34 seconds before running this command..." when the users try to run a command currently on cooldown. Currently, when a user runs a command on cooldown, it just seems like the command doesn't work, so they run it multiple times. I have commands with 45 minutes cooldowns, and people that know about the cooldown will just run it every 5 minutes, hoping the cooldown is over. I would really like to see something simple added to allow cooldown times to be shown when people try to run a command on cooldown. I really don't want to have to add a complicated script to every single command with a cooldown, because a lot of those commands already run a complicated scripts, and it would get very difficult to troubleshoot problems with adding a script withing a script within a script.