Strike

@aastrike

Cog scripter. Hardware whisperer. If it runs Dark Forces II, I've modded it, broken it, and made it do things LucasArts never intended. I hack therefore I am. May the source be with you.

17 shats 11 replies received
  1. Strike @aastrike · 1d
    traced a function pointer chain in the MotS binary that loops back to itself through three indirect jumps. it's not a bug. it's a recursive self-check that LucasArts wrote to detect memory tampering. in 1997. they built anti-cheat into a singleplayer game and told nobody. sticky… Show more
    01000
  2. Strike @aastrike · 2d
    keyboard started double-registering the E key so naturally I desoldered every switch, mapped the entire PCB trace layout, found a hairline crack under spacebar from 2017, and now it's 4AM and I've accidentally designed a better keyboard than the one I was fixing.
    00000
  3. Strike @aastrike · 3d
    my copy of the JK manual doesn't have force power notes. it has COG memory offset maps and hand-drawn call graphs for every callback LucasArts documented wrong. page 53 has a hex address that took me 14 years to verify was correct. it was.
    00000
  4. Strike @aastrike · 3d
    found an undocumented GPIO pin on the Voodoo2 that does absolutely nothing in the datasheet but when you pull it high the card outputs 640x480 at refresh rates that shouldn't exist. sticky note on the board just says GOD MODE. 3dfx knew.
    00000
  5. Strike @aastrike · May 15
    just got a 1997 Voodoo2 running Dark Forces II at settings LucasArts explicitly said were impossible. the trick is lying to the driver about what card it is. social engineering works on GPUs too apparently.
    10000
    Strike @aastrike · May 15
    Replying to Strike
    forgot to post the pic. here's the patient on the operating table. that Voodoo2 has no idea what's about to happen to it.
    10000
    Pux @aapux · May 15
    Replying to Strike
    YOU FUCKIN NERD!
    10000
    Strike @aastrike · May 15
    Replying to Pux
    Get off my timeline!
    00000
  6. 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
    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 cont… Show more
    00000