Judging criteria

This page is intended to give a brief overview of how we will judge each submission. This document is subject to change as we refine the judging criteria for this year's event.

For ten.java 2014, judging will be split into three categories:

• Idea (worth 75 points)
• Execution (worth 75 points)
• Code (worth 100 points)

Each plugin will be assigned to two judges and the mean of each sub-category will be calculated to try to minimize the chance of judge bias and/or other factors impacting results. The final score will be computed from the sum of each sub-category average. The maximum score is 250 points.

Idea

The criteria that form part of the idea category will revolve around scoring the idea that the developer has come up with. The idea category is made up of the following sub-categories:

• Idea originality (worth 15 points)
  • We're looking to see new ideas that haven't been done before or combinations/improvements on existing ideas. Well-known concept submissions with little additions/changes will receive low scores for this category.
• Conformance to theme (worth 30 points)
  • We want to ensure plugins do somehow relate to the theme. You don't need to take the theme 100% literally as we do want to encourage innovation and 'thinking outside the box'. Some connection will help you gain points here, though.
• Idea complexity (worth 10 points)
  • Simple plugin concepts that could be built in 10% of the contest time will not score well here. We want to encourage making full use of the ten hours and creating a well thought out concept.
• Fun/usefulness (worth 10 points)
  • This sub-category is concerned with how fun the concept is (for ideas such as minigames) or how useful the plugin is if the theme and concept are less about fun.
• Expansion possibility (worth 10 points)
  • This sub-category concerns how much the idea can be extended or added to. We want to reward ideas which have room for expansion and improvement.

Execution

• User-friendliness (worth 20 points)
  • In this category we want to reward developers who make an effort to provide a friendly experience to users.
• Absence of bugs (worth 20 points)
  • This sub-category deals with how bug-free the end result is and how the concept has been implemented.
• General plugin mechanics (worth 35 points)
  • This category is concerned with how well the developer has pulled off their idea.

Code

• Quality of code: Bukkit API use (40)
  • This sub-category deals with the quality of the developer's use of the Bukkit API. Are commands handled properly?
• Quality of code: General Java use (40)
  • This sub-category deals with the quality of the developer's general use of Java and general code quality. Code shouldn't be unnecessarily inefficient, repeated code should be abstracted etc.
• Documentation (20)
  • As well as line & JavaDoc comments, we're looking for a README which explains how the plugin works and how it should be used.