Ambushed teleports carry their destination; room 59UN unstuck (rev 35)

An ambush springing TELEPORT OPPONENT opened a stack with params null —
the spring bypasses cast validation and nothing ever asked where the
victim goes — and resolution crashed on the missing cell, wedging the
room 'waiting on Automaton'. Three layers:
- Crash guards: teleport-opponent and mental-force fizzle gracefully on
  a destination-less stack (ungated: no stored command had resolved one).
- The trap commits its destination when laid: setAmbush carries a cell
  ('wherever you say', said in advance), the spring passes it into the
  stack, and the client's arming flow asks for the click.
- Rev 35 refuses arming those spells without a destination; older
  ledgers armed blind and their springs fizzle.
All ledgers verified before deploy.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0138A8CjeQRpvzKxuMfz1Bqc

This commit is contained in:

Eric Wagoner

2026-08-20 10:51:16 -04:00

co-authored by

Claude Fable 5

parent e8c25ddc19

commit 76dd019d5d

5 changed files with 86 additions and 7 deletions

									
										packages/server/src/rooms.ts
									
		+1
		-1
	
												View File
												
				@@ -54,7 +54,7 @@ export interface Room {

				const rooms = new Map<string, Room>();

				/** Rules revision new games are dealt under (stored games keep their own). */

				const RULES_REV = 34;

				const RULES_REV = 35;

				const ROOM_CODE_ALPHABET = "ABCDEFGHJKLMNPQRSTUVWXYZ23456789";