Tree of Savior Forum

[BUG] Overheat is broken on certain skills, and doesn't function properly

Date and Time : April 15, 2016

Game Control Mode (Keyboard/Joypad/Mouse) : Joypad

Where it happened (which map, which quest, which npc, etc) : All Maps

Bug Description :
Overheat is displaying incorrect charges while using Controller/Joypad mode.

Steps to reproduce the issue :

Overheat, by default, allows you to cast an ability multiple times before it goes on cooldown.

If a skill has 2 charges on the overheat mechanic, it allows you to cast it twice before it goes on cooldown. However, while using a controller, if you cast the ability only once, and then wait for the overheat charge to cooldown, the next cast will put the ability on cooldown and eat TWO overheat charges.

For example: I use Fireball one time, and it adds 1 overheat charge. I have 1/2 charges now. If I wait for the UI to remove the yellow circle (the overheat charge) from the skill, the spell APPEARS to have cooled down, and I will have 2 empty overheat charges again. I now cast Fireball ONE time, and the spell goes on cooldown, spending 2 charges of overheat.

For the next example, we’ll IGNORE the UI telling us about the overheat for fireball:
If I use fireball one time, it will add 1 overheat charge. I have 1/2 charges now. If I wait for a FULL MINUTE without using fireball (ignoring the UI’s overheat display on the skill), it will have long since cooled down, and I will have 2 overheat charges remaining. I can now cast fireball 2 more times, putting it on cooldown. (This is normal)

What does this mean?

It means that the Overheat mechanic on the UI while using a joypad/controller is bugged, and displays the incorrect number of charges on overheat, making you think the abilities have cooled down, when in reality, they still have an overheat charge remaining.

Swapping to Mouse Mode causes the overheat charges to show their proper timings on the UI. However, if you swap back to a controller, the overheat circles are being removed almost 10 or more seconds too soon on the UI, causing you to cast earlier thinking the spell is ready again.

4 Likes

Been a problem since beta. Another one of those things that just never got fixed.

2 Likes

I have the same problem