In this post, I will use the State Pattern to alter the behaviors of a hero when it is under attack or being silenced. State pattern allow us to encapsulate states into separate classes and delegate behaviors to the object representing the current state.
See code at Github repo (https://github.com/yangju2011/design-patterns). Code is adapted from Head First Design Patterns: A Brain-Friendly Guide 1st Edition by Eric Freeman and Elisabeth Robson.
State Pattern
Definition
Allows an object to alter its behaviors when its internal state changes. The object will appear to change in class. It encapsulates states into separate classes and delegates behaviors to the object representing the current state.
State pattern and state machine
These two concepts are closely related and sometimes used interchangeably. However, they are different in their focus.
- State pattern abstracts the states and focuses on varying behaviors of a state. It doesn’t mean to address the transition.
- State machine abstracts the state diagram and focuses on the transition between states. It doesn’t mean to address the behaviors in each state.
See Wikipedia and StackOverflow.
HeroStateV1
In this example, a Hero can be in one of the 3 states: ALIVE, DEAD, SILENCED defined in HeroContext
When a Hero is ALIVE with hp>0, it can attack, and can be attacked and silenced.
- When
attacked, itshpis decreased bydamage. Ifhp<=0, a Hero enters the state ofDEADwithhp=0. - When
silenced, a Hero enters the state ofSILENCED.
When a Hero is DEAD with hp=0, it can be revived.
- When
revived, a Hero enters the state ofALIVEwith full hp.
When a Hero is SILENCED, it can be attacked and recovered.
- When
attacked, itshpis decreased bydamage. Ifhp<=0, a Hero enters the state ofDEADwithhp=0. - When
recovered, a Hero enters the state ofALIVE.
If we have a new State or a new behavior, we will have to modify code in HeroContext.
Example output:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 |
Hero Context ================ Hero HP 10 Hero is alive ...Hero is being attacked with damage: 5 Hero Context ================ Hero HP 5 Hero is alive ...Hero is attacking others. Hero Context ================ Hero HP 5 Hero is alive ...Hero is already recovered, and cannot be recovered. ...Hero is already alive, and cannot be revived. ...Hero is being attacked with damage: 10 Hero Context ================ Hero HP 0 Hero is dead ...Hero is dead, and cannot attack others. ...Hero is dead, and cannot be attacked. ...Hero is dead, and cannot be recovered. ...Hero is dead, and cannot be silenced. ...Hero is being revived. Hero Context ================ Hero HP 10 Hero is alive ...Hero is being silenced. Hero Context ================ Hero HP 10 Hero is silenced ...Hero is silenced and cannot attack others. ...Hero is already silenced and cannot be silenced again. ...Hero is already alive but silenced, and cannot be revived. ...Hero is being attacked with damage: 5 Hero Context ================ Hero HP 5 Hero is silenced ...Hero is being recovered. Hero Context ================ Hero HP 5 Hero is alive ...Hero is being silenced. ...Hero is being attacked with damage: 10 Hero Context ================ Hero HP 0 Hero is dead ...Hero is being revived. Hero Context ================ Hero HP 10 Hero is alive |
HeroStateV2
Here we are applying the State Pattern with HeroContext and State
- create a
Stateinterface with all possible behaviors (actions). - implement the
Stateinterface in concrete classes, each class has its own implementation for all bebaviors. HeroContextincludes all differentStateand callsstate.handle(). All behaviorshandle()are delegated toState.
We can think of the State Pattern as an alternative to having a lot of if-else conditions in the context.
Using the State Pattern, we encapsulate what varies (behaviors) in State classes and usually have to create more classes in the design. The client HeroContext knows very little about the state object. The current state of the context changes across a set of state objects to reflect its internal state, and the behaviors of the context changes as well. When we call context.handle(), depending on the current state of the context, the behaviors vary.
Example output is the same as before.
HeroStateV3
Here we have two new behaviors disappear, appear (in red) associated with a new state InvisibleState.
Using State Pattern, we can keep HeroContext mostly unchanged.
- When we have a new
behavior, we can modify theStateinterface and implement this behavior inStateclasses. - When we have a new
State, we can easily create a new class implementingStateinterface and define its behaviors.
The state transition graph is shown below:
Example output:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 |
Hero Context ================ Hero HP 10 Hero is alive ...Hero is being attacked with damage: 5 Hero Context ================ Hero HP 5 Hero is alive ...Hero is attacking others. Hero Context ================ Hero HP 5 Hero is alive ...Hero is already visible, and cannot appear. ...Hero is already recovered, and cannot be recovered. ...Hero is already alive, and cannot be revived. ...Hero disappears. Hero Context ================ Hero HP 5 Hero is invisible ...Hero is already invisible, and cannot disappear. ...Hero is invisible and cannot be attacked. ...Hero is invisible and cannot be silenced. ...Hero is already recovered, and cannot be recovered. ...Hero is already alive, and cannot be revived. ...Hero is attacking others. Hero Context ================ Hero HP 5 Hero is invisible ...Hero appears. Hero Context ================ Hero HP 5 Hero is alive ...Hero is being attacked with damage: 10 Hero Context ================ Hero HP 0 Hero is dead ...Hero is dead, and cannot appear. ...Hero is dead, and cannot disappear. ...Hero is dead, and cannot attack others. ...Hero is dead, and cannot be attacked. ...Hero is dead, and cannot be recovered. ...Hero is dead, and cannot be silenced. ...Hero is being revived. Hero Context ================ Hero HP 10 Hero is alive ...Hero is being silenced. Hero Context ================ Hero HP 10 Hero is silenced ...Hero is already visible, and cannot appear. ...Hero is silenced and cannot attack others. ...Hero is already silenced and cannot be silenced again. ...Hero is already alive but silenced, and cannot be revived. ...Hero disappears. Hero Context ================ Hero HP 10 Hero is invisible ...Hero appears. ...Hero is being attacked with damage: 5 Hero Context ================ Hero HP 5 Hero is alive ...Hero is already recovered, and cannot be recovered. Hero Context ================ Hero HP 5 Hero is alive ...Hero is being silenced. ...Hero is being attacked with damage: 10 Hero Context ================ Hero HP 0 Hero is dead ...Hero is being revived. Hero Context ================ Hero HP 10 Hero is alive |
Real life use cases
- Uber trip booking: State Machine Design pattern — Part 2: State Pattern vs. State Machine
- E-commerce ordering, food ordering, and trip booking: Finite State Machines + Android + Kotlin = Good Times
- Mobile app UI activity flow: State Machine Design pattern —Part 1: When, Why & How
- Workflow engine (sequential pattern): WORKFLOW ENGINE VS. STATE MACHINE
