Hit Him Where It Hurts, Cassandra! (Apollo Is The WORST.)

Hit him where it hurts, Cassandra! (Apollo is the WORST.)

Mordred Manor! (with close-ups under the cut)

edit: i just put up some new drawings on my ko-fi, so if you wanna print this out as a poster or something, you can find it there at full resolution in the 'Misc Art' folder! :) (personal use only!)

If you got dopamine problems I feel bad for you son

I got 99 problems and ADHD is all of them

I don't know if I'll draw every episode but felt compelled with these.

S2 Ep 2 stuff

I'm a big fan of wizards-as-programmers, but I think it's so much better when you lean into programming tropes.

A spell the wizard uses to light the group's campfire has an error somewhere in its depths, and sometimes it doesn't work at all. The wizard spends a lot of his time trying to track down the exact conditions that cause the failure.

The wizard is attempting to create a new spell that marries two older spells together, but while they were both written within the context of Zephyrus the Starweaver's foundational work, they each used a slightly different version, and untangling the collisions make a short project take months of work.

The wizard has grown too comfortable reusing old spells, and in particular, his teleportation spell keeps finding its components rearranged and remixed, its parts copied into a dozen different places in the spellbook. This is overall not actually a problem per se, but the party's rogue grows a bit concerned when the wizard's "drying spell" seems to just be a special case of teleportation where you teleport five feet to the left and leave the wetness behind.

A wizard is constantly fiddling with his spells, making minor tweaks and changes, getting them easier to cast, with better effects, adding bells and whistles. The "shelter for the night" spell includes a tea kettle that brings itself to a boil at dawn, which the wizard is inordinately pleased with. He reports on efficiency improvements to the indifference of anyone listening.

A different wizard immediately forgets all details of his spells after he's written them. He could not begin to tell you how any of it works, at least not without sitting down for a few hours or days to figure out how he set things up. The point is that it works, and once it does, the wizard can safely stop thinking about it.

Wizards enjoy each other's company, but you must be circumspect about spellwork. Having another wizard look through your spellbook makes you aware of every minor flaw, and you might not be able to answer questions about why a spell was written in a certain way, if you remember at all.

Wizards all have their own preferences as far as which scripts they write in, the formatting of their spellbook, its dimensions and material quality, and of course which famous wizards they've taken the most foundational knowledge from. The enlightened view is that all approaches have their strengths and weaknesses, but this has never stopped anyone from getting into a protracted argument.

Sometimes a wizard will sit down with an ancient tome attempting to find answers to a complicated problem, and finally find someone from across time who was trying to do the same thing, only for the final note to be "nevermind, fixed it".

Wait, but the infamous "he was disarming a weapon" line in regards to Ambrosius could actually be not a justification but explanation for why Bal still trusted Ambrosius. We know from posters and propaganda that the protocol isn't to "disarm" but to kill.

"If you see something, slay something."

Ambrosius didn't follow protocol for a monster or human threat. He followed protocol for a weapon. His target wasn't Ballister but the sword, not in the sense that Ballister is in denial and making up excuses, but in the fact that he literally made use of the protocol meant for weapons, NOT living threats