Contest: CTF Submission Instructions

Submission of CTF code is fairly straightforward (described below). Code will be stored and at midnight ever night, a double elimination will be run between all teams that have submitted code up until that point. (If no new code is submitted, the game won't be rerun: I want to conserve some CPU cycles for myself!). Or you can just view the results of the last-run double elimination.

Instructions

You must REGISTER your team by providing me with a faux uID (an arbitrary eight digit string). UofU teams should have ids of the form 1####### and Berkeley teams should have ids of the form 2#######. To register, send email to me with the subject line: CTF Registration. The body of the email should contain your desired team name (any string of alphanumerics) and desired (fake) uID. I'll write back confirming your registration.
To submit code, you must package it all up in a single zip file. To test if the zip file is "okay", you should be able to run the following test. Suppose you call the zip file /path/to/code.zip. Then you should be able to run:
```
cd /tmp
mkdir mycode
cd mycode
unzip /path/to/code.zip
python pacclient.py -a SOMEAGENT --agentArgs="SOMEAGENTARGS"
```
And everything should just work. I.e., unzipping code.zip shouldn't create any new directories or anything. You must also include all the code necessary to run it, including things like pacclinet.py. We provide an example using the baseline agents: default_code.zip.
You must create a file called config that tells us how to run your code. This file should have a very simple format, as in the following:
```
teamname:     __your_team_name_1__
agentfactory: OffenseDefenseAgents
agentargs:    
```
Note that you need the agentargs line even if you don't have any agent args (just leave it blank). We will read this in and run something like:
```
python pacclient.py -U $teamname -a $agentfactory --agentArgs="$agentargs"
```
where the $... means a value read from config.
Now you're ready to hand it in. Simply go to the handin page and enter your team name (from the registration email) as your "last name" and your fake uID as your student id. You need to attach three files: a partners.txt file that lists all the people in your team (yes, this is a bit redundant with registration, but oh well); your config file; and your code.zip file.