Changes between Version 12 and Version 13 of Debugging

Timestamp:

Sep 20, 2014, 4:22:29 PM (10 years ago)

Author:

Itms

Comment:

Update replay mode informations to handle the new mod selection system

Debugging

@@ -156 +156 @@
 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.
 
+'''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).
+
 When replaying a `commands.txt`, the hashes are checked periodically. This can also be used to verify that no breaking changes are introduced by a new patch. Replay mode also creates a `profile.txt` with profiling information every 20 turns, this can be processed into a nice graph as explained [EngineProfiling#Creatinggraphs here].