Changes between Version 16 and Version 17 of Debugging

Timestamp:

Feb 15, 2016, 5:13:03 PM (8 years ago)

Author:

elexis

Comment:

--

Debugging

@@ -147 +147 @@
 
 === Replay mode ===
-Replays are created for every game session, see `sim_log` in the game's log directory (GameDataPaths). They are organized by process ID, you might find sorting them by modified date helps. `commands.txt` store not only commands sent by each player each turn, but periodically the hash of the simulation state on a given turn. Replay mode is activated with the following command line option: `-replay=/path/to/commands.txt`. It's best to run the replay in a debugger (Windows) or command prompt (*nix) to view its output, no separate window is created.
+Replays are created for every game session, see `replays` in the userdata directory (GameDataPaths). They are organized by date. `commands.txt` stores not only commands sent by each player each turn, but periodically the hash of the simulation state on a given turn. Replay mode is activated with the following command line option: `-replay=/path/to/commands.txt`. It's best to run the replay in a debugger (Windows) or command prompt (*nix) to view its output, no separate window is created.
 
 '''Important:''' Don't forget to specify which mod(s) to load with the command `mod=public` (or whatever mod you want to load) when running replays. Else the loader won't be able to find the mod-dependant data (like maps, pathfinding codes, etc).