You can show kaitiakitanga by: 

• understanding the issue

• Finding out about the problem(s)

• Considering the people who might be affected by the problem and who might care about a solution (stakeholders)

• Making sure you don’t damage or hurt or insult any person, thing or business. In the making of your outcome this includes things like getting copyright free images and checking information is true, up to date and valid.

You can show manaakitanga by:

• Talking and listening to people who have an interest in the issue

• Talking and listening to people who may be affected by the the outcome

• Making changes based on suggestions by the above mentioned people

• Using good valid and impactful content that does a good job of getting your message across

• Not using content that hurts, insults or harms others

• When pictures or content is not yours, make sure you credit the creators 

Video games are not just for entertainment. 

Think of games as ways to create an “experience” for your intended players. From “horror” games that keep them on the edge of their seat to “boomer shooters” that make them feel ultra-powerful, games are experiences. 

If you try to imagine how you want your player to “feel” you’ll come up with a much better purpose than just entertainment.

Watch the video to the left for more on this.

• Platformers (Easiest option)

• Top Down games

• Endless runners

• Point and Click games

• One Mechanic games (Flappy Bird, Frogger, or Super Hexagon for instance)

1. Make a multiplayer game.

2. Not have clear ideas on how the enemy AI will work.

3. Having a complicated story or characters.

4. Having more than a handful of different things you need to animate/draw/design.

5. Insufficient planning.

Introduction to flow charts

https://lucid.app/ 

Example of a game flow diagram

Requirements are like the rules a game has to follow to make players happy and meet the project's goals. They tell us what the game needs to do and set limits on what we need to accomplish. There are different types of requirements:

• Functional Requirements: These rules say what the game has to do. For example, "Players must control a character like in a platformer game" or "Players need a health system where they lose health when attacked and can get it back by picking things up."

• Non-Functional Requirements: These are about how well the game should work, like how fast it should run, how reliable it is, and how safe it is. For instance, "The game needs to run at least 30 frames per second on all devices."

• Quality of Life Requirements: These rules focus on how players feel when they play the game. This includes things like easy controls, smooth animations, clear tutorials, and menus that respond quickly.

• Compatibility Requirements: These rules make sure the game works right on certain devices and software setups.

Specifications are super-detailed descriptions of a video game. They tell us exactly how the game should work and what it will look like:

• Technical Details: This tells us , like what kind of game engine it uses, where you can play the game (on a computer, game console, or phone), how good the graphics and sounds will be, and if you can play with friends online.

• Gameplay Mechanics: These are the rules for how the game works. How you move and do things, what your goals are, how you go from one level to another, and if there are special things like playing with others or computer-controlled characters.

• User Interface (UI) and User Experience (UX): This part is about how the game looks and how you interact with it. It includes menus, buttons, maps, and anything you see or click on while playing.

• Art and Design: This is all about how the game looks, including the characters, the world they're in, the animations, and special effects that make the game look cool.

• Sound and Music: Here, we talk about the sounds in the game, like footsteps or explosions, and the music that plays in the background. It's what makes the game sound great!