He wasn't playing for fun. He was replaying the "Mall Shootout" mission for a video retrospective. But the game, as always, had other plans: infinite loading screens, audio crackling like a broken radio, cars that fell through the pavement, and a memory leak so aggressive that after 20 minutes, Tommy Vercetti would start T-posing like a glitched god.
Why?
Today, somewhere in the world, a 19-year-old downloads SilentPatchVC.zip for the first time. They don't know who made it. They don't know the 14 crashes it prevents. They just know the game works.
He found the first wound at offset 0x004C7A31 — the infamous "streaming memory" bug. The game loaded assets into RAM but never freed them properly. Every 20 minutes, the heap overflowed, and the engine panicked.
SilentPatchVC.zip Status: Completed / Archived Signature: Silent (Alexander Blade, 2015) The Story The Breaking Point (2014)
Silent realized something horrible: the official patches (v1.1) didn't fix the game. They just added more workarounds .
Silent opened IDA Pro (a disassembler) and loaded gta-vc.exe . He wasn't going to patch the game. He was going to autopsy it.
"This is unacceptable," he muttered.
Because the memory leak was just the beginning.
Over the next two years, SilentPatch became the silent standard. Every modpack included it. Every "How to play Vice City in 202X" guide led with it. Even Rockstar's own later re-releases (the notorious "Definitive Edition" of 2021) had bugs that SilentPatch had fixed six years earlier.
Silent would have liked that.
The description was three lines: Fixes crashes, audio issues, frame rate dependency, memory leaks, and broken reflections. Drop in game folder. No configuration needed. Within 24 hours, the thread exploded.
At 9:14 PM, Silent uploaded SilentPatchVC.zip to a small modding forum. The file size: 247 KB.
In a 2017 interview (translated from Russian), he said: "I didn't fix Vice City because I loved it. I fixed it because it was broken, and no one else was going to do it. That's all."