X-Git-Url: https://troll.desast.re/troll.git/blobdiff_plain/9b4fddb8c0b4186907dd311efc77a3b90a2b895d..d8386a8848a4ba71b9048c03c2a6010dac937352:/config/statement_en.html diff --git a/config/statement_en.html b/config/statement_en.html index b47d627..89a0e27 100644 --- a/config/statement_en.html +++ b/config/statement_en.html @@ -1,4 +1,4 @@ -
+

@@ -20,29 +20,88 @@ turn if you have any left.

-
+

-   +   + Breaking Change +

+

+ The roadLength game input variable used to be the + cardinal number of positions the troll could be in. That's the + way it was presented in the original game, but I leaned more + towards distances to make the I/O protocol easier on beginners. + So it's currently inconsistent. +

+

+ This is going to change in the following days to be a distance + everywhere, more in line with the protocol's other measures. + Not to mention being somewhat more consistent with the variable + name. Thanks + + @Snef + + for reminding me of this. +

+

+ If you used this variable, I suggest you temporarily used one + of these workarounds so you don't get bit by the upcoming + change: +

+ + + + + + + + + + + + + + + + + +
Former useAs aTry this
roadLength - 1
distance to opponent
roadLength & (~1)
roadLength
number of troll states
roadLength | 1
roadLength + 1
I have no idea
(roadLength + 1) & (-1)
+
+
+

+   Rule Evolution

-
- The following points are still ideas in flux, waiting for some - opinions (leave a comment on the draft submission page!) +
+ The following ideas are still in flux, waiting for some + opinions. Please drop a word on the + + contribution's page + + or + + on the forum +
  • - is it even worth publishing? can the problem be totally solved? + Is it even worth publishing? can the problem be totally solved?
  • - More maps? (a map is a road length / initial stones pair) + More maps? (a map is a {road length} × {initial stone count} pair)
  • - leagues? I could conceive the referee being permissive (allow 0 stones thrown) in the first one, and then strict. + 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?) + 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? +
    • +
  • + alternative fog of war? (seeing enemy stones only when + troll is close to us?)
  • Praise for my artistic skillz @@ -73,10 +132,84 @@

      - I/O Protocol + I/O Protocol

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

    +   + Maps +

    +
    +

    + The following maps are currently available and randomly yet + extremely fairly (you wouldn't believe the effort that went + into this) chosen uniformly at random among the following: +

    + + + + + + +
    Road lengthStones
    715
    730
    1530
    1550
    +

    + As with anything in this draft statement, this + is subject to change without notice. Why do + you think they're provided in the game input? +

    +
    +
    +
    +

    +   + Change Log +

    +
      +
    • + Of course that game needed MSG functionality! +
      • +
    • + Enforce the one-stone rule. (that also fixed the legacy + buh—sorry people! I put an easter egg in exchange) +
      • +
    • + Cutesy defeat animations. +
      • +
    • + Distinct castle sprites! +
      • +
    • + Terminate game when there are no more stones in sight. +
      • +
    • + More pretty. (SRLSLY) +
      • +
    • + No more void maps. (root cause: Java % on a + negative seed) +
      • +
    +
    +
    +
    +
    + Based on an involuntary suggestion by + + Zaap38 + + on the #Fr channel. The original appears to be by + + Romain André-Lovichi + . +
    +
    +