Also another question for you if you don't mind: you said you were unable to move when the bug occurred. I managed to reproduce the issue, and I was still able to go into move mode and move. Are you sure you weren't able to move? (You would have to select move mode - clicking on an adjacent tile in spawn mode wouldn't work.)
I messed around with it and was able to reproduce the issue. Am writing the following down here for future reference. The issue occurs when you have 1 mana and attempt to use a summoning card which is hardcoded in obj_tile as costing 2 mana. (The only way to have an odd numbered mana currently is to use the moon card.) Summoning tile, when clicked, is supposed to use the tarotCost function (which currently always returns 1), but is just hardcoded in this case as 2. This results in obj_card successfully being selected, said card being destroyed by obj_tile, but obj_boardElement does another check on available mana - it then sets the action to null, and thus doesn't spawn the angel and doesn't decrement mana. All of this would just be solved by using a consistent amount of mana by calling the tarotCost function. So yeah, that was definitely the result of a rushed job. Whew.