Constraints
You must design and build your game within the given constraints. The constraints are deliberately chosen to get you considering deeper designs, and to help remove the blank canvas syndrome.
- You can only use a single button as the input for the entire game
- It must be an action mapping
- No axis mapping is allowed
- No analog sticks or triggers are allowed
Advice
It can seem daunting to be given creative constraints and be mandated to create a game within them. Constraints can actually increase your creative output if utilized correctly. Lean into the constraints and think of clever ways to apply the theory.
- Overloading - A button can change what action it performs depending on the game state.
- Button States - A button has both a pressed and released event.
- Held Length Contexts - A button can perform different actions depending on how long the button is held down.
- Button History - If you store the history of inputs, you can change which action the button will perform.
Rules
These rules are steadfast and unbreakable. Abide by them.
- You must submit your game before the deadline.
- You can only use assets that you have a license to use.
- The majority of game has to be original.
- Respect your team members' roles.
- Keep the scope of the game small - try to focus on a single feature.
Judging Criteria
These are the areas the staff will be judging your games on. Keep this in mind when designing and building your games.
| Concept | Design | Functionality | Aesthetics |
|---|---|---|---|
| Fitting the theme | Compelling | Technical challenge | Visual |
| Creativity | Fun | Stability | Audio |
Previous Examples
It can be difficult to create something without a quality target or example. So here's a collection of One Button Games that previous student groups have created. Go and play them to see what your predecessors have created.
We expect you to surpass them. 😊
Submissions(3)
No submissions match your filter
