Gamasutra: The Art & Business of Making Gamesspacer
View All     RSS
October 24, 2014
arrowPress Releases
October 24, 2014
PR Newswire
View All
View All     Submit Event

If you enjoy reading this site, you might also want to check out these UBM Tech sites:

The Perception of Roles In Game Systems
by Mark Venturelli on 08/07/11 12:49:00 pm   Featured Blogs

The following blog post, unless otherwise noted, was written by a member of Gamasutra’s community.
The thoughts and opinions expressed are those of the writer and not Gamasutra or its parent company.



In “Communication Design”, professor Jorge Frascara [2007] states that all design generates communication situations – not only objects, but events in which people interact with the design. The idea of the designer as a communicator isn’t novel in any way: the act of design is, by morphology, associated with designate – to signify, to imbue with meaning. Nonetheless, it’s a concept rarely discussed in the field of game design.

Frascara’s work has another concept that is even more interesting to game designers: the most important aspect of the communication between the designer and the public is not the act of communication itself, but the impact that it has “on the knowledge, the attitudes and the behavior of people” [Frascara 2007]. In this article I propose a few lenses to look at how the different ways a game designer can communicate his or hers systems may affect players’ mental models and, consequently, the way that the game experience plays out.

In the next sections I’ll try to outline the concept of roles of objects in a game system, the basics of space of possibility and decision-making in games, and how the perception of roles change the game experience. I will also do case studies of successful games such as Relic’s Dawn of War 2 and Richard Garfield’s Magic: The Gathering.

Semiosis and Choice

All human beings live in worlds they construct for themselves by semiosis, defined by Peirce as the production and interpretation of signs [Atkin 2010]. Perception is our only interface with the “real” world around us, and while the actual process of semiosis is infinitely complex and sometimes chaotic, the underlying concept is a fairly simple triadic representation: a sign (object) mediates what it represents (or what it is intended to represent) and the way it is interpreted (the impact on the interpretant).


Fig. 1 Adapted from Lucy Niemeyer’s presentation “Semiótica Aplicada ao Design”


The act of playing a game, on the other hand, is composed of a series of decisions that are taken based on, roughly, four steps that players take:

1)    Interpretation of the current state of the game;
2)    Interpretation of the space of possibility of the current state;
3)    Model of an ideal future state of the game;
4)    Judgment of the most adequate action or set of actions to achieve the desirable state;

While it is common to believe that playing a game “well” means excelling at the last step of decision-making, it is interpretation that provides the basis to work with. That is, a wrong interpretation of the game state and/or of the space of possibility may lead the entire process towards frustration and “bad decisions”. The first two steps, then, are more interesting for our discussion, as they form players’ mental model [Norman 1988] of the game. A mental model is a “thought reconstruction” of how something works in the real world, built by experience, training and instruction [Norman 1988] – a model built by semiosis.

It is pertinent, then, to discuss game state and space of possibility a little more in-depth. The game state is clearly and concisely explained in “Rules of Play”:


“(…) the game state represents the current condition of the game at any given moment. In a Chess game, for example, the game state is represented by the arrangements of the pieces on the board, the captured pieces, and which player is about to move next. In a console fighting game such as Virtua Fighter 4, the game state includes which two combatants were chosen, the health and other fixed and variable stats of the two fighters, their relative spatial positions, and the arena in which they are fighting. The game state is a formal way of understanding the current status of the game, and does not take into account the skills, emotions, and experience of the players. (…) the game state refers only to the formal, internal condition of the game.”

[Zimmerman and Salen 2004]

Space of possibility is the space of possible action that players explore in a specific moment in the game [Zimmerman and Salen 2004]. In a game of chess, for example, it covers every legal movement of every piece that the player controls within a game state. It is the collection of all possible actions and outcomes inside the designed space of the game – all actions and outcomes artificially made possible by the system [Venturelli 2009]. Interpretation of the space of possibility is a concept deeply related with the idea of affordance -  everything that an object or system can offer, support, furnish [Gibson 1986].

Roles In Game Systems

Every game is a system, thus every object that composes it has a role to play on that system. A role, as I’ll develop throughout this article, can be more or less subjective, more or less dynamic, but it represents a meaningful way with which an object affords change or prevention of change on the game state. In badly designed games (or games that have been deliberately designed like this), not all objects have roles. Ideally, good game design guarantees that all objects are integrated into the system to provide players with meaningful decisions [Zimmerman and Salen 2004], that is, decisions which affect the game state in a way that influences future decisions.

Roles can be designed to be more or less extrinsic or intrinsic. It is simpler to understand the concept by analyzing the extremes. Completely intrinsic designs creates constructed, explicit, static game experiences. Completely extrinsic designs create emergent, implicit, dynamic experiences.

The classic game of Rock, Paper, Scissors is an example of a completely intrinsic role design. There are three objects in the game system, and their roles are as follows:

1)    Rock: beats Scissors, gets beaten by Paper, ties with Rock;
2)    Paper: beats Rock, gets beaten by Scissors, ties with Paper;
3)    Scissors: beats Paper, gets beaten by Rock, ties with Scissors;

Each object has one clear role that players must know to understand the rules of the game, these roles never change, and objects never have different roles. This game is, then, a completely intrinsic role design – all roles are determined by the system regardless of player strategies, mental models and game state.

It is important to note that objects in the system are not the only element that affects the way decisions are made. For example, in the game of Rock, Paper, Scissors there is a very simple layer of metagame that makes it fun – thus, playing Rock just after a Rock vs. Rock play has its own meaning regardless of role. Just as it would if you were playing against an opponent that is known for always starting the game by playing Rock. The concept of roles is powerful and useful, but it only exists on the system level of a game.


On the extremely extrinsic role designs side, the ancient game of Go is one of the best examples. In Go, every object is symmetrical to each other – there is no “special” piece. Roles exist, but they are completely determined by player strategy and game state. For example, a piece put near the end of a clear diagonal has a role, on that game state, of “marking the territory”. This role is completely situational, since another piece put next to it may invalidate or change it completely. The system does not dictate roles out of the box: they happen dynamically during gameplay.

Roles are not to be mistaken by mere asymmetry between objects, but asymmetry does play a part in making role designs less extrinsic. In Chess, for example, each type of piece has its own rules of movement, but theoretically any piece can be used to capture any other and to execute any play. In practice, however, the asymmetry of movement and starting positions of the pieces creates unique roles for them in gameplay, even though many overlapping roles exist.

Most designs sit in the middle of the two extremes. Classic RPG combat, with its “Tank-Healer-DPS” roles, is more intrinsic, while Chess or strategy games such as Starcraft are more extrinsic. The concept of dynamic extrinsic roles will be further developed in the next section.

The Perception of Roles

Playing a game is a dance of pattern recognition – it’s about signifying and creating mental models. Our brain is pretty good at that: “the destiny of games is to become boring, not to be fun. Those of us who want games to be fun are fighting a losing battle against the human brain because fun is a process and routine is its destination (...). All of this happens because the human mind is goal driven” [Koster 2005]. As I’ve wrote previously:

“Our brains are constantly trying to optimize information, simplify it, put everything in little boxes inside of our heads. We create and refine patterns throughout our lives to identify facial expressions, written and spoken words, odors, everything that can be perceived by our senses. It is through this process that we have meaning. Playing games is not different. When playing Space Invaders, for example, a player is constantly trying to figure out the patterns for the enemy ships' movements, the trajectory of his shots, the best way to destroy the first rows of enemies as fast as possible, and so on.”

[Venturelli 2009]

The artificiality of game systems is one of the main reasons why this intense process of semiosis occurs – and arguably why the act of playing games is so compelling. Zimmerman and Salen [2004] relate the process of entering a game as a step into a “magic circle” where objects have new meaning – a pair of sandals is no longer a piece of attire when it is used to mark the scoring zone of a Sunday soccer game.

“What does it mean to enter the system of a game? How is it that play begins and ends? What makes up the boundary of a game? (…) At stake is an understanding of the artificiality of games, the way that they create their own time and space separate from ordinary life. The idea that the conflict in games is an artificial conflict is part of our very definition of games.”

[Zimmerman and Salen 2004]

And if a game system is its own universe, when in contact with a game for the first time we act not unlike the whale from the Hitchhiker’s Guide, investigating our new surroundings, wondering what everything is and what it is for, and giving each object a sign that seems in line with what it affords us.

“Why am I here? What’s my purpose in life? What do I mean by who am I? Calm down, get a grip now … oh! this is an interesting sensation, what is it? It’s a sort of … yawning, tingling sensation in my … my … well I suppose I’d better start finding names for things if I want to make any headway in what for the sake of what I shall call an argument I shall call the world, so let’s call it my stomach. (…) And wow! Hey! What’s this thing suddenly coming towards me very fast? Very very fast. So big and flat and round, it needs a big wide sounding name like … ow … ound ... round ...  ground! That’s it! That’s a good name – ground! “

[Adams 2002]

If roles, as discussed earlier, represent ways that objects afford change or prevention of change on the game state, they are a very powerful way to understand how pattern recognition causes refined mental models to emerge when we play. According to Koster [2005], “the natural instinct of a game player is to make the game more predictable because then they are more likely to win”. This means we are constantly optimizing our thought processes to include as much useful information as possible in as little signs as possible in order to predict accurately how each decision can affect the game state. That’s how a player grows increasingly skilled in a game, replacing the raw presentation of the design with a highly efficient model which only takes into consideration the elements that meaningfully affect decision-making.

When playing a game for the first time, our repertoire of objects and their roles is fairly big – even if we are yet to acknowledge some of them (“what is this box for? What about that pipe?”). We are not sure of how each object interacts with one another, what is important, what is not important, what is possible and what is not possible. With experience, training and instruction we slowly start to refine our model of the game: different objects start to be grouped under the same category if they all affect the game in pretty much the same way (“these are all objects that I can use to climb”); new patterns that previously were not even perceived now take most of our attention as to when they will appear and how (“maybe that noise I heard means that a climb-able object appeared over there”); common situations are more easily identified, and roles are generated to resolve each one (“I need a climb-able object to go over there”). 

In more “challenging” games, identifying roles is more difficult. Above, when describing the design of roles in Go, I stated that the same piece in the same position in the same game can participate in several different “plays” at the same time, and have different roles in each of them. One particular object in a system may have multiple – even simultaneous – roles (“I can also use that pipe to divert water”), or change roles according to the game state (“If I hit that platform, I will be able to climb on it”).

Case Study: Dawn of War 2

Dawn of War 2 is a real-time strategy game developed by Relic Entertainment. Players form small armies based on the classic miniatures game “Warhammer 40K” and, in the title’s main competitive mode, battle for control of strategic points. Dawn of War 2 is a very interesting example of role design: there are several asymmetrical armies with asymmetrical units at players’ disposal, all with many upgrade options that unlock different capabilities as each match progresses.

Below the surface, however, a very clear and simple set of roles governs most in-game decisions. When players, for example, see a squad of units called “Slugga Boyz” charging against an opposing squad of “Devastator Heavy Bolter” troops, they can already be sure that the latter will win. What they are really seeing is not necessarily a network of relationships between each individual unit, but instead a simple case of “melee” going up against “suppression”.

 “Melee” and “Supression” are both examples of the main combat roles that units play in the game of Dawn of War 2, which also include “Jumpers/Teleporters”, “Vehicles”, and others. Roles are dynamic, meaning that the same unit can have multiple roles, or even change roles depending on the situation and/or in choice of upgrades by the player. This type of quasi-intrinsic role design is of great use for designers to proper balance the otherwise extremely asymmetric armies and units in the game, but it also eases the learning curve that normally keeps less dedicated players away from other titles on the same genre, such as the classic Starcraft, developed by Blizzard.

Interestingly, the recognition of this fact led Relic’s designers to actually try and communicate the roles in their game directly to players. A few months after Dawn of War 2 was released, an update became available which would show small icons called “Decorators” on top of each unit representing their respective main roles.


Fig.2 Dawn of War 2 Decorators

This decision had little impact on high-level play – skilled players already understood the game way better than the icon set could ever present – but made the learning curve even lighter for new users since it was no longer required of them to carefully examine each unit in the game before making their own decisions about their roles. A quick glance was enough for a rough assessment. It also lead them easily towards the mental model that the designers intended for the game.

Of course there is a lot more depth to the actual system than this – the dynamic nature of roles in the game was already mentioned, and combat is only one of the title`s strategic elements. Nevertheless, Dawn of War 2 is one of the finest examples of how role design and communication can deeply affect player experience.

Case Study: Magic: The Gathering

Magic: The Gathering is a collectable card game designed by Richard Garfield and published by Wizards of the Coast. In it, players assemble decks of around 60 cards from a collection of thousands and match them against other decks to test not only their playing skills, but their “deck-building” skills as well.

Magic is a good example for this discussion, as the gargantuan space of possibility when building a deck can only be resolved without frustration by players with a solid role-based mental model. It is easy, however, to be confused by the game`s own categorization of cards. Cards in Magic have “types”, which dictate unique rules for those groups of cards. These types can be “enchantments”, “instant magics”, “terrains” and so on. Types, however, are not directly related to roles.

Magic has no formal way of communicating roles to players – they have to find them on their own. That`s one of the main reasons why the game is considered to be extremely reliant on metagame knowledge to function – modern gameplay of Magic is actually designed to work like this, and players and designers alike take pride of that characteristic, even if the tough learning curve and seemingly imbalanced state of the game may look roughly designed by an outside observer.

Community, in these cases, is always helpful in guiding players towards the “ideal” mental models of the game. There is a very interesting mode of playing Magic called “Draft”, in which players received sealed packs of random cards and must all take turns picking cards from this pile to build their own decks, taking into consideration not only an efficient fulfillment of all the roles they`ll need in gameplay, but also trying to deny the most useful cards to their future opponents.


Fig.3 The card is described as a “red instant magic”, but its role is actually “Removal”

In such a seemingly chaotic semantic environment as “Draft”, roles play a very important part. The community even have clear names and references to some of the most important ones. For example, cards which roles are to remove other dangerous cards from play are called “Removals”; cards which allow players to overcome other players` defenses are called “Evasion”; very rare cards which can win the game if brought into it are called “Bombs”, and so forth and so on. This is paramount for players as they build their decks, as they will continuously assess their mental models in ways such as “do I have enough Removal on my deck?”, and “I think I need some ways to provide me Card Advantage”. It is a much simplified and manageable model to deal with a huge amount of sometimes unknown cards than it would be if players had to judge the individual value of each card and deck configuration.


It is crucial that a designer understands how he builds roles in his designs, and – almost as importantly – how he communicates them to players. While this discussion is just preliminary, the concept of “roles” as a design tool is extremely powerful and should not be ignored. One step further than that, game design as a communication situation is an even more powerful concept that provides us with a different perspective on travelled ground. What more new conceptual tools can we develop when we make use of this framework? Design as Communication can offer good insights on how we can impact the behavior, knowledge, attitude and emotions of players.


FRASCARA, J., 2007. Communication Design – Principles, Methods and Practice. Alworth Press.

ATKIN, A., 2006. Peirce`s Theory of Signs. Stanford Encyclopedia of Philosophy. Available from: [Accessed 26 July 2011].

NORMAN, D., 1988. The Design of Everyday Things. Basic Books.

GIBSON, J., 1986. The Ecological Approach to Visual Perception. Psychology Press.

ZIMMERMAN, E. AND SALEN, K. 2008. Rules of Play: Game Design Fundamentals. The MIT Press.

KOSTER, R., 2005. A Theory of Fun for Game Design. Paraglyph Press.

ADAMS, D.,2002 . The Ultimate Hitchhiker's Guide to the Galaxy. Del Rey.

VENTURELLI, M., 2009. Space of Possibility and Pacing in Casual Game Design - A PopCap Case Study. Available here. [Accessed 8 August 2011].


While it is common to believe that playing a game “well” means excelling at the last step of decision-making, it is interpretation that provides the basis to work with. That is, a wrong interpretation of the game state and/or of the space of possibility may lead the entire process towards frustration and “bad decisions”. The first two steps, then, are more interesting for our discussion, as they form players’ mental model [Norman 1988] of the game. A mental model is a “thought reconstruction” of how something works in the real world, built by experience, training and instruction [Norman 1988] – a model built by semiosis.

It is pertinent, then, to discuss game state and space of possibility a little more in-depth. The game state is clearly and concisely explained in “Rules of Play”:

Related Jobs

Digital Extremes
Digital Extremes — LONDON, Ontario, Canada

University of Central Florida, School of Visual Arts and Design
University of Central Florida, School of Visual Arts and Design — Orlando, Florida, United States

Assistant Professor in Digital Media (Game Design)
The College of New Jersey
The College of New Jersey — Ewing, New Jersey, United States

Assistant Professor - Interactive Multi Media - Tenure Track
Bohemia Interactive Simulations
Bohemia Interactive Simulations — Prague, Czech Republic

Game Designer


Raph Koster
profile image
Nice! I am unsure about the basic term, though, because you are using roles here in two different senses:

1. the roles taken on by multiple players interacting inside of one game system, as a team (the common lay usage of role)

2. the varying attributes and verbs afforded by specific tokens within a game system, under the control of one player

Now, it's certainly true that in any sort of formal analysis of nested games, the players on a team can be considered as fairly autonomous tokens in a game played between two coaches. But I think that the common usage of role as meaning distinct "positions" on a team is hard to overcome, despite the fact that you spend most of your article on what are effectively tokens under the control of one player.

You also use RPS as an example; generally, I personally would regard the play of rock, paper, or scissors as direct verb choices, rather than manipulation of tokens, as they do not have any of the other characteristics of tokens -- persistence, discreteness, existence within a topology.

These are nits though. :)

Mark Venturelli
profile image
Hello Raph! Thank you for sparing the time to read my article =)

I am aware that the term "role" overlaps with other common game axioms, specifically the idea of "playing a role" - be that a role in a soccer team or a character in a RPG. It was not my intention to use these definitions of roles in any way.

My definition of role, instead, is: "a representation of a meaningful way with which an object affords change or prevention of change on the game state". This is much deeper than the idea of "tokens in control of a player" because it's not just about objects *you control* - it's actually about ALL objects in the system that could alter the game state. It's a way that I found to represent how our minds simplify systems with redundant or overlapping functions of objects.

In the soccer example, it is possible to think about players' positions as "roles" in a play between coaches, but the definition also supports the idea of objects having multiple simultaneous roles. That is, depending on the game state, the "Attacker" is not the only one with an opportunity to score. A "Middle-field" player could consider the Goal Keeper for a goal pass if it's a specially dramatic moment in the match and everyone is risking everything.

Soccer would also be a neat example of how a seemingly intrinsic role system (each player seems to do just one thing), but everything is actually very dynamic and the *actual* player roles change a lot depending on the game state: the relative position of the ball, own team players, adversaries, etc.

Ronildson Palermo
profile image
After reading the article, Raph's insight and your answer, I'm still left to wonder... This object you mention, it is any entity within the game's system that can be either controlled by a player or an AI or does object, in your article, holds a broader meaning than that?

Also, the roles these objects have are ways they can employ within the game's system to prevent or cause a shift in the game's balance/state, as in "stuff they can do"?

Exemplifying: Two soldiers are objects within a fighting game's system and attacking, blocking & parrying, as well as any other actions which draw a clear line of cause & effect, are all roles these fighters have in attempting to change the game's state by reducing each other's health, neglecting the reduction of their own health and reflecting some of damage back at the attackers, respectively?

Mark Venturelli
profile image
From Wikipedia's definiton of "System":

"A system is a set of elements and relationships which are different from relationships of the set or its elements to other elements or sets."

"elements" and "relationships" are often referred to as "objects" and "dynamics".

In your example, "Attack", "Block" and "Parry" are all objects of the system, elements of the systems. Objects *have* roles, they aren't roles.

Ronildson Palermo
profile image
Oh, great! Thanks, got it now, just misplaced the elements in the hierarchy tree; it makes sense too.

How the attack, block and parry relate to each other is indeed very important during the initial design stage, but even more important once you need to change things in your game: knowing how elements relate to each other is even more important when you need to remove something from the system.

Thanks for the insight, the article's very helpful.

Raph Koster
profile image

That's why I referenced "nested games." After pounding my head on the issue of game grammar for a while, I ended up at the conclusion that this is all MUCH simpler to examine if you do regard games as made of games (and we often call these smaller games terms like "systems" or "minigames" or even "features" or "opponents."

So what you are calling a role would actually fall out differently depending on the level of granularity with which you are examining the overall design.

For the soccer example, at the high level you would say that it is a game between two coaches, where the players are assets. The "moves" -- aka verbs, aka inputs into the system -- available to the coach are fairly limited, since the "tokens" are autonomous.

But when you look at the individual players on the field, they all have a set of goals -- for strikers it might be "score goal" and "set up goal" and so on... They have a very few moves: pass, intercept, strike, steal, and "skip turn" which is "stand around and do nothing this microsecond."

In addition, each token exists inside a unique topology -- generally NOT a topology that covers the entire field. The individual player has varied statistics, situational awareness, varied location, varied availability of open space, and so on.

In this way of looking at things, it is the topology of the space that provides "score a goal" as a possible goal for the individual player.

The advantage to this approach is that then you can proceed to analyze just passing the ball as a game system in its own right, one in which there are

- three roles for actors: initiator, receiver, obstacle (this latter one could arguably be split up, as opponent obstacles and own team obstacles can have different outcomes should the ball be touched by them).

- one token -- the ball.

So I would personally look at roles that way. It reduces away the complexity of dealing with multiple simultaneous roles, which greatly simplifies analysis. It also makes clear the distinction between "actors that I control directly" and "actors over which I have no influence." I term the former "tokens", usually call "actors who have an antithetical goal" as "opponents" and regard purely passive tokens as part of the topology.

Mark Venturelli
profile image
Hi Raph!

Thank you for keep coming by! I love great design discussions like this.

I guess we're not disagreeing, actually. What you are describing is system analysis, and I agree with you completely - it is MUCH easier if you break everything in sub-systems, providing you don't lose focus of the big picture, of course.

"So what you are calling a role would actually fall out differently depending on the level of granularity with which you are examining the overall design. "

I could not agree more. That's precisely the case. However, the reason why I believe we are talking about two different things is that my focus in not on formal system analysis, i.e. in determining what are the sub-systems, objects and possible actions - your topology-actors-tokens framework is solid for that.

The idea of roles is to allow a deeper understanding on how the player interprets the system - that's why their nature *is* to be dynamic and changing, not static. Think of it this way: "initiator, receiver, obstacle" is the formal system - the "Dynamic Object" (see fig.1 above). Roles try to make sense of what is happening on the "Dynamic Interpretant".

Soccer is an extremely complex game in a player's point of view, but I'll try not to bore you with the following analysis. Taking your example, mapping the dynamic interpretant of a pass in a certain situation (ALWAYS in a certain situation/game state) could be something like this:

"My current state is: I have the ball. My team is losing by one goal. I have all my teammates outside of meaningful range, but there is one attacker on my left, not too far away, and another on the right. I also take note of the opposite team's positions and overall attitude and know that two of them are threatening to my possession of the ball."

"My analysis of my current state's space of possible action is: I'm too far to shoot for a goal, and there are two markers too close from me, so I'm in danger. There are two teammates that could participate on this play. I could try and drible my way out of this situation, but I believe it's risky. I could also try to fall back and give the ball to someone behing me, but we are losing the game and must play agressively. I could try to force the opponents into making a fault on me (.... and so forth and so on, the space of possibility is huge)"

"My desirable future state is: one of my teammates should receive the ball in a position closer to the opponent's goal, and with no marker nearby"

"My choice of action is: I will feint a pass to my teammate on the right, and when the markers make their move and my teammate on the left advances, I will give *him* the ball with a long pass."

And I focus mainly on the two first things: perceiving and interpreting the game state. What would be the simplest concept that would allow these extremely complex situations to be handled quickly? Experienced players seem to almost instintively know what to do, so they've *got* to have a framework inside of their heads - even though they can't properly explain it if someone asks.

The idea of roles is to attribute to each object a little label informing the player of how this object, in the current game state, can affect the game state in a moment in the future.

In my example, both teammates had roles as "People Who Could Receive a Short Pass From Me". Other teammates as "Too Far Away for a Pass". Closer opponents turned to me as "My Markers". Opponents that are closer to the other teammates are "Their Markers". Possible actions such as "Pretending to Shoot the Ball" could have a role such as "Forcing the Markers to Move". Or maybe running in a perpendicular direction from my closer marker could have the role "Forcing the Marker to Try a Fault".

And so forth and so on...

The idea is to re-signify the game world (since the *real* world is already re-signified by the rules of the game themselves) in a way that simplifies decision-making. Soccer is extremely dynamic - that's why it's so hard to be good at it -, so it's a good example of why a framework such as this might be needed.

Raph Koster
profile image
I see; in your terms, then roles are really about evaluative processes -- means of classifying what I termed actors and tokens into buckets in order to arrive at a decision heuristic and thence a decision.

In my terms, "forcing the markers to move" and "forcing a fault" would be goals, and "feint" would be a verb.

Luis Guimaraes
profile image
The amount of roles each object is able to fulfill in a system, i.e. the relevance of said objects in the system is surely between the most important aspects that generate gameplay-related depth in a game, and (although can be treated as an aspect of depth) the space of possibility in player agency (for the most extrinsic elements, mechanics and agents). Having knowledge and foresight of both perception and actual roles (and role interconnections) of each element present in a system is the ground for extensive positive evolution (and perception of emergent, unplanned possibilities) and polishing steps in an iterative subcycle.

Great noteworthy piece, Mark. Bookmarked.

Mark Venturelli
profile image
Couldn't say it better myself! More roles = mechanics are more integrated = more depth/design elegance. Thanks for reading =)

Luis Guimaraes
profile image
"What more new conceptual tools can we develop when we make use of this framework?"

That made me think of a visual thesaurus, where you could point the connections between its elements, and their roles and integrated mechanics. A visual thesaurus is great because each point often have more than two connections, and in the end, somehow, everything is connected.

Then the designer could analyse each connection (foreseen, logical or observed in test phases), and raise questions where there seem to be no connection: what can I make here?

Each connection can be weighted with arbitrary or data-based values (fun, frequency in gameplay, marketing impact, strategy value, balance), then each point (element) can be evaluated per level of importance (gameplay value), which can tell which mechanics deserve more development time to be polished and improved upon, how it affects the game feel, balance and pacing.

Basically a big chart, but visually organized like a map, with places and roads, and comercial trajectories, that can tell which road must be improved, pavemented, train-lined, and where new things should be build to make best use of what's already there (hope it's a good analogy).

The first exemple in mind was Bioshock's machines/electricity/water/fire/oil interconnected roles as an exemple, on how everything in the game has more than one role. Medical stations for exemple: buy a heal/burn to steal a health pack/hack to buy cheaper and make an acid spilling trap, and its waypoint role for enemy AI and the player itself). It's a good exemple, but then I thought it would work even better to simply mention the name Scribblenauts.

Not so much of an ideal tool, but an analysis technique to funnel observation and efforts a clear way. A bit similar to writing techniques, but something that might be of good use, specially in communicating the vision for the roles of the system objects, in a visual (and preferably interactive) way.

Mark Venturelli
profile image
Your Bioshock analysis is spot-on! Seeing the medical station as a healing/hack point, but a waypoint that enemies could also use is a great example of dynamic roles in games and how they add depth!