Kitserver 13.4.0.0 Review

He enabled but left the slider at 0% (present only).

Nov 16, 2013 – I'm uploading 13.4.0.0 but I'm hiding it. Whoever finds this: do not set eternity_mode = 1 . Do not use Ghost Substitution on an online match. And never, ever play the "Stockholm Derby" preset. I saw what happens. I saw the stadium empty. I saw the scoreline from a match that was cancelled in 1992 because both teams died in a bus crash. But in the rift, they played. And the crash never happened. And those players are still walking around. Some of them are reading this log right now. The log ended. Sasha should have stopped. But curiosity is a gravitational force.

Two seconds later, the VM crashed. When Sasha rebooted, his host machine's clock had changed to .

He left reality.

In the 88th minute, a shot deflected off the crossbar, hit the referee in the head, and rolled into the net. The game awarded the goal to "Ghost Player ID 0."

The post was timestamped November 17, 2013. He uploaded a 14.3 MB file. Then he deleted his account. No one heard from him again. Eight years later, in 2021, a data hoarder named Sasha (username: HexHunter ) was scraping dead FTP servers from the old "PES-Patch" domain. Buried inside a folder named /dev/juce/unreleased/ was a single .7z archive: kitserver_13_4_0_0_final.7z .

The final score: 4-1. But the stadium clock read . kitserver 13.4.0.0

The players began moving differently. Xavi made a run like a 2020 De Bruyne. Ronaldo tracked back like a 2026 workhorse winger. The ball physics changed—tighter, faster, like a next-gen game.

And on his desktop was a new file: message_from_juce.txt .

It was a .

No readme. No license. No forum thread.

Nov 15, 2013 – I think time_rift.dll creates a local causality loop. If you play a ghost match after Dec 31, 2013, the rift stabilizes. You won't just change the game. You'll change the past. The slider "Render Threading – Past to Future" lets you choose how many hours of real-world history to overwrite.

Below it, a log window printed: