Debugging spells isn’t like the fancy debuggers in your modern IDE. You gotta compile the spell with debugging symbols and run it through the spell equivalent of gdb direct in the command line.
But most wizards just go with the ol’ “add print statements everywhere” method of debugging.
What is casting a spell in debug mode?
Can you put a breakpoint in your spell? Picturing a devil having a smoke while the wizard puzzles over all the runes suspended in the air.
Debugging spells isn’t like the fancy debuggers in your modern IDE. You gotta compile the spell with debugging symbols and run it through the spell equivalent of gdb direct in the command line.
But most wizards just go with the ol’ “add print statements everywhere” method of debugging.
Okay, let’s see… Not sure if the spell is even activating that glyph sequence. Let’s try casting it again with a purple glow rune there…
printspell debugging.