Contestants are challenged with creating a "Space Invaders" type of game.

• Gameplay mechanics and core logic should be written in C++.
• There should be three visually different enemy types, but all behave the same.
• An enemy can shoot if no other enemy is in front of it.
• Additionally a UFO will sometimes go across the top of the screen which the player can shoot for bonus points.
• Enemies move left or right as a group and shift downward and change direction every time they reach the screen's edge.
• Enemy group speed gradually increases as enemies are destroyed.
• The player has three lives.
• The game saves the highest score between sessions.
• In each advancing level the enemies start one row lower, unless already at the lowest possible one.
• Above the player are "bunkers" which get eroded when shot at by either the player or enemies, or if they get touched by enemies.
• Cite your sources in your code comments if you use code/methods from elsewhere.
• You're allowed to use Quixel Megascans or marketplace assets as long as they're assets only (no code or BP).
• Only one game entry allowed per participant (no team entries).
• Feel free to change the visual theme of the game (it doesn't have to be in space).

Create a game or application that addresses a global concern of either inequality or conservation. If you need ideas you can look at the UN Global Issues list. This can tell a story to teach others about a culture they may not understand, or aim to help drive real world change.

Tool Versions

Unity 2020 LTS or Unity 2021 LTS
You may use any IDE of your choice

App Requirements

• Game Mechanics and Core Logic should be written in C#
  
• Minimum of 3 types of objects that are interacted with to progress gameplay or application state these can be:
  
  • Collectibles
    
  • Enemies
    
  • Data entry points
    
  • Other objects
    
• UI Elements to report any needed player feedback such as:
  
  • High Score
    
  • Level Progression
    
  • Minimap/navigation
    
• The project should have states guiding it through beginning/middle/end. The application should handle the ability to restart should a completion or loss condition happen.
  
• Code should be appropriately commented and/or named
  
  • Show knowledge of standard gameplay programming patterns such as:
    
    • Singleton
      
    • State
      
    • Observer
      
• A playable build either as PC/Mac standalone, or WebGL - judges will need to be able to play your game.