"On retail pet had a gcd for receiving commands" - False imo

[Lelol]

Regarding your(itslovelol) statement in this thread which you also seem to have implemented: https://www.smolderforge.com/forums/vie ... f=9&t=9632
Got any source/proof of this?


What is the bug?
Pets have a GCD for every form of command, should only have GCD for actual pet spells.

What kind of bug is it? (Quest, Class, Spell, PvE)
Pet/Mechanic

How can you reproduce it?
Duel someone, stand right next to them, order felhunter to attack, now try to cast spell lock on the target, it won't work for another 1.5 seconds.

Please describe, in detail, what is suppose to occur when this bug happens:
Pets should only have a GCD on their actual spells. If the aggresive/defensive/passive & attack/follow/stay commands would have had a gcd on retail then they would most likely have a GCD animation to their icons, which they don't.

Please describe, in detail, what happens when it bugs up, and how it's malfunctioning:
There's a GCD added to every single pet command that shouldn't be there. This causes other issues such as if you put the pet on stay then switch it to follow and quickly back to stay again within 1,5 seconds. Then the stay icon will be highlighted but the pet will still be following you.

Evidence providing proof of bug:
I suspect that the reason you might have gotten this idea is because of the spell delay that existed on retail for all spells & commands. But since the spell delay doesn't exist on all other spells & abilities on this server it would be unfair to just apply it to pets imo.

[Ricekrispies]

I call bullshit on this one too. I did some digging at Wowhead and Wowwiki and nothing indicated that pet commands would have GCD.

[Itslovelol]

They had a small delay on retail, this was found out on some CC forum post which I can't find anymore. However I changed it to actualy have a 250ms delay on pet COMMANDS and 100ms delay on pet spells, both not counters for the other one. The main reason behind this is to make pet commands not spammable because it would recalculate movement each time you press so e.g. following.

I'll leave this open to see results.

[Itslovelol]

I think it's fine like this. Just reopen if you think it's still wrong.