Player/System Action Composites

From gdp3
Jump to: navigation, search

Game systems where a player's actions can be initiated by either that player or the system, or where the execution of the actions are performed together.

This pattern is a still a stub.

Examples

Using the pattern

Player/System Action Composites can either be created by letting actions that execute mechanically once activated be possible to be activated both by a player or the game system, or let input from both affect the execution of an action.

An important aspect of the latter is to make sure that the system part actually differs from "normal" execution of the action; this is most easily done by letting others not have the pattern or making the pattern active due to Power-Ups or setting Gameplay Options before gameplay begins.

Independent of type, they are most easily created through Automated Responses. Sometimes this is created through letting the Skills or Characters affect the action, i.e. using Player/Character Skill Composites together with Automated Responses (or, in more complex cases, Enforced Agent Behavior) to instantiate the pattern. Supporting Player Augmentations can allow players to choose to have the pattern or not independent of gameplay events.

Consequences

Player/System Action Composites quite naturally modify patterns related to actions modified by the pattern, of which Combat and Movement are perhaps the most natural choices.

The use of the pattern affects both Performance Uncertainty and Player Unpredictability, typically in making them less uncertain or unpredictable.

Relations

Can Instantiate

-

Can Modulate

Combat, Movement, Performance Uncertainty, Player Unpredictability

Can Be Instantiated By

Automated Responses, Player Augmentations

Player/Character Skill Composites together with Automated Responses or Enforced Agent Behavior


Can Be Modulated By

-

Possible Closure Effects

-

Potentially Conflicting With

-

History

New pattern created in this wiki.

References

-

Acknowledgements

-