RacerRoomSetup: Edited via web interface
authorunC0Rr
Mon, 20 Aug 2018 22:24:01 +0100
changeset 1508 2fe2497eb7d7
parent 1507 0df1fac87c44
child 1509 9c51e2c8572c
RacerRoomSetup: Edited via web interface
RacerRoomSetup.wiki
--- a/RacerRoomSetup.wiki	Mon Aug 20 22:16:41 2018 +0100
+++ b/RacerRoomSetup.wiki	Mon Aug 20 22:24:01 2018 +0100
@@ -37,7 +37,7 @@
 And leave.  The callvote will cause errors as long as you are still the room admin, but they don't matter.  You can quit/rejoin before that step if you wish.
 
 == Running checker ==
-Make sure you have hedgewars working, your login/password is stored in frontend's config
+Make sure you have hedgewars working, your login/password is stored in frontend's config.
 
 To build checker:
 {{{
@@ -55,3 +55,9 @@
 {{{
 INSERT INTO gameversions (protocol, version) VALUES (55, '0.9.24'), (56, '0.9.25-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.
+
+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 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