Difference between revisions of "Goal Hierarchies"

Revision as of 15:03, 25 January 2018

Structures of goals where the completion or non-competition of certain goals affects the possibility to complete other goals.

One of the typical design elements of games is goals. These provide players with motivation to perform various possible activities within the game system and to provide more details and sequences to these activities the goals can be organized so they build upon each other. Since this typically means that some goals can only be completed by first completing other goals, they often create Goal Hierarchies. These can let players have long-term and short-term goals that are interrelated or let players be provided with goals during gameplay as they progress through the Goal Hierarchies.

Examples

A good example of a Goal Hierarchies can be found in Zelda: A Link to the Past. At the start, Link is given the task of rescuing princess Zelda from the castle. After accomplishing this, Link is presented with a more elaborate quest of overcoming the evil wizard Agahnim. The subgoals of this task, such as freeing the seven maidens, are gradually revealed to the player during the gameplay and, near the end of the game, it is revealed that it is not Agahnim, but Ganon from the Dark World, that Link has to overcome.

Chess can be seen as a loosely defined implicit Goal Hierarchy. No pieces need to be captured from the opponent, nor any strategic locations occupied, to be able to checkmate the opponent's king. However, it does make the goal of checkmating easier, and nearly all players focus on achieving these subgoals before attempting to achieve the main goal.

The rough Goal Hierarchy in Pac-Man is as follows: eat the pills while avoiding the ghosts, get the power pill while avoiding the ghosts, chase the ghosts or eat the pills while under the influence of the power-pill, finish levels by taking all pills on each level, and finally get into the high score list.

Using the pattern

Can Modulate

Companion Quests, Enemies, Traverse

The most common way of constructing Goal Hierarchies is to create a structure where fulfilling the most accessible goals — leaf goals — leads to fulfilling other branch goals. Variations of this includes that completing leaf goals only makes possible or makes easier the completion of branch goals or that there are several mutually exclusive branch goals on the highest level. Goal Hierarchies may also have different branches that split off from each other but rejoin later (e.g. succeeding in unlocking a door may allow the two goals of collecting parts of a code that together allow the hacking of a computer). More complex variants are possible but unusual, e.g. a cycle of inner goals that all can be started to be completed as soon as a dedicated leaf goal or the previous inner goal in the cycle have been completed. A goal that is used as a leaf goal becomes a Supporting Goal since it has a relation to a branch goal. Of course, Supporting Goals may also be branch goals to leaf goals, so Supporting Goals can both be modulated by Goal Hierarchies and modulate it. An obvious candidate for the inner-most goal in a |Goal Hierarchy is the Main Goal of a game.

Basically any goal can be a leaf goal in a Goal Hierarchy. The most basic branch goal is the one that simply requires the fulfillment of all leaf goals associated with it. Selectable Set of Goals is a variation of this which allows a certain number of the leafs to be unfulfilled.

Other more specific branch goals can be created through using

Can Be Instantiated By

Achievements, Capture, Collecting, Continuous Goals, Factions Grind Achievements, Levels, Minigames, Narration Structures, Optional Goals, Predefined Goals, Quests, Speedruns, Stimulated Planning, Supporting Goals, Tournaments

Herd together with One-Way Travel

Can Be Modulated By

Clues, Dynamic Goal Characteristics, Excluding Goals, Save Points, Strategic Knowledge, Unknown Goals

Quick Games can be difficult to combine with Goal Hierarchies (at least complex ones) since there simply may not be enough gameplay time to handle many goals and relations between them. Completing a Quick Game can however of course be a leaf goal in a Goal Hierarchy.

Diegetic Aspects

Interface Aspects

Narration Aspects

Consequences

Goal Hierarchies often lead to Complex Gameplay since not only the structures suggest a more detailed relationship between goals in a game but can also make players need to think about these structures and how they wish to traverse them. Higher-Level Closures as Gameplay Progresses is also a common consequences of a presence of Goal Hierarchies in a game, at least as long as goals lower down in the hierarchies need to be completed before higher ones (or are the way higher ones can be completed). And, while Narration Structures can be the origins of Goal Hierarchies the opposite can be true in that Goal Hierarchies suggest or can work as the starting point for Narration Structures. One place where these consequences can merge is in games with Factions; here Goal Hierarchies involving the Factions is extra likely to create Higher-Level Closures as Gameplay Progresses that quite unavoidably also affects any narration.

Relations

Can Instantiate

Complex Gameplay, Higher-Level Closures as Gameplay Progresses, Narration Structures

with Factions

Higher-Level Closures as Gameplay Progresses, Narration Structures

Can Modulate

Companion Quests, Enemies, Main Goals, Supporting Goals, Traverse

Can Be Instantiated By

Achievements, Capture, Collecting, Continuous Goals, Factions Grind Achievements, Levels, Minigames, Narration Structures, Optional Goals, Predefined Goals, Quests, Speedruns, Stimulated Planning, Supporting Goals, Tournaments

Herd together with One-Way Travel

Can Be Modulated By

Clues, Dynamic Goal Characteristics, Excluding Goals, Save Points, Selectable Set of Goals, Strategic Knowledge, Unknown Goals

Possible Closure Effects

-

Potentially Conflicting With

Quick Games

History

An updated version of the pattern Hierarchies of Goals that was part of the original collection in the book Patterns in Game Design^[1].

References

1. ↑ Björk, S. & Holopainen, J. (2004) Patterns in Game Design. Charles River Media. ISBN1-58450-354-8.

Acknowledgements

-