Spellbook Stays Open

Greetings.

I must be missing something. I have a hero ability spellbook with multiple spells in it. However, when I use one of those abilities, it doesn't close the spellbook, as I am accustomed to it doing. I am free to use any of the abilities in the book as much as I want, as long as they're not individually on cooldown.

I have Data - Shared Spell Cooldown set to True.

How about deseleting then reselecting the unit instantly after using a spell?

Because that sucks royally due to the crappy delays.

================

My guess is that this is a random blizzard bug in spellbooks. Give each of them a 0.01 second cooldown...?

They all have 30-or-so second cooldowns, actually.

Setting the field I mentioned to True is *supposed* to toggle whether the book stays open.

Is the Maximum/Minimum spells set to appropriate numbers... like... on the default spell book,

Data - Maximum Spells 3
Data - Minimum Spells 3

Yes.

Actually, I have another spellbook that I am force canceling but I had assumed it was merely a problem with the trigger destroying the unit that had it before the spellbook was finished closing that caused that to be necessary.

So, in short, no, there are no spellbooks that I know of that are working as intended.

I messed around with the spellbook on the map I was using it on for a while and didn't get very far, so I put together a tiny test map.

At the moment, it seems like whether the spellbook closes properly has something to do with what spell is being cast. I thought it might be tied to the cooldown of the individual spells but the original map's spells all had the same cooldown and it never used any of them.

In this map, the hero has a spellbook like the original and a hero ability with the exact same skills. Both of them close properly and start the cooldown when either Entangling Roots or Dispel Magic is used but not with Roar.

In the original map, I tested with altered versions of Cluster Rockets, Flare, and Acid Bomb and none of them closed the book or started the cooldown.
Artificially closing the book (via "force menu cancel") worked but was ultimately not useful because the book could be immediately re-opened by the player; it wasn't on cooldown at all.



EDIT!: Solved here.