: What are you using to disassemble that code? Disassembly may be the only way
: to reproduce some of Marathon's behavior.
Wrong tense. I disassembled it years ago, using MacNosy on a G3 booted into MacOS 8.6. I finally got my fill of trying to follow all the twists and turns in MacNosy, and had it output what it had to a plain text file, which I now peruse in BBEdit. I keep notes in NoteBook. That combination is a real pleasure to work in.
I fiddle with the disassembly in my spare time, adding comments as I figure things out. The notebook in a separate window helps me keep track of record layouts and keep symbol names consistent. Every time I figure out what a field does, I give it a name, record that in the notebook, then find every use of it in BBEdit and make the name consistent.
I recently wrote a small C++ app to expand the data initialization code from the original codefile. (It won't run on my Intel iMac, but Resource Manager still works.) That helps me figure out what the code is doing. (For example, the code to assign wall images after rebuilding the Labyrinth didn't make any sense until I could actually see the tables that were driving the process.)
Looking at the unpacked data is also the only way to learn some of the traits of the various monsters. I now know, for example, that the Purple Barney on Warning Earthquake Zone is truly invulnerable. Nothing hurts him. Not bullets. Not crystals. Nothing. (The Venomous Oozes on the same level are also invulnerable. The (in)vulnerability of the Dreaming God is controlled by code, not by the table.)
