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

@@ -16,33 +16,47 @@ Rules

- You have to shoot at least 1 stone per - turn if you have any left. -
+ If you have stones, shoot 1 or more of them. +
+ If you don't have stones, shoot 0 exactly. +
-
+

-   +   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 stone count} pair)
  • - 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.
  • - 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)
  • - 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?) + 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 +87,119 @@

      - I/O Protocol + I/O Protocol

    Just read the sample code. You can figure this out. +
    + You're currently allowed the default SDK timings. I think it's + one second for the first turn and 50 ms then, but don't + quote me on this. +
    +
    +
    +

    +   + 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
    615
    630
    1430
    1450
    +

    + 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 +

    +
      +
    • + This is computer science. Trees are non-negociable. + (asset contributed by + + Alshock + ) +
      • +
    • + Don't destroy the castle if the troll doesn't reach it. +
      • +
    • + Ensure proper troll movement direction in all cases of + cheating. +
      • +
    • + Fixed the road length fencepost non-issue. +
      • +
    • + 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) +
      • +
    +
    +
    +
    +
    +
    + “Trolls simply detest the very sight of dwarves (uncooked).” +
    +
    + — J.R.R. Tolkien, The Hobbit +
    + +

    + Based on an involuntary suggestion by + + Zaap38 + + on the #Fr channel. The original appears to be by + + Romain André-Lovichi + . +

    + +

    + The source code for this game + is available. +

    +