1 <div class="statement-body">
3 <div class="statement-section statement-goal">
5 <span class="icon icon-goal"> </span>
8 <div class="statement-goal-content">
9 Don't get destroyed by the troll.
13 <div class="statement-section statement-rules">
15 <span class="icon icon-rules"> </span>
18 <div class="statement-rules-content">
19 You <em>have</em> to shoot at least <const>1</const> stone per
20 turn if you have any left.
23 <div class="statement-section statement-warning">
25 <span class="icon icon-warning"> </span>
26 <span>Rule Evolution</span>
28 <div class="statement-warning-content">
29 The following ideas are still in flux, waiting for some
30 opinions. Please drop a word on the
31 <a href="https://www.codingame.com/contribute/view/507070b7925f661e2d2835c14f950b9d157e">
35 <a href="https://forum.codingame.com/t/troll-vs-castles-brainstorm/184827?u=jbm">
40 Is it even worth publishing? can the problem be totally solved?
43 More maps? (a map is a {road length} × {initial stone count} pair)
46 Leagues? I could conceive the referee being permissive
47 (allow 0 stones thrown) in the first one, and then strict.
50 Fog of war? (see only troll position, not enemy throw/stones left)
53 <strong>variable</strong> for of war? (seeing enemy stones
54 is a boolean decided randomly as part of the map?
57 alternative fog of war? (seeing enemy stones only when
58 troll is close to us?)
61 Praise for my artistic skillz
69 <div class="statement-victory-conditions">
70 <div class="icon victory"></div>
72 <div class="title">Victory Condition</div>
73 <div class="text">Your opponent loses.</div>
76 <div class="statement-lose-conditions">
77 <div class="icon lose"></div>
79 <div class="title">Defeat Condition</div>
81 <li>The troll reaches your castle.</li>
82 <li>When no player has stones left, the troll is closer to your castle.</li>
86 <div class="statement-section statement-protocol">
88 <span class="icon icon-protocol"> </span>
89 <span>I/O Protocol</span>
91 <div class="statement-protocol-content">
92 Just read the sample code. You can figure this out.
95 <div class="statement-section statement-expertrules">
97 <span class="icon icon-expertrules"> </span>
100 <div class="statement-expert-rules-content">
102 The following maps are currently available and randomly yet
103 extremely fairly (you wouldn't believe the effort that went
104 into this) chosen uniformly at random among the following:
107 <tr><th>Road length</th><th>Stones</th></tr>
108 <tr><td><const>7</const></td><td><const>15</const></td></tr>
109 <tr><td><const>7</const></td><td><const>30</const></td></tr>
110 <tr><td><const>15</const></td><td><const>30</const></td></tr>
111 <tr><td><const>15</const></td><td><const>50</const></td></tr>
114 As with anything in this <em>draft</em> statement, this
115 is <strong>subject to change without notice</strong>. Why do
116 you think they're provided in the game input?
120 <div class="statement-section statement-protocol">
122 <span class="icon icon-protocol"> </span>
123 <span>Change Log</span>
127 Enforce the one-stone rule. (that also fixed the legacy
128 buh—sorry people! I put an easter egg in exchange)
131 Cutesy defeat animations.
134 Distinct castle sprites!
137 Terminate game when there are no more stones in sight.
140 More pretty. (SRLSLY)
143 No more void maps. (root cause: Java <const>%</const> on a
148 <div class="statement-story-background">
149 <div class="statement-story"
150 style="position: relative; min-height: min-content">
151 <div class="story-text">
152 Based on an involuntary suggestion by
153 <span class="card" cg-codingamer-card-popup=""
154 userid="user.codingamer.userId">
156 href="/profile/dbfa96e0ac9b77a3db679628f27224ae8509333"
157 title="Zaap38">Zaap38</a>
159 on the #Fr channel. The original appears to be by
160 <a href="http://andre.lovichi.free.fr/teaching/ea/2015-2016/cours/troll/Trolls_et_chateaux.pdf">
161 Romain André-Lovichi