Clarify a few things

This commit is contained in:
Neale Pickett 2010-10-27 14:50:16 -06:00
parent f42533cc3e
commit c7cc36b058
2 changed files with 17 additions and 11 deletions

View File

@ -15,6 +15,9 @@
<li> <li>
<a href="puzzles.html">Puzzles</a> <a href="puzzles.html">Puzzles</a>
</li> </li>
<li>
<a href="scoring.html">About scoring</a>
</li>
<li> <li>
<a href="irc://10.0.0.2/ctf" <a href="irc://10.0.0.2/ctf"
title="IRC on 10.0.0.2, channel #ctf">Contest chat</a> title="IRC on 10.0.0.2, channel #ctf">Contest chat</a>
@ -24,8 +27,8 @@
<h2>Claim Token</h2> <h2>Claim Token</h2>
<form action="claim.cgi" method="post"> <form action="claim.cgi" method="post">
<fieldset> <fieldset>
team:<input name="t" size="8"> team hash:<input name="t" size="8">
token:<input name="k" size="20"> token:<input name="k" size="30">
<input type="submit" value="claim"> <input type="submit" value="claim">
</fieldset> </fieldset>
</form> </form>

View File

@ -78,17 +78,20 @@
<h2>About time</h2> <h2>About time</h2>
<p> <p>
Many Capture The Flag contests attempt to reward teams who answer Many Capture The Flag contests attempt to reward teams who answer
quickly with more points, by adding a "quick answer" bonus or quickly, by adding a "quick answer" bonus or by decaying point
decaying point values over time. Our contest doesn't work this values over time. Our contest doesn't work this way.
way.
</p> </p>
<p> <p>
We believe that given enough things to work on, quick-moving teams We want to focus on rewarding technical proficiency, allowing
will emerge with more points by answering more questions; while skilled contestants to prove their worth independant of their
providing novice teams a realistic picture of how they're doing. ability to hit F5 quickly. It is our hope that by providing
In addition, when the game infrastructure goes down—which seems to enough things to work on, quick-moving teams will emerge with more
happen a lot in anybody's CTF—there's no losing points while the points by solving lots of puzzles, while novice teams get a solid
organizers struggle to get things back up. benchmark against which to judge their technical skill level: you
don't have to make allowances for reaction time in comparing
scores. In addition, when the game infrastructure goes down—which
seems to happen a lot in anybody's CTF—there's no losing points
while the organizers struggle to get things back up.
</p> </p>
</body> </body>
</html> </html>