The mod didn't load the maps as separate instances. Instead, it teleported your entity across the void of the engine’s coordinate system. Because the RenderWare engine stores map data in a linear array, the mod simply repositioned your player to x: -600, y: -1000 for Liberty City and x: 1400, y: -200 for Vice City.
And for that, we remember version 0.9.4—the broken, beautiful ghost of what could have been. Have you ever attempted to run GTA Coop 0.9.4? Did you manage to finish a single mission without crashing? Share your war stories in the comments. gta coop 0.9.4
It showed us that Rockstar’s engine—that creaky, beautiful RenderWare beast— could be bent into co-op shape. It inspired later projects like GTA V: Enhanced Native Trainer (which had mission co-op) and even FiveM (which owes a debt to these early network experiments). The mod didn't load the maps as separate instances
The mod injected a DLL into the San Andreas executable (v1.0, specifically—modders know the pain of the v2.0 executable). It hijacked the game’s rendering loop and inserted a secondary network thread. The result? Two players could inhabit the same single-player world. And for that, we remember version 0
The prevailing theory is legal pressure. Rockstar Games had just launched GTA IV, which featured its own (laggy, limited) co-op in modes like "Deal Breaker." An open-source mod that let you play the entire San Andreas campaign for free was a competitive threat. There were no cease-and-desist letters made public—just a slow fade. The team’s website (gtacoop.com) went offline. SourceForge pages grew cobwebs.
When you launch 0.9.4 today, you’re not playing a game. You’re visiting a digital fossil. You’re seeing the exact moment the modding community realized that GTA didn't need to be a lonely crime spree. It could be a shared rampage.