Олег Новосад “Mama, I am game architect. What’s next?”

7. ENTERPRISE IS ABOUT
BUSINESS
GAME IS ABOUT
EMOTIONS

8. Oleg Novosad
Game Developer @ Hornless Unicorn Entertainment Studio
Mobile Developer @ SoftServe
MAMA I’M GAME ARCHITECT.
WHAT’S NEXT?

9. Idea
Game
Design
PrototypeDevelopment
Feedback
GAME CREATION FLOW
Soft + Hard

10. Problem
Partitioning
Interface
creation
between
parts
Structure
Manage +
Flow
Use of
techniques
patterns,
platform
features
etc.
Technical
Specification
Development
Delivery
GAME ARCHITECTURE FLOW
80 / 20

11. GAME GENRE

12. SO WHAT?
Action Lots of fantastic button pushing, blood, explosions, hot girls (boys) etc.
Adventure The story matters, progress tracking
Strategy Nontrivial choices, decision making and lots of units
Simulation Optimization exercises, real-world behavior
Puzzle Hard analytic thinking (especially in Match-3)
Toys Software you just have fun with, it should be cute and emotional
Educational Learning by doing
Game genre usually describes the components of the game and
intercommunication between.

13. PARTS AND INTERFACE CREATION

14. ARCHITECTURE DESIGN
1. Prototyping
2. Hard architecture
3. Soft architecture

15. …your game is: world, player, entity, enemy, score, quest, menu etc.
THINKING IN TOKENS
TOKENIZATION

17. DESCRIBE TOKENS
• Token is ‘object’
• Think of every token you can think of
• Do not try match token on a language feature
• Build interaction matrix
• Symmetric
• Asymmetric
• Discard tokens you don’t need

18. ARCHITECTURAL GRANULARITY
Module
• Class
• Class
Module
• Class
• Class
Module
• Class
• Class

19. ARCHITECTURAL GRANULARITY
Character
• Player
• PlayerController
World
• GameManager
• UIManager
Weapon
• InventoryManager
• Item

20. BUILDING BLOCKS

26. PRIORITIES
• Speed
• Performance
• Flexibility
• Portability
• Maintainability
THE THREE LEAD BALLOONS
1. Bad management.
2. Feature creep.
3. Developer insularity.

27. THE SEVEN GOLDEN GAMBITS
1. Plan for reuse. Don’t reinvent the wheel.
2. Document. Don’t keep it in your head.
3. Design first, develop second.
4. Schedule. Make sure everybody knows the
targets.
5. Catch mistakes as you go along.
6. Control the degree of R&D.
7. Know when to draw the line.

28. ALL GAMES ARE THE SAME
Your
Unique
Game
User
interface Bidirectional
event
handler
Data engine
(graphics,
level etc.)
Dynamics
engine
(collisions
and physics)
Logic engine
(the heart of
the game)
Graphics
engine
Sounds
engine
Hardware
abstraction
layers
Game
configuration
system
Menu
system
Online and
help system
Backend

29. THANK YOU!