From gdp3
Revision as of 11:30, 6 July 2016 by Staffan Björk (Talk | contribs) (Using the pattern)

Jump to: navigation, search

Ancillary actions necessary for gameplay but that do not contribute directly to gameplay.

This pattern is a still a stub.

Note: the concept of Excise comes from the field of Human-Computer Interaction[1].


Using the pattern

Excise is usually seen as a Negative Pattern which although unwanted occurs as a consequence of wanted design features. Thus, designing for Excise is typically aimed at minimizing the effects of it. The need for Excise can depend on many different design features. On the most general level, Optional Rules can introduce new Excise but also introduces it by making players need to choose which Optional Rules to use and keep track of this during gameplay. Also generally, the issue of Excise in games can be mitigated by having it interwoven with choices (i.e. Freedom of Choice) or allowing players to interaction socially while performing them (i.e. ensuring that the Excise has Minimalized Social Weight.

The first reason for Excise comes from having to manipulate game states for other reasons than actual gameplay actions. Handling complex or detailed Abstract Player Constructs, Characters, groups of Units, or Persistent Game Worlds does so because specifics about them need to be found, described, or updated. Dedicated Game Facilitators, Game Servers, and Game Masters can remove this, but of course the latter requires Excise from the Game Masters themselves (Entitled Players can spread the burden somewhat). Similarly Complex Gameplay can give rise to Excise because many game elements need to be manipulated (e.g. through Game Element Insertion or updating No-Use Bonuses). More generally, any game with significant about of Gameplay Statistics that needs to be manually updated can cause Excise. For this reason, any game needing Bookkeeping Tokens can be said to have some Excise but having Resource Caps can limite this. While Current Player Tokens and First Player Tokens are examples of Bookkeeping Tokens, they help players remember things they need to keep track of anyway and can thereby be seen to modulate rather than create Excise. The same goes for Score Tracks. Loading and saving game states in Computer Games does produce some Excise related to manipulating game states but this is often not a problem unless players engage in Save Scumming.

Another reason for Excise comes from actions that are gameplay actions but can be perceived as meaningless or uninteresting to players. Given that Grinding is performing repetitive actions without significant challenges, any actions perceived as these can easily be perceived as Excise; this type of Excise can be removed through offering Purchasable Game Advantages or allowing Mules or Non-Player Help. More specifically applying brute force methods to find solutions to Puzzle Solving can be Excise, as can conducting Movement across uneventful terrains. Having to move without Vehicles in Vehicle Sections being a prime example of this while introducing Vehicles can be a way of removing Excise for "normal" Movement (which can be noticed in games like the Battlefield series). Quick Returns and Quick Travel are other design patterns that can mitigate Excise related to Movement. Drafting requires some Excise to swap game elements in synchronicity, and this becomes pronounced when there is no gameplay or choices involved (as for example occurs when dealing hands of Cards in many Card Games. Zero-Player Games can be said to have made all gameplay into Excise but can still offer meaningful play to players through the Meta Games they can provide. Similarly, games with Action Programming but no actual choices for players when the inner gameplay occurs (as is for example the case in C-Robots) consist purely of Excise (although interesting choices exist outside the inner gameplay).

A final reason for Excise occurs easily in Self-Facilitated Games, especially if these make use of AI Players, Game System Player, detailed Game Worlds, or large numbers of Units.

Diegetic Aspects

As mentioned above, having to describe Characters or Persistent Game Worlds can be Excise when players need to do it.

Interface Aspects

As also mentioned above, Bookkeeping Tokens are necessary design solutions that cause Excise in significantly complex games. However, they may be justified on their own for helping players keep track of things they anyway need to keep track of. Examples of this include Current Player Tokens, First Player Tokens, and Score Tracks.


Often, performing Excise can be seen as a form of forced No-Ops.



Can Instantiate


Can Modulate


Can Be Instantiated By

Abstract Player Constructs, Action Programming, Bookkeeping Tokens, Characters, Complex Gameplay, Drafting, Game Element Insertion, Game Masters, Gameplay Statistics, Grinding, Movement, No-Use Bonus, Optional Rules, Persistent Game Worlds, Puzzle Solving, Save Scumming, Self-Facilitated Games, Units, Vehicle Sections, Zero-Player Games

AI Players, Game System Player, Game Worlds, or Units in Self-Facilitated Games

Can Be Modulated By

Current Player Tokens, Entitled Players, First Player Tokens, Game Servers, Score Tracks

Possible Closure Effects


Potentially Conflicting With

Dedicated Game Facilitators, Freedom of Choice, Game Masters, Minimalized Social Weight, Mules, Non-Player Help, Purchasable Game Advantages, Quick Returns, Quick Travel, Vehicles

Resource Caps when Bookkeeping Tokens are used


New pattern created in this wiki.


  1. Cooper, A., Reimann, R., Cronin, D. & Noessel, C. (2014). About Face: The Essentials of Interaction Design, 4th edition. Wiley.


Karl Bergström