<commit_before><h1>Help me, Obi-Wan, it's a wall of text</h1>
<p></p>
<p>
    <strong>How does this work?</strong><br>
    <a href="#step1">1) compile your submission.</a><br>
    <a href="#step2">2) upload your submission.</a><br>
    <a href="#step3">3) if there is a specific matchup you'd like to see then create a new game.</a><br>
    <a href="#step4">4) wait for the Match to be resolved and see the outcome and download the battle.</a><br>
    
    
    
    <br><br><a name="step1" class="anchor">. [invisible]</a><br><strong>1. Compiling your Submission</strong><br>
    Since we don't want to give away our clever strategies too easily, we only want to upload compiled jar files.<br>
    i.e. your code has been compiled and is no longer human readable.<br>
    <br> a) Download this <%= link_to "build_for_arena.xml", static_pages_build_for_arena_xml_url, :class => "themed_text" %>. 
    <br> b) Save it into your Battlecode Directory
    <br> c) Run ant -buildfile build_for_arena.xml -Dteam=team arena_build   (Where team == the package your team is currently in)
    <br><br> This will produce an arena_submission_team.jar file (of compiled code only) in your battlecode Directory
    <br> This is the file you need to upload.
    <br> Note team in the above command line is the folder in teams you are wanting to upload. 
    <br> This is the name this Competitor will be known by, so don't use teamnnn if you want to remain anonymous!
    </p>
    <br>
    <a name="step2" class="anchor">.</a><br><strong>2. Uploading your Submission</strong>
    <br>        Clicking on the upload Submission button will allow you to create a new submission.
    <br>   a) Upload your Jar file. 
    <br>        You upload the arena_submission_#teamname#.jar. 
    <br>   b) You have the option of adding your team name (or some sort of team name) if you'd like to declare who you are
    <br>        I'd recommend using the team name slot, it's always more fun to know who you are up against, but the choice is yours. 
    
    <br><br> <a name="step3" class="anchor">.</a><br><strong>3. Creating a Match</strong>
    <br> By default, every submission will play every other submission
    <br> however, this will take some time as the numbers of submissions grow
    <br> to the point that some games may never happen within the life time of the competition.
    <br> These auto played matches, will be played in reverse uploaded time order. i.e. the latest submissions will play each other first.
    <br> If there is a particular match you are interested in, then create a new match.
    <br> When specifying a new match, there is a team name option. Again this can be left blank,
    <br>but it might be interesting to see who is requesting what matches.
    <br> Matches created by users are always played first. (ordered by creation time.)
    <br> so create those matches you are interested in, and leave the rest to be auto generated over time.
    
    <br><br><a name="step4" class="anchor">.</a><br><strong>4. Results</strong>
    <br> There may well be a queue of matches to be played, but eventually matches will be displayed in the <%= link_to "View Matches",  games_path %> area,
    <br> these default to being ordered by played time (latest on top).
    <br> Clicking on them brings up more information, and the ability to download the results file.
    
   <br><br><br><strong>Why are games being played I didn't start?</strong>
   <br> Active submissions attempt to play every other submission to prove they are the best. 
   <br> This can take a long time, so it's best to specify a few matches that you are interested in.
   <br> Note auto matches are played latest vs latest first, so it is possible that the games you are interested in are going to be played sooner rather than later.
</p><commit_msg>tweek help. needs more work though<commit_after><h1>Help me, Obi-Wan, it's a wall of text</h1>
<p></p>
<p>
    <strong>How does this work?</strong><br>
    <a href="#step1">1) compile your submission.</a><br>
    <a href="#step2">2) upload your submission.</a><br>
    <a href="#step3">3) if there is a specific matchup you'd like to see then create a new game.</a><br>
    <a href="#step4">4) wait for the Match to be resolved and see the outcome and download the battle.</a><br>
    
    
    
    <br><br><a name="step1" class="anchor">. [invisible]</a><br><strong>1. Compiling your Submission</strong><br>
    Since we don't want to give away our clever strategies too easily, we only want to upload compiled jar files.<br>
    i.e. your code has been compiled and is no longer human readable.<br>
    <br> a) Download this <%= link_to "build_for_arena.xml", static_pages_build_for_arena_xml_url, :class => "themed_text" %>. 
    <br> b) Save it into your Battlecode Directory
    <br> c) Run ant -buildfile build_for_arena.xml -Dteam=team arena_build   (Where team == the package your team is currently in)
    <br><br> This will produce an arena_submission_team.jar file (of compiled code only) in your battlecode Directory
    <br> This is the file you need to upload.
    <br> Note team in the above command line is the folder in teams you are wanting to upload. 
    <br> This is the name this Competitor will be known by, so don't use teamnnn if you want to remain anonymous!
    </p>
    <br>
    <a name="step2" class="anchor">.</a><br><strong>2. Uploading your Submission</strong>
    <br>        Clicking on the upload Submission button will allow you to create a new submission.
    <br>   a) Upload your Jar file. 
    <br>        You upload the arena_submission_#teamname#.jar. 
    <br>   b) You have the option of adding your team name (or some sort of team name) if you'd like to declare who you are
    <br>        I'd recommend using the team name slot, it's always more fun to know who you are up against, but the choice is yours. 
    
    <br><br> <a name="step3" class="anchor">.</a><br><strong>3. Creating a Match</strong>
    <br> By default, every submission will play every other submission
    <br> however, this will take some time as the numbers of submissions grow
    <br> to the point that some games may never happen within the life time of the competition.
    <br> These auto played matches, will be played in reverse uploaded time order. i.e. the latest submissions will play each other first.
    <br> If there is a particular match you are interested in, then create a new match.
    <br> When specifying a new match, there is a team name option. Again this can be left blank,
    <br>but it might be interesting to see who is requesting what matches.
    <br> Matches created by users are always played first. (ordered by creation time.)
    <br> so create those matches you are interested in, and leave the rest to be auto generated over time.
    
    <br><br><a name="step4" class="anchor">.</a><br><strong>4. Results</strong>
    <br> There may well be a queue of matches to be played, but eventually matches will be displayed in the <%= link_to "View Matches",  games_path %> area,
    <br> these default to being ordered by played time (latest on top).
    <br> Clicking on them brings up more information, and the ability to download the results file.
    <br> If you are only interested in the games played by your latest submission, clicking on your Competitor in the
    <br> active competitors view will show only those games the curernt version has played
    
   <br><br><br><strong>Why are games being played I didn't start?</strong>
   <br> Active submissions attempt to play every other submission to prove they are the best. 
   <br> This can take a long time, so it's best to specify a few matches that you are interested in.
   <br> Note auto matches are played latest vs latest first, so it is possible that the games you are interested in are going to be played sooner rather than later.
</p>
{'fraction_non_alphanumeric': 0.09083988835320984, 'fraction_numerical': 0.004567368688150216, 'mean_word_length': 3.517478510028653, 'pattern_counts': {'":': 0, '<': 179, '<?xml version=': 0, '>': 181, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 6}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 6, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2490741', 'n_tokens_mistral': 2275, 'n_tokens_neox': 2219, 'n_words': 1148}