Mercurial Mercurial > hwkb / diff
summary | shortlog | changelog | graph | tags | bookmarks | branches | files | changeset | file | latest | revisions | annotate | diff | comparison | raw | help
Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
RacerRoomSetup.wiki
changeset 2077 514babfbad9e
parent 2051 3a9136f56fe5
child 2078 499a9bda5571 
--- a/RacerRoomSetup.wiki	Wed Oct 30 03:01:54 2019 +0000
+++ b/RacerRoomSetup.wiki	Wed Oct 30 11:59:37 2019 +0100
@@ -47,17 +47,19 @@
 Put checker.ini into ~/.hedgewars with such content:
 {{{
 [engine]
-exe=/usr/home/hedgewars/0.9.24/bin/hwengine
-prefix=/usr/home/hedgewars/0.9.24/share/hedgewars/Data
+exe=/usr/home/hedgewars/<VERSION>/bin/hwengine
+prefix=/usr/home/hedgewars/<VERSION>/share/hedgewars/Data
 }}}
 
 When updating between versions, update version in checker's source, run this on the server's database to have new stats appear on the records page (see also [ProtocolNumbers]):
 {{{
-INSERT INTO gameversions (protocol, version) VALUES (55, '0.9.24'), (56, '0.9.25-dev');
+INSERT INTO gameversions (protocol, version) VALUES (59, '1.0.0'), (60, '1.0.1-dev');
 }}}
 
-If you see too many "Check failed" messages in your checker's log, check your setup. If you fixed a problem with engine, you might want to recheck previously failed replays by moving them from "failed" to "replays" folder on the game server. You may do it on live system, that's np.
+(Replace the version numbers and protocol numbers with the correct ones.)
+
+If you see too many "Check failed" messages in your checker's log, check your setup. If you fixed a problem with engine, you might want to recheck previously failed replays by moving them from "failed" to "replays" folder on the game server. You may do it on a live system, that's not a problem.
 
-It is also not a problem to stop checker at any point. If you have engine hanging for too long (shouldn't happen since .24) and game0.log suggests that there's nothing going on in the game being replayed, just kill engine process to count this attempt as failed.
+It is also not a problem to stop checker at any point. If you have engine hanging for too long (shouldn't happen since 0.9.24) and `game0.log` suggests that there's nothing going on in the game being replayed, just kill engine process to count this attempt as failed.
 
-It is fine to have multiple instances of checker running, even on the same host and on the same account, if you like. This helps when you have lots of replays to check and some spare cpu cores.
\ No newline at end of file
+It is fine to have multiple instances of checker running, even on the same host and on the same account, if you like. This helps when you have lots of replays to check and some spare CPU cores.
hwkb