90 likes | 213 Views
CT60A7000 Critical Thinking and Argumentation in Software Engineering Patterns in Game Design Chapters 1-2. Jesse Yli-Huumo , 0326806 Ville Kytömäki , 0326660. Introduction. Purpose of book is to give a tool for understanding and creating games .
E N D
CT60A7000 Critical Thinking and Argumentation in Software Engineering Patterns in Game Design Chapters 1-2 Jesse Yli-Huumo , 0326806Ville Kytömäki, 0326660
Introduction • Purpose of book is to give a tool for understanding and creatinggames. • Help to make design choiceswhencreatinggame. • Therearedifferenttools for designing and analyzinggames. • Bookfocuses on themostessentialpart: Gameplay. • Gameplay: Structures of playerinteractionwiththegamesystemand otherplayers.
Gamedesingpattern • Collectionof possible design choices in games. • Examplepatterns: Bossmonsters, levels, weaponsetc. • Eachpatterndescribes a part of theinteractionpossible in game. • Togetherwithotherpatternstheydescribethepossiblegameplay in thegame.
Gamecomponentframework • Book presents a framework for describing games based on the activities of the player • The framework provides the concepts about the physical and logical components of game design • These components are used to describe the game design patterns. • Framework is based on an idea that player makes quantitative changes in the state of the game
Holisticcomponents • Player concentrates on the all components working together and not as single components • Game instance : Everything from starting the game to closing the game • Game session : Player specific activity • Play session: In long and complex games, time spent for playing is divided
Boundarycomponents • Limits the actions of the players. • Rules: Describe and lay out theboundaries of thegame. • Modes of play: Manygameshaveseveraldifferentmodes of play. • Goals and subgoals: Giveplayermotivation for theiractions.
Temporalcomponents • Describesflow of thegame. • Actions: Player input to thegamestatethroughownactions. • Events: Gamestate output throughactions. • Closures: Quantifiable and meaningfulplayerexperiences. • Endconditions: Requirements for ending a state is fulfilled. • Evaluation functions: Algorithms for determiningtheoutcome of game.
Structuralcomponents • Basic partsthataremanipulatedbyplayers and system. • Gamefacilitator: Setsupthegame and synchronizesthegamestateduringthegameplay. • Players: Person(s) playing thegame. • Interfaces: Givinginformationaboutthestate and possibleactions in thegame. • Gameelements: Physical and logicalcomponentsthataremanipulatedbytheplayers. • Gametime: Timeline to describethegameevents.