Status Updates posted by axdoomer
I just published an article on Medium that explains how I managed to patch the Doom II executable in order to fix the Arch-Vile fire spawned at the wrong location bug using a hex editor. Some knowledge of assembly may be required to understand everything.
I started to write this article in July to describe how I did the patch for my Doom patcher tool. The article was 90% done, but then I got lazy and didn't touch it again until this week. :D
If you want to play Deathmatch 3.0 using vanilla Doom (weapons stay, items respawn), here's how you do it.
Open DOOM2.EXE (size: 709905 bytes) in your hex editor of choice (I suggest HxD on Windows and Okteta on Linux).
At offset 0x0006001, replace 0x01 with 0x03. This make the -deathmatch option start a DM 3.0 game. Then go at offset 0x00073712 and replace 0x85 with 0x82. This makes the items respawn in DM 3.0 and DM 2.0 (altdeath) instead of just DM 2.0.
You won't be able to start DM 1.0 games anymore, but this hack is demo-compatible with Crispy Doom and Doom Vanille. My patching tool can also patch the EXE for you. Let me know if you have any issues.
Note: Numbers start with 0x because they are hexadecimal.
I just finished with my Doom patcher, a script that applies hacks to the vanilla Doom 2 executable. Right now, it has 12 different hacks that it can patch.
Also, please feel free to tell me if you find spelling mistakes in README.md. I always do a few mistakes late at night. I already found one and I will correct all of them at the same time.
You need a Python interpreter to run the script. If you are on Windows, you'll have to install it.