It's my understanding that Maniac Mansion does something similar with coroutines and costumes. This makes certain things easier with timing since the animation and gameplay logic are decoupled.

The change_costume macro is effectively inter-thread comm. to tell the costume to change to a different animation. In my NES game engine "veil engine" each actor gets 2 coroutines one for logic and the other a costume thread.

The code shown previously was from the actor's coroutine. This has all the logic for physics and gameplay. There is another coroutine that is the costume thread.

Yeah, with this I am using a jump table. So on the left is a CA65 enum with all the states (including transition states). The middle shows the jump code and part of the table, and then the last are all the subroutines that execute for each state.

6502 assembly

It does look like that. I use CA65 scopes to encapsulate data and subroutines like a class would.

CA65

although, after uploading with dropped frames of course you can barely tell....