Player State Machine (Test)
Table of Contents
0 - Introduction
This document outlines the Finite State Machine infrastructure inherent to the Player Character. It contains and defines:
- Player States & Overarching Architecture
- State Transitions
- State Actions
The player's Finite State machine defines the states and capabilities of the Player Character within the game. Each state is self-contained, and can be transitioned to when certain conditions are met. The state capabilities, transition requirements, and relations to one another are defined within this document.
0.1 - Disclaimer
This document is subject to change as part of the evolving nature of the game's development, and updates will be made accordingly. If anything is not correct or requires further explanation, contact Adam Janus to get further guidance.
0.2 - Terminology
| Term | Meaning |
|---|---|
| PC | Player Character |
FSM | Finite State Machine |
1 - Core Concepts
There are 4 key concepts inherent to the FSM
| Concept | Definition |
|---|---|
| State | The different, distinct, and self-contained conditions the PC can be in. The PC can only be in one state at any given moment. |
| Action | Describes the different actions, mechanics, and elements the player can engage with.Multiple States can have access to the same Actions. Some Actions will Transition from the current State to a new one. Actions can induce Statuses on the player. |
| Status | Describes an external effect (e.g. buff/debuff) that affects the player (e.g. Blindness, Crippled) Statuses can affect the capabilities of the player (e.g. reduce speed), and prevent or allow certain Actions taking place (e.g. no sprinting when Crippled). Statuses can prevent or allow the player's Transitions to another State. |
| Transition | A Transition refers to the act of moving from one State to another, usually as a result of an Action or Status. |
2 - Player States
| State | Description |
|---|---|
| Idle |
| Controlled Fall | |
| Idle | |
| Idle | |
| Idle | |
| Idle | |
| Idle | |
| Idle |