Join Norwegian Game Awards!
TEAM REGISTRATION DEADLINE - 1st FEBURARY 2019
HOW TO JOIN THE COMPETITION
THE TODO LIST FOR PARTICIPANTS
TEAM REGISTRATION - 1. FEB
The team must be registered before – 1st of Feburary. This registration is only about the members of the team. The game doesn’t have to be finished! This will give us an estimation of the amount of accommodation, food and stands.
GAME REGISTRATION - 1. MAR
The game must be registered before 1st of March. Read the rules down below. More information will follow. Just focus on the team reg. for now 😉
GAME SUBMISSION DEADLINE - 1st MARCH 2019
DO YOU NEED TO TRAVEL?
HOW TO APPLY FOR FINANCIAL SUPPORT
The travel to Trondheim has to be arranged by the team itself. The way we can support the team, is with a compensation for the travel. To find out if your team has the opportunity to get support, fill out the application below.
We have arranged free accommodation for traveling participants for NGA 2019. The team have to fill out the application down below to take advantage of this offer.
The application is a google form, connected to the button on the right. Please apply as soon as you have registered the team.
§1.1 Norwegian Game Awards (NGA) reserves the right to decide whether an entry may compete or not.
§1.2 NGA reserves the right to change the rules at any time, without waring. Larger changes will be announced at official channels.
§1.3 The participants have the responsibility to keep updated about the rules at any time.
§1.4 The deadline for game submissions during NGA 2019 is the 1st of March 23.59 Norwegian time (UTC +01:00). Entries submitted later than this may be ignored.
§1.5 Entries and participants may not be currently associated with, or sponsored by, a company in the games or entertainment industry. An entry that violates this rule will be disqualified. However, it is allowed to start a company associated with the entry. The rationale behind this rule is that this is to be kept a student oriented competition.
§1.6 The entry must not have been published by a publisher. Releasing the game independently is allowed.
§1.7 A playable demo – not necessarily a completed game – must be submitted by each team by the competitions deadline. This submission is referred to as the final entry. Additionally, each team is required to submit at least three (3) in-game screen shots, a game-play video or a trailer and a 100 word description of the game.
§1.8 Award nominees and winners are selected by the competition’s jury, with exception of “Gamer’s Choice”. The decisions cannot be appealed.
§1.9 Partners to NGA are not liable for lawsuit from participants of the competition regarding game ideas or likenesses to their own products, current or future.
§1.10 Teams may submit multiple game entries. This also means individuals may participate in multiple teams and entries during the same competition run.
§2.1 Entries must run on one of the following operating systems: Windows 7, 8 or 10, Linux (latest stable build of Ubuntu) or OS X (as a Universal binary). Emulators are permitted. Should your game need a gamepad or such, please contact one of the organizers.
§2.2 Entries targeting the mobile platform must run on one of the following platforms: Windows Phone, Iphone/Ipad or Android. The entry must be a native application. SDK emulators are also allowed.
§2.3 Entries are allowed to use existing technology (such as libraries, game engines, game makers, etc.) and existing media (such as images, 3D models, sound effects, etc.) However, teams must have the right to use the technology, media and trademarks, as well as the right to submit the final entry to SGA for judgement, i.e. respect copyrights and any applicable license agreements. This also means that modifications of existing games (“mods”) are allowed.
§3.1GA aims to promote ambitious individuals, looking to break in to the Norwegian game and/or entertainment industry. Therefore at least 50% of the team participating must be students with a Norwegian study and be an active in the development of the game.
§3.2 The submission can and should be tested by people outside the team. The testers can only give advise to improvements. If the testers become more involved in the development, they should be apart of the team.
§3.3 The registered team can add and remove members during the development. It’s not allowed to use §3.2 to remove the testers after implementing the improvements.