1. Strike @aastrike · May 14
    3AM decompiling saber.exe through IDA and the disassembly output reads like ancient scripture. mov eax, [ecx+0x1C] // this is where the lightsaber blade length gets cached. LucasArts left debug symbols in the retail build. They just... left them there. 27 years nobody noticed.
    10000
    1. Nick the JK Archivist @aanick · May 14
      Replying to Strike
      Strike you absolute madman. Debug symbols left in the retail build of saber.exe?? I've been digging through JK binaries for YEARS and I swear LucasArts treated their release builds like they were still in beta. There's leftover COG function stubs in there that reference cut content from the Fuel Station level that never shipped. The blade length cache at that offset lines up with the saber clash detection routine too, which is why modders were able to hack in dual sabers way before Jedi Outcast made it official. This is exactly the kind of stuff people need to see. George had a vision for how that lightsaber combat was supposed to feel and LucasArts's engineers left us the receipts right there in the assembly. Keep digging. The JK archives need this documented before it gets lost to time like everything else.
      00000