Frequently Asked Questions

Registering for an account allows you to post to the forums and scrimmage other contestants. It also enables you to compete in the open tournament at the end of March, where you can gain fame (and riches if you are a tsudent at a participating university). If you're an MIT student, you are also eligible to compete in the MIT tournament at the end of January, where top finishers receive cash prizes and eternal glory.

After you register, you will be able to create and join teams, and invite other contestants to join your team, from the "Team Options" page.

If you want to participate in 6.370, but don't yet have a team, you can register individually, and then post to the forums or use private messages to find other teammates. If you already know who you want on your team, you can have one person register, create the team, then invite the other teammates to join that team.

6.370 is an MIT class, so MIT students can register and receive credit as they would for any other class. We are working on getting transfer credit for other universities. However, we have been unable to grant credit in the past.

To get credit and EDPs, you must join an MIT tournament team. This means you must register using a college email address. In addition, for MIT students, you must use your Athena username address, not a mailing list.

You are not required to attend the "first class" -- the unfortunate wording in the IAP guide is automatically generated. However, you are required to attend the final tournament on February 1^st. If you are a finalist, you are also required to attend the finalists' celebration on January 31^st. Attendance at the final tournament is absolutely mandatory, regardless of your team's performance.

In addition to the tournaments, we will be holding a few class sessions to teach you some tools and tricks for writing players. Check the calendar as IAP approaches for details about these sessions.

It is possible to compete in 6.370 even if you can only be on campus starting Feb. 1, because all announcements and information that are crucial to the competition will be available through the website. However, we expect that you will want to watch your player in action at preliminary tournament on January 30^th and the practice tournaments held in January, as well as see what the other teams have come up with. Finally, we encourage you to attend our "classroom sessions", where the devs can answer your questions and talk about the BattleCode game.

There will be three tournaments at the end of IAP (all for the MIT tournament). The Seeding Tournament will determine your seed for the Qualifying Tournament. The Qualifying Tournament will narrow the field down to eight teams. The Final Tournament, played among the top eight teams, will determine this year's BattleCode winners.

The number "6.370" was actually made up as a name for the competition (only at MIT...). Because the competition is also a class taken for credit, it is listed in the catalogue with an official course number, 6.187: Special Laboratory Subject.

You'll need the number 6.187 only when you register on WebSIS. For all other purposes, the competition will be known as "6.370".

We recommend that you register both on WebSIS and on the 6.370 web site. Registering on the 6.370 site is mandatory, but registering on WebSIS is only required if you are an MIT student and wish to receive credits or EDPs.

Yes. The 6.370 game changes enough from year to year that writing a successful player is always considered a new design challenge.

There are a couple requirements for getting credit in 6.370. First, attendance at the Final Tournament on Fri. Feb. 1 is mandatory in order to receive credit. Second, if your team is one of the top eight in the Final Tournament, you must attend the Finalists' Celebration to get credit.

With those requirements taken care of, there are a couple ways to earn credit (and EDPs) for 6.370. The main avenue is to beat the "reference player," a basic player written by the devs.

Specifically, soon after the final submission deadline, we will take your final submission and run it against the reference player on two sets of 3 different maps (we will announce which maps they are a few days before the submission deadline). If your player beats the reference player on 2 out of the 3 matches in either set, your whole team gets credit and EDPs. Because you can run these matches yourself, you should know in advance whether your submission will beat the reference player.

If your submission does not beat the reference player, we will email you soon after the submission deadline. At this point, you can get credit an alternate way, by sending us a 2-page report on your player: its code design, how it works, an explanation of any AI paradigms you used, etc. We will look over your source code and your report, and if both show a significant amount of effort, thought, and good design techniques, we will give you 6 credits and 6 EDPs.

Most contestants find that the reference player is easily beaten. If you find that you have other time commitments or can't beat the reference player, IAP guidelines allow you to drop 6.370 without penalty up until very late in IAP.

EDPs are Engineering Design Points. They are a part of the old course 6 curriculum that is being phased out. Chances are if you don't know what they are, it's because you don't need to.