8,342
edits
Paradox-01 (talk | contribs) mNo edit summary |
Paradox-01 (talk | contribs) m (copy-edit) |
||
Line 43: | Line 43: | ||
Anyway, to let an character flow from one anim state to another the <ToState> is used. | Anyway, to let an character flow from one anim state to another the <ToState> is used. | ||
Let's say a SBG grenade | Let's say a SBG grenade hits Konoko. The particle's '''damage type''' is '''blownup''', this and the direction of damage force an anim of type '''Blownup''' or '''BlownupBehind''' to play like TRAMKONOKOblownup1. | ||
This all simply means she falls to her back, going into the FallenBack state. The engine picks up next anim with <FromState>FallenBack. | |||
Also, '''receiving damage''' puts the character into '''Combat mode''' so further anims will be of variant Combat. | |||
But if the player gives no input Mai will remain on the ground as <ToState>FallenBack creates a loop. | But if the player gives no input Mai will remain on the ground as <ToState>FallenBack creates a loop. | ||
Line 61: | Line 63: | ||
Knowing this behavior we can deduce that anims types registered to user input will make the engine ignore all the automatic anims inside the pool, therefor breaking the loop of KONCOMfallen_back. | Knowing this behavior we can deduce that anims types registered to user input will make the engine ignore all the automatic anims inside the pool, therefor breaking the loop of KONCOMfallen_back. | ||
Since KONCOMgetup_lt has <ToState>Standing and | Since KONCOMgetup_lt has <ToState>Standing and Konoko is still in Combat mode the following idle anim must also have <Varient>Combat. | ||
So, next anim played will be KON'''COM'''idle1 or KON'''COM'''idle2. | So, next anim played will be KON'''COM'''idle1 or KON'''COM'''idle2. |
edits