Skip to content

GitLab

Closed
Created by Dragon@DragonEye

[Bug] /md setcooldown does not work if you don't have a cooldown enabled in the dungeon config.

Greetings, I seem to be having an issue with the /md setcooldown command. It seems to not be placing the player on cooldown.

I have a dungeon timer mythicmob that spawns at the start of the dungeon and runs a command for everyone to put them on cooldown - command{c="md setcooldown Outpost <target.name> 4h"} @World ~onSpawn

And console says the cooldown was properly set

[15:02:47 INFO]: [Dungeons] Set DraakKin's cooldown for dungeon Outpost!
[15:02:47 INFO]: [Dungeons] Dungeon will unlock again at Tue, Aug 16, 06:02 PM EST

But it seems to have no effect and I can continue to play the dungeon. (Using dev build 48)

(Also the time seems a bit off? The command was run at 3:02 PM EST and it says it will unlock at 6:02 PM EST when the command specified 4h but the cooldown claims to be 3h. The unix timestamp in the dungeon player file is actually 4h by the looks of things.)

Update: I found out that the cooldown command only works if you have cooldowns enabled in the dungeon's config file.

Edited by Dragon