From 9b4fddb8c0b4186907dd311efc77a3b90a2b895d Mon Sep 17 00:00:00 2001 From: JBM Date: Wed, 20 May 2020 16:10:13 +0200 Subject: [PATCH] Fill up statement --- config/statement_en.html | 62 +++++++++++++++++++++++++++++++++++++++- 1 file changed, 61 insertions(+), 1 deletion(-) diff --git a/config/statement_en.html b/config/statement_en.html index 83c0e4e..b47d627 100644 --- a/config/statement_en.html +++ b/config/statement_en.html @@ -16,7 +16,67 @@ Rules
- In the classic version, you have to shoot at least one stone per turn. This isn't enforced yet. + You have to shoot at least 1 stone per + turn if you have any left.
+
+

+   + Rule Evolution +

+
+ The following points are still ideas in flux, waiting for some + opinions (leave a comment on the draft submission page!) +
    +
  • + is it even worth publishing? can the problem be totally solved? +
    • +
  • + More maps? (a map is a road length / initial stones pair) +
    • +
  • + leagues? I could conceive the referee being permissive (allow 0 stones thrown) in the first one, and then strict. +
    • +
  • + fog of war? (see only troll position, not enemy throw/stones left)
    + variable for of war? (seeing enemy stones + is a boolean decided randomly as part of the map?) (or + seeing enemy stones only when troll is close to us?) +
    • +
  • + Praise for my artistic skillz +
    • +
  • + Other remarks? +
    • +
+
+
+
+
+
+
Victory Condition
+
Your opponent loses.
+
+
+
+
+
+
Defeat Condition
+
    +
  • The troll reaches your castle.
    • +
  • When no player has stones left, the troll is closer to your castle.
    • +
+
+
+
+

+   + I/O Protocol +

+
+ Just read the sample code. You can figure this out. +
+
-- 2.30.2