Poseys and Prickleys cooldown incorrect
Open, Needs TriagePublic


What is happening:
When you cast P&P the cooldown indicator resets the spell but upon trying to use it you get "Spell is still on cooldown", sometimes for two or three more seconds.

What should be happening:
Once the spell icon indicator has become available to use again, you should be able to use it again.

Steps to reproduce the issue:

  1. Cast P&P
  2. Let it cooldown on your hotbar and become available to use again
  3. Attempt to use it and get the cooldown message
  4. Repeat

Game client version:
Filename: legends-of-equestria-legends-of-equestria-win-lar-64bit-33.zip
In-game version: 2020.05.01

Reproduced by:
Not sure. Only me as far as I know

Reproduced on:
Windows 7 Professional 64bit SP1

Crash logs or exceptions generated:
This does not crash the game

Will produce a video soon!

I forgot to upload the video. The link is below. Note that even after the hotbar indicates that the spell is ready, I cannot cast it for multiple seconds.


I noticed a larger bug last night. I was working on leveling up my magic skill by tanking two or three timberwolves in The Heartlands. All was well until a level 30 dragon popped through the terrain and nuked me. I respawned and returned to continue grinding and noticed that when I used Regenerative Aura my hotbar only showed a four-second cooldown! Using Poseys and Prickleys shows something like a 1.6 second cooldown. So fainting and respawning breaks SOMETHING with the hotbar. I will try to get a video of this today.

Here is a video showcasing the hotbar cooldown bug. I noticed today, while recording this video, that it affects ALL skills. For example, when I start fighting the timberwolf at the end and use combat skills, note how it only shows about half a second of cooldown. Note how Regenerative Aurua only shows about a four second cooldown after respawning as well. Maybe the cooldown issue isn't specifically with Poseys and Prickleys, but with all skills and spells? Actually, my gut tells me it is something with the hotbar, but I have no way to verify that.