2017 FCC Online Hackathon Rules

Team Composition

• Teams must be comprised of members of a local FCC group, or local coding group.
• There should be no more than seven members per team.

Theme

• This hackathon has a games theme, all entries must be HTML5 games playable online.

Timeframe

• This hackathon will be held on Saturday, May 6th. Teams are given the full 24 hours to complete their entries.
• This 24-hour period is determined by the local time zone of each team. Each team must include on their application what time zone that is.
• Github repos must reflect adherence to this rule.

Code

• All code must be written the day of the hackathon.
• No github repos shall be created prior to the day of the event.
• All code written in this hackathon is owned by the team that wrote it. If you would like to keep working on the project after the hackathon, it is up to you and/or your team. We will not claim copyright or ownership for anything written or created during this competition.
• All languages and frameworks are legal so long as they meet the requirements below:
  
  1. The game logic must be written by the hackathon team. Thus, no "drag and drop" game creation engines are allowed (eg. Spark, GDevelop).
  2. Game frameworks that simplify physics and other low-level functionality are legal (eg. Phaser).
  3. All games must be playable on the web as HTML5 games.
  4. No downloads or installation shall be required by users.
  5. Any frameworks used must be original, open source, or free-to-use. Paid frameworks are illegal.
• The spirit of these rules is that "the team writes the code." Final interpretation of this rule will be decided on by judges.

Art Assets

• Art assets must be original or free-to-use.
• Any original art created for your team is owned by you/your team. FCC-Remote-Hack will not claim any ownership for what you create.
• Art assets may NOT be created ahead of the event (This is to keep teams using original art and those using assets available online on equal footing.).

Entry Submission

• Entries are submitted as a link to a functional game, deployed online.
• Game must not require downloads or installation.
• Game code should be visible on Github. A link to this repo must be included in the submission.
• Only one entry per team.
• Games must not contain material that discriminates against or is grossly offensive to any race, gender, religion or sexual orientation. Judges will be the final arbitrators on this rule.
• Mature content is allowed but games should not be pornographic in nature. Judges will be the final arbitrators on this rule.

Judging Criterion

1. Judging is on a scale of one to ten in three categories, with one being the lowest score. A score of one should be reserved for games that are non-functional while ten would be a game that is a professional-quality effort.
2. The three scoring categories shall be:
   • Functionality
     1. Stability of the code
     2. Quantity and quality of game features
   • Artwork
     1. Overall aesthetics of the game
     2. Quality of animations
     3. Style and originality
   • Player Experience
     1. Quality of user experience
     2. Fun
     3. Quality and quantity of game content
3. Judges scores in each category will be averaged for each game, rounded to two decimal places. That game will then be given a total score based on these averages.
4. Placement in the competition will be in order of total score, from highest to lowest.