General rules

No time to wade through all the rules at this specific moment? Here's an executive summary of the most important guidelines:

  1. Team represents one country. At least one member of the team must be a citizen of this country.
  2. You can only be a member of one team and one team only. A team consists of one to three members.
  3. All team members need a valid passport, because the finalists will travel to Helsinki, Finland.
  4. In the manner of all sporting events, any unsportsmanlike conduct is grounds for disqualification. This includes any abuse such as DDOS, hacking, manipulating and copying attempts. Competitors or their bots are not allowed to disturb their opponents or the competition.
  5. You retain your rights to the code, but you agree that the organizers can use your code in connection with the competition. You agree that your code repository can be published by the organizer under Apache License v2.0 or any other open source license determined by you by changing the license in the repository.
  6. Bring it on!

See you at the pit stop...

1. Eligibility

All team members must be 18 years of age or older by the time of the finals on June 10th 2014. You can only be a member of one team. The language used in all communications between the organizers and the contestants is English.

Teams represents one country. At least one member of the team must be a citizen of this country. All team members must have passports valid up until at least July 10th 2014. Finalists will be required to travel to Helsinki, Finland for the onsite finals. Any finalist who is unable to obtain appropriate travel documents, such as a passport or visa, may be disqualified from the onsite finals and an alternative finalist may be selected.

Employees of Reaktor or Supercell and people directly involved in organising the contest are not permitted to compete.

2. Sign up

Sign up at starts on March 31st 2014 at 1 PM GMT+3. The sign up-form will be closed either on April 22th 2014 at 1 PM GMT+3 or when 10 000 teams have registered, whichever takes place earlier.

Contestants must provide their real contact information: name, email and BitBucket account name. The provided name must be the same name contestants have in their passport. Contestants can compete in only one team, competing in multiple teams leads to disqualification of all related teams. Teams must work on their own, sharing code between teams is not permitted.

After the sign up the organizers can publish information about the team such as team name, full names of team members, team picture, team story. Contact information such as BitBucket account name, email address, phone number will not be published.

All content provided by the team, for example text, code and pictures, must be suitable for publishing. The team must ensure that they have all such rights and permissions in the content as are required for providing the content to contest to be used and published in accordance with these rules. Any inappropriate, illegal or infringing content can lead to disqualification.

All content the team provides can be used for marketing purposes without notifying the team by the organizers of Hello World Open 2014.

In the manner of all sporting events, any unsportsmanlike conduct is grounds for disqualification. This includes any abuse such as DDOS, hacking, manipulating and copying attempts. Competitors or their bots are not allowed to disturb their opponents or the competition.

3. Contest structure

The coding time start on April 15th 2014 at 1 PM GMT +3 and ends on April 29th at 1 PM GMT+3. Once the coding time ends, all teams must have their working code in the master branch of the repository provided.

The competition is split into two rounds: the qualification round and the finals.

Qualification rounds take place within three regions on consecutive days -- May 6th, 7th and 8th 2014. First, teams compete against their fellow-countrymen. The best teams within each country compete against other teams within their Hello Region. The two best teams within each region will travel to the finals which take place in Helsinki, Finland on June 10th 2014. You can check your Hello Region from the map right here.

4. Awards

The teams that fight their way to the finals will receive a four-day, all-expenses paid trip to Helsinki, Finland. The trip will include great company, delicious food and one heck of a tour in the capital city of Finland.

The finals take place on June 10th. Supercell's second annual gaming summit will be held earlier the day.

The finalists will be awarded the following prizes:

1st place - 5000 euros
2nd place - 3000 euros
3rd place - 2000 euros
4th to 8th place - sponsor prizes

All eight finalist teams will get exclusive tickets to the to-be-sold-out tech conference of the year Reaktor Dev Day, worth 500 € / piece. More information on the conference. Travel and accommodations costs are not included.

The best 100 teams will receive tickets to the live finals in Helsinki (travel and accommodation not included).

We will also reward other well-performed teams not qualification for the finals with cool gear.

Additional Rules for Finals: In the event of a tie in the top three, the order of the tied teams are decided as follows: 1) Number of first positions, 2) Number of second positions, 3) Number of third positions. Should the teams be tied after this, a panel of judges will decide the final order.

5. Other

The competition is organised by Reaktor Innovations Ltd., Mannerheimintie 2, 00100 Helsinki, Finland (“Reaktor”).

Reaktor may change these rules, the contest or its prizes, at any time for any reason without incurring liability to any of the contestants. Such changes are notified via website. Reaktor may disqualify any contestant or team on the basis of their breach or suspected breach of these Rules or any other conduct deemed inappropriate by Reaktor.

The contest and any services related thereto are provided on an “AS IS” basis without any express or implied warranties. Reaktor is not liable for any indirect or consequential damages or losses. Reaktor’s liability in all circumstances is limited to 50 euros.

The contest, these rules and any related contract are governed by Finnish law. Any dispute, controversy or claim arising out of or relating to the contest, these rules or any related contract, or the breach, termination or validity thereof, shall be finally settled by arbitration in accordance with the Rules for Expedited Arbitration of the Finland Chamber of Commerce. The seat of arbitration shall be Helsinki, Finland. The language of the arbitration shall be English.

Technical instructions

Code an AI for a race car

The goal is to create an AI for a simple real time racing game. Your AI will sit on the drivers seat of a racing car and race against others AIs on different virtual tracks. The server will send you track details and car positions and your job is to send car control messages to the server. You'll communicate with a game server using JSON over TCP. More details will be delivered later.

When the competition starts each team will be provided with

  • Access to a private BitBucket Git repository with a simple bot implementation in their preferred programming language
  • Instructions about the communication protocol used by the game server and the bot
  • Access to game servers where they can test their bot and compete against other bots
  • Continuous Integration (CI) process that tests the bot daily. The process builds the bot from Git repository and runs it through a few test races.

Additional information
  • Programming languages that are currently available for selection are C, C++, C# / Mono, Clojure, CoffeeScript, Erlang, F#, Haskell, Java, JavaScript, Lua, Perl, PHP, Python, Rust, Ruby, Scala, Go. At the moment, due to technical reasons, we cannot 100% guarantee that all of these will be supported, but we'll do our best. You can change the programming language at any time.
  • Bot code must be pushed to the team's repository. The version in the master branch in Bitbucket will be used in the qualification round.
  • Push early and often to Bitbucket to get feedback from the CI process that will run at least daily to make sure your bot is good to go.
  • The CI and the qualification round are run on a virtual Linux server. Bot must pass the CI process to get access to the qualification round.
  • All external dependencies must be included in the repository but keep the repository size down. The CI and competition servers do not have access to the public internet.
  • The AI must have have near real time performance on CI and qualification round. Slow response time is grounds for disqualification.
  • In the finals, the bots are run from contestants' own laptops.
  • Code quality is important. Please keep your codebase clean.
  • Additional instructions are sent via email to all participants.