If no time travelers have come back to stop your nonsense, it can't be that bad, right?

Afterwards, I revealed that I had named that option the "Cliffs of Knievel" in my notes, and despite the fact that we all knew that failure would mean certain death, that I was almost certain that they would choose it.

...The War Machine did explode a little bit after making the jump, though.

I know it's been a year, but is this still an issue? I'm wondering if there's something that we can change on the Homebrewery side to improve screen reader compatibility.

My favourite addition so far is the "New > From Blank" button, which now wipes the content in the scratch space to give users an easy way to start a fresh document.

Nothing like "here's the consequences of this spell, you can choose it if you want but it will end the campaign for your character" and letting them opt out of it, to state exactly how much they don't want that

Then using that exact spell on them in the VERY NEXT BATTLE

UPDATE: They could have been banished and gone home. Instead, they chose to stay and fight!

...and then they fought a wizard, who attempted to split the party with Banishment. That wizard was hit so fast, so many times that they lost concentration almost immediately!

I didn't know how many things you could use that ventriloquism book on! I don't know if it counts, given that Guybrush isn't introducing himself, really... Although I kinda want to see more of the adventures of Frank, the talking donkey who fights crime.

Zombie Pirate LeChuck
Won-ton Goodsoup
Captain Loogie
Jethro Vangoghderfassenson
and Just Tito.

Jucius Maximus the Third
The Phlegm Master
Captain Loogie

I believe the "I'm Bobbin. Are you my mother?" line was post-cannon in the Circus of SoMI.

ELAINE: "You honestly expect me to believe that you were disintegrated in a pit of acid? And yet here you are telling me about it, looking very integrated indeed?"
GUYBRUSH: "Ah, well... OK, I embellished it a little for dramatic effect."

Whoops! I accidentally broke the app - all API calls were returning Error 500. Just because it "works on my machine", it doesn't mean that the Vercel deployment will...

It's fixed now.

Managed to sneak away long enough to post it here - redd.it/1olaj76