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.
“Glorfinx’s Globular Glassblower” still shouts “HERE!” at max volume when it walks past a wet dog because he never removed the printf rune after he fixed a bug relating to dripping fur.
Oh but the fireworks of Ericas “broader detect magic” became so popular that she actually added back all the spark colors for all the moral edge cases!
We now have novice wizards playing around with exactly how angry they need to be and how gaudy their robes need to be to get the different signals triggered…
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.
“Glorfinx’s Globular Glassblower” still shouts “HERE!” at max volume when it walks past a wet dog because he never removed the printf rune after he fixed a bug relating to dripping fur.
Oh but the fireworks of Ericas “broader detect magic” became so popular that she actually added back all the spark colors for all the moral edge cases!
We now have novice wizards playing around with exactly how angry they need to be and how gaudy their robes need to be to get the different signals triggered…
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…