Players complained. Leo explained in a Discord announcement: "v19 has a memory leak in the instance manager. Restarts every 4 hours keep the server stable. This is authentic to the original experience."
Leo checked the LoginServer source. Lyra was right. In the original v19 files, the CGPlayer::CreateGM function had no authentication check. Any client could send 0x7D03 packet with a GM level, and the server would obey.
/Resource/ , /Script/ , /Neuz.exe/ , /AccountServer/ , /CacheServer/ , /CoreServer/ , /Database/ , /LoginServer/ , /WorldServer/ . flyff v19 server files
SorrowX logged back in. Within 90 seconds, he was in jail. He tried to log out and back in. The server remembered his flag. He deleted his character and made a new one. The Reaper Loop caught him again within five minutes.
It wasn't.
But the old v19 files had a secret. Deep in the CoreServer 's memory management, there was a hidden function: SendV19CoinUpdate . Leo had assumed it was deprecated code from the Korean version.
Leo had to ensure the siege scripts worked. v19 siege was notoriously buggy. The Flag objects sometimes despawned. The Castle Gate HP bar would freeze if a player disconnected inside the siege zone. Players complained
/announce Server shutting down permanently in 30 days. Download your character data at epochflyff.com/export.
He bought a cheap dedicated server from OVH in France: Intel Xeon E3, 32GB RAM, 1Gbps unmetered. He configured the CoreServer to handle 500 concurrent users, but he knew the real bottleneck was the WorldServer 's garbage collection. In v19, memory leaks were a feature, not a bug. This is authentic to the original experience
SorrowX, the hacker from Day 47, had become a developer. He now maintained the anti-cheat system.
[INFO] User 'Kite' has logged in. [INFO] User 'Merlin' has logged in. [INFO] User 'SorrowX' has logged in (banned flag overridden by admin).