* The maximum number of hackers per team is limited to 4.
* Teams should be made up exclusively of students who are not organizers, volunteers, judges, sponsors, or in any other privileged position at the event.
* Teams can of course gain advice and support from organizers, volunteers, sponsors, and others.
* Teams can use an idea they had before the event.
* Teams can work on ideas that have already been done. Hacks do not have to be “innovative”. If somebody wants to work on a common idea they should be allowed to do so and should be judged on the quality of their hack. These days it’s hard to find something that’s fully original and teams might not know an idea has been done before anyway.
* Teams can work on an idea that they have worked on before (as long as they do not re-use code).
* Teams can use libraries, frameworks, or open-source code in their projects. Working on a project before the event and open-sourcing it for the sole purpose of using the code during the event is against the spirit of the rules and is not allowed.
* Adding new features to existing projects is allowed. Judges will only consider new functionality introduced or new features added during the hackathon in determining the winners.
* Teams must stop hacking once the time is up. However, teams are allowed to debug and make small fixes to their programs after time is up.
* Projects that violate HackCU's Code of Conduct are not allowed.
* Teams can be disqualified from the competition at the organizers' discretion. Reasons might include but are not limited to breaking the Competition Rules, breaking HackCU's Code of Conduct, or other unsporting behavior.