Game Design School online course Game Design School Game Design School Home Home
Concept
Be Unique
Game Design Canvas
Concept Document
Do Market Research
Utilize Your Theme
Know Your Target Group
Platforms
Mechanics
Goal & Objective
Challenge
Metagame
Features
Story In Games
Design
Basic Game Loop
Components Of A Game
Learning Curve
Communication To The Player
Design Document
Level Design
The Checklist
Bad Games
Where Your Design Fails
Good Design Principles
Game Design Guidelines
Working
Game Design Process
Being A Game Designer
Designer Requirements
Working As A Game Designer
Vision Must Exist
Core Extended Wishlist
Redesign A Classic
Biggest Designer Problems
Inspiration
Production
Game Production
Production Outline
Feature Presentation
Making Games
Roles In The Team
Use Priorities
Metrics
Playability Evaluation
Game Design Canvas Game Design Canvas Game Design School Videos to study Videos & Templates Game Design School Pricing Pricing Game Design School Login Login ☰ Sign Up


Game Design School - USE PRIORITIES

You need a Membership to view this content. Select your Membership from here!

Course Contents









USE PRIORITIES

xxxHEADERxxx

After this page:
  • You understand to prioritise all features in the future for a production
  • You know how the game evolves during production
  • You understand that you might have to drop something suddenly and see how that will affect the game

PRIORITIES

I've done about 100 published games. After doing so many games something happened to me regarding how I see the games.
I see a game as a bunch of components / features we want into the game and these all depend on each other. See also
We want to have all these great features but somewhere is the reality of time. Somewhere we need to divide which components are in and which out. How easily they drop to the out part is to do with their priority.
Most the priority features are the ones you'll never drop - these are also your core.

PRIORITIES

I've done about 100 published games. After doing so many games something happened to me regarding how I see the games.
I see a game as a bunch of components / features we want into the game and these all depend on each other. See also
We want to have all these great features but somewhere is the reality of time. Somewhere we need to divide which components are in and which out. How easily they drop to the out part is to do with their priority.
Most the priority features are the ones you'll never drop - these are also your core.

img/game_production_priorities.jpg

img/game_production_priorities.jpg

Here in this sample game we might realise during production at some point that we cannot do the storyline, it's just too big. What can we fit if anything? Maybe Multiplayer? No, that require more additional supporting features, but we have some achievements and those would support the core gameplay so let's do that!
So this is what happens in the designers mind during production. Each feature is prioritised based on

  • how valuable it is for the final game how much time it takes to create
  • how much dependency it has and requires from other features
It's a constant puzzle.

Here in this sample game we might realise during production at some point that we cannot do the storyline, it's just too big. What can we fit if anything? Maybe Multiplayer? No, that require more additional supporting features, but we have some achievements and those would support the core gameplay so let's do that!
So this is what happens in the designers mind during production. Each feature is prioritised based on

  • how valuable it is for the final game how much time it takes to create
  • how much dependency it has and requires from other features
It's a constant puzzle.