Additionally we added a different subtree displaying the structure of a game. This subtree is supposed to show the structured form the game uses to present its content. A key distinction to be made was a game being a match or a game containing matches. Especially for this we added the match based identifier, which allows us to tag the structure of a game as what the player regularly encounters i.e. during a match, while indicating that the game has matches that most likely offer the same content repeatedly. In contrast to that, the cyclic tag provides the user to tag games that encourage the player to repeat the game after a playthrough by providing information or assets that can be migrated to the next playthrough i.e. via new game+ modi. Furthermore we added order to indicate the manner in which the content can be consumed. For the open tag the player must be able to freely choose in which order actions are taken, resulting in missable content or such.
For now we define cyclic as 'The game is designed in a way that can be experienced to full extent only by replaying the game a large (but not concretely defined) number of times'. This should be seen mostly disconnected from concerns of replayability and motivation/incentive/rewards. We use the above list as a basis for tagging the game structure in the next tagging round and will revisit it afterwards for evaluation.
Spawned by:
50
Related issues:
40
42
53
55
01.06.2024 Discussion
narrative(Banner Saga / Starcraft)treelikeworld/ parallelnahtlos)continuous
match based
homogen
continuous
match based
homogen
cyclic :red_circle:
continuous
match based
homogen
cyclic :red_circle:
continuous
homogen
continuous
homogen
continuous
heterogen :red_circle:
continuous :red_circle:
heterogen
paketweise :red_circle:
heterogen
paketweise :red_circle:
continuous:no_entry:heterogen
continuous
homogen
continuous
heterogen :red_circle:
continuous
homogen
continuous :red_circle:
homogen
paketweise :red_circle:
homogen
paketweise :red_circle:
continuous:no_entry:homogen
cyclic :red_circle:
continuous
match based
heterogen
paketweise :red_circle:
continuous
match based
heterogen
cyclic :red_circle:
paketweise:no_entry:continuous
match based
heterogen
cyclic:no_entry:continuous :red_circle:
match based :red_circle:
homogen
paketweise :red_circle:
homogen
open :red_circle:
paketweise :red_circle:
continuous:no_entry:homogen
continuous
homogen :red_circle:
continuous
heterogen :red_circle:
open
paketweise:no_entry:continuous
homogen :red_circle:
heterogen:no_entry:continuous
homogen
continuous
homogen
paketweise :red_circle:
continuous:no_enty:homogen
heterogen
paketweise
heterogen
paketweise
heterogen
paketweise
continuous:no_entry:heterogen
continuous :red_circle:
homogen
paketweise :red_circle:
continuous :red_circle:
homogen
open :red_circle:
paketweise :red_circle:
continuous:no_entry:heterogen :red_circle:
continuous :red_circle:
homogen
paketweise
homogen
paketweise
homogen
continuous
match based
homogen
continuous
match based
homogen
continuous
match based
homogen
cyclic :red_circle:
continuous
homogen
continuous
homogen
branches:no_entry:paketweise :red_circle:
heterogen :red_circle:
continuous
homogen
continuous
homogen
cyclic :red_circle:
linear:no_entry:branches :red_circle:
continuous
homogen
heterogen:no_entry:paketweise
homogen
paketweise
homogen
paketweise
homogen
heterogen:no_entry:paketweise
homogen
paketweise
homogen
paketweise
homogen
heterogen
continuous
homogen
continuous
homogen
continuous
homogen
cyclic :red_circle:
continuous
homogen :red_circle:
continuous
heterogen :red_circle:
cyclic :red_circle:
continuous
heterogen :red_circle:
continuous
homogen
continuous
homogen
branches:no_entry:open:no_entry:paketweise :red_circle:
continuous:no_entry:homogen
Related Changes
Open questions
15.04, Tree Iteration IV: