X-Git-Url: https://troll.desast.re/troll.git/blobdiff_plain/9b4fddb8c0b4186907dd311efc77a3b90a2b895d..045284cf1ba0061fd70a318c67586ef0f40f0a5d:/config/statement_en.html
diff --git a/config/statement_en.html b/config/statement_en.html
index b47d627..e703b11 100644
--- a/config/statement_en.html
+++ b/config/statement_en.html
@@ -27,22 +27,35 @@
      
      
        The following points are still ideas in flux, waiting for some
-       opinions (leave a comment on the draft submission page!)
+       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 +86,53 @@
    
      
         
-       I/O Protocol
+       I/O Protocol
      
      
        Just read the sample code.  You can figure this out.
      
     
+   
+     
Change Log
+     
+       - 
+         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
+         .
+       
+     
+