Unreal-Engine-3

I started reading the decompiled arena code and found the server logic sitting right next to the client logic in the same files, fully written, wired to a switch that’s soldered to ‘off’.

I’ve been working on this alone and some of my early conclusions are load-bearing. If you’ve cracked open an old Unreal Engine 3 game before, this post is me asking you to check my work.

Last time eight of ten test functions came back readable. Then I pointed the tool at the one class that actually matters and it fell over on 111 functions out of 150. This is the fix, and the moment the whole codebase finally dumped to disk.

The tool that turns Fury’s compiled code back into something readable crashes on the first file. A day later it is reconstructing real Fury functions, and I know the one specific thing still standing between me and the rest.

Half a day of poking the dead client with a stick is done. It’s in great shape. Every way in is bricked shut. So the next stretch is the slow one: decompiling.

The shortcut was: get the game to quietly host a match for itself, no server needed. I tried it. The door is welded shut, same as the last three.

I point the dead game’s login at a tiny program I wrote, just to eavesdrop on the very first thing it tries to say to a server that isn’t there anymore.

A 16-year-old game boots on Windows 11 and hands me the whole character screen with nothing behind it. Then every other door I try is bricked shut.

I set up the project, wrote a plan, had it audited, and found out the plan was aimed at the wrong problem. The client I have is also way more generous than I thought.

Kicking off a project to reverse-engineer and revive Fury, a 2007 MMO that’s been dead since 2008.