LogFAQs > #893725358

Dikitain posted...

Probably Doom/Doom II (I consider them one game since Doom II is basically just an updated version of Doom). Granted, probably not the perfect game engine for an FPS since it is technically 2.5D (since two objects can't exist in the same space on top of each other), but it is probably the perfect FPS. Labyrinthine, never repetitive, perfect balance of weapons, perfect balance of monsters, everything just works out perfectly.

@Dikitain Oh, brother. You're talking to someone who spent 6 years making a custom Doom II level set / campaign. lmao. I love Doom/Doom II, I know that engine inside and out by now. You're right, the automap (tab) is actually the map itself that is being read by the game. The different geometric sectors and lines have data like "floor height" "light level" "wall texture" "switch activate tag: (variable)" etc. and the game engine runs from that information. John Carmack is seriously a genius, if you've ever read his development logs or journals about his contributions in the creation of 3D gaming and PC image rendering, from Commander Keen (which started as a Mario 3 DOS clone, but Nintendo said they weren't really interested in the PC market so they rejected the idea) all the way to true 3D polygons in Quake etc.

Doom 64 accomplished room over room "3D" by a visual trick involving silent teleporters and sector floor/ceiling heights, similar to the way Duke Nukem 3D did, if I recall correctly. That was why cooperative and deathmatch had to be scrapped from Doom 64, because there would be really weird bugs and glitches if someone went over a "3D Bridge" and the other player didn't. This problem didn't happen in Duke Nukem 3D because you actually (silently) teleported to a different room entirely when you were "upstairs", it wasn't a visual change of sector data.
---

Hoppe hoppe Reiter, und kein Engel steigt herab
mein Herz schlagt nicht mehr weiter, NUR DER REGEN WEINT AM GRAB