HedgeDocs - User contributions [en]

Enemy States (Werehog)

2026-09-14T02:28:08Z

King Galactix: Added a section for small enemies statenames

The Werehog's enemies have a chart (or character) state xml, found in their respective archive files (e.g. #EvilEnemyNightmareR.ar.00 >> EvilEnemyNightmareR.chr.xml). This XML file deals with the different states of the enemies, and how the enemies react to the player's attack types.

{{Notice|type=note|content=Each enemy has distinct states (hard-coded), so we will view common values between enemies.}}

== StateChartInfo ==
[[File:StateChartInfo.png|thumb|The StateChartInfo identifies the enemy's state as "Rise", and receives "KnockOut" when hit with a "KnockBackSoft" attack type.|left]]'''StatChart''' is what the game calls the '''StateChart''', which contains every individual information of the different states. '''StateChartInfo''' represents an individual state of a nighttime enemy. '''StateNames''' identify the different enemy states which are active, along with player attack types.

These vary between enemies, hence it is currently impossible to add new ENEMY states or states which belong to other enemies. However, it is possible to create a StateChartInfo with an attack type, allowing for enemies to react to the next attack type.

The enemy reacts to different attack types by writing in the '''StateNames''' into the variables. For example, if an enemy is in the "Rise" state and the player attacks them with a combo using the "NormalSoft" attack type, that enemy will enter a damage state and therefore receive damage (which is determined by Evil_Enemy.prm.xml and the code itself. Refer to "Attack and Hitbox Collision Types" for more information on attack types.
== StateNames ==
StateNames determine what the state of an enemy is, and how they react to different player attack types. It is a static system, so it makes sense to use it sparingly.

There are common states such as "Begin", "Walk", "Damage", "Think", and so on, which work commonly between enemies and their variants. Next, enemies tend to have group specific values, such as Small and Middle enemies having a "Jump" or "Combo" state while minibosses do not. Finally, enemies have their own specific values for their enemy type and variants, such as "AttackOneHand" or "Shot".

Below this paragraph are listings of majority of the different enemy states, though there will be information missing. It is your responsibility to find out what every state does, but most of the named states will be informative enough.

=== Common States ===
{| class="wikitable sortable"
|+Common StateNames
!StateName
!Enemy Type
!Function
|-
|Begin
|All
|Enemy is summoned and awakens
|-
|Tell
|Small, Middle
|Warns other enemies around them
|-
|Walk
|All
|Walks around.
|-
|Wait
|All
|Untested
|-
|Think
|All
|Enemy has a certain percentage chance of
walking, waiting, or doing a certain action.
|-
|Seek
|All
|Looks around for player
|-
|Fall
|Small, Middle
|Falls from height
|-
|Rise
|Small, Middle
|Rises after getting knocked out
|-
|RiseAfterCombo
|Small, Middle
|Rises after getting comboed mid-air
|-
|Guard
|Middle
|Guards against the player
|-
|Stance
|Small, Middle
|Prepares for attack
|-
|AttackSpecial
|Small, Middle
|Special Attack
|-
|Chase
|Small, Middle
|Chases after player
|-
|Jump
|Small, Middle
|Jumps
|-
|Damage
|All
|Damages enemy
|-
|Stun
|All
|Stuns enemy
|-
|KnockOut
|Small, Middle
|Knocks back enemy (static)
|-
|KnockOutByMotion
|Small, Middle
|Knocks back enemy (dynamic?)
|-
|Combo
|Small, Middle
|Juggles enemy when hit
|-
|Dead
|All
|Death state
|}

=== Small Enemy States ===
{| class="wikitable"
|+
!StateName
!Enemy
!Variant
!Function
|-
|AttackNormal
|Little Rex (Reckless), Chibi Fighters, Dark Fright (Spooky)
|All
|Single bite attack, punch attack, Flying strike attack
|-
|AttackHard
|Little Rex (Reckless)
|All
|Hard headbutt attack
|-
|AttackRush
|Little Rex (Reckless)
|All
|Chomping charge attack
|-
|Sleep
|Little Rex (Reckless)
|All
|Napping
|-
|DeepSleep
|Little Rex (Reckless)
|All
|Napping, but with Zs.
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|}

=== Middle Enemy States ===
{| class="wikitable"
|+MiddleEnemy Specific StateNames
!StateName
!Enemy
!Variant
!Function
|-
|Attack
|Egg Fighter, Master, Killer Bee
|All but Egg Shooters, All, All
|
* Combined state for all Egg Fighters attack (punches, sword strike, shield bashes)
* Close-range hit for Masters
* Both rush and near attack for Killer Bees
|-
|Shot
|Egg Fighter
|Egg Shooter
|Shooting at player
|-
|ShootChibi
|Egg Fighter
|Egg Chibi Fighter
|Shooting chibi fighter out of hands.
|-
|AttackOneHand
|Nightmare
|All
|Single hand attack (close and far)
|-
|AttackBothHand
|Nightmare
|All
|Double hand attack (close and far)
|-
|AttackJump
|Nightmare
|All
|Jump attack
|-
|SummonSpooky
|Master
|Spooky Master
|Summons spooky's and other enemies
|-
|MagicRecovery
|Master
|Heal Master
|Heals enemies
|-
|MagicPowerUp
|Master
|Power Master
|Powers enemies
|-
|MagicFire
|Master
|Fire Master
|Fire ball
|-
|MagicLightning
|Master
|Lightning Master
|Lightning ball
|-
|Dodge
|Nightmare
|All
|Dodges against attack
|-
|Idle
|Dark Eel (Moleel)
|N/A
|Idle state
|-
|Appear
|Dark Eel (Moleel)
|N/A
|Appears from hole
|-
|AttackSlash
|Dark Eel (Moleel)
|N/A
|Straight bite attack
|-
|AttackRolling
|Dark Eel (Moleel)
|N/A
|Horizontal spinning attack
|-
|AttackRollingOnce
|Dark Eel (Moleel)
|N/A
|Horizontal sweep attack
|-
|Fireball
|Dark Eel (Moleel)
|N/A
|Fire ball
|}

=== Miniboss Enemy States ===
{| class="wikitable"
|+Miniboss Enemy States (Variants N/A)
!StateName
!Enemy
!Variant
!Function
|-
|AttackIdle
|Titan, Big Mother
|N/A
|Prepares for attack
|-
|AttackRolling
|Titan, Big Mother
|N/A
|Large swipe attack, Spinning attack
|-
|AttackNear
|Titan
|N/A
|Close-range attack
|-
|AttackOneStrike
|Titan
|N/A
|Single strike attack
|-
|AttackThreeStrike
|Titan
|N/A
|Triple strike attack
|-
|AttackStreightShockwave
|Titan
|N/A
|Charged strike attack
|-
|AttackJumpShockwave
|Titan, Big Mother
|N/A
|Jumping shockwave attack
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|}

Enemy States (Werehog)

2026-09-07T15:11:43Z

King Galactix: Refactored the enemy specific section to add distinction between enemy types (small, middle, large)

The Werehog's enemies have a chart (or character) state xml, found in their respective archive files (e.g. #EvilEnemyNightmareR.ar.00 >> EvilEnemyNightmareR.chr.xml). This XML file deals with the different states of the enemies, and how the enemies react to the player's attack types.

{{Notice|type=note|content=Each enemy has distinct states (hard-coded), so we will view common values between enemies.}}

== StateChartInfo ==
[[File:StateChartInfo.png|thumb|The StateChartInfo identifies the enemy's state as "Rise", and receives "KnockOut" when hit with a "KnockBackSoft" attack type.|left]]'''StatChart''' is what the game calls the '''StateChart''', which contains every individual information of the different states. '''StateChartInfo''' represents an individual state of a nighttime enemy. '''StateNames''' identify the different enemy states which are active, along with player attack types.

These vary between enemies, hence it is currently impossible to add new ENEMY states or states which belong to other enemies. However, it is possible to create a StateChartInfo with an attack type, allowing for enemies to react to the next attack type.

The enemy reacts to different attack types by writing in the '''StateNames''' into the variables. For example, if an enemy is in the "Rise" state and the player attacks them with a combo using the "NormalSoft" attack type, that enemy will enter a damage state and therefore receive damage (which is determined by Evil_Enemy.prm.xml and the code itself. Refer to "Attack and Hitbox Collision Types" for more information on attack types.
== StateNames ==
There are common states such as "Begin", "Walk", "Damage", "Think", and so on, which work commonly between enemies and their variants. Next, enemies tend to have group specific values, such as Small and Middle enemies having a "Jump" or "Combo" state while minibosses do not. Finally, enemies have their own specific values for their enemy type and variants, such as "AttackOneHand" or "Shot".

=== Common States ===
{| class="wikitable sortable"
|+Common StateNames
!StateName
!Enemy Type
!Function
|-
|Begin
|All
|Enemy is summoned and awakens
|-
|Tell
|Small, Middle
|Warns other enemies around them
|-
|Walk
|All
|Walks around.
|-
|Wait
|All
|Untested
|-
|Think
|All
|Enemy has a certain percentage chance of
walking, waiting, or doing a certain action.
|-
|Seek
|All
|Looks around for player
|-
|Fall
|Small, Middle
|Falls from height
|-
|Rise
|Small, Middle
|Rises after getting knocked out
|-
|RiseAfterCombo
|Small, Middle
|Rises after getting comboed mid-air
|-
|Guard
|Middle
|Guards against the player
|-
|Stance
|Small, Middle
|Prepares for attack
|-
|AttackSpecial
|Small, Middle
|Special Attack
|-
|Chase
|Small, Middle
|Chases after player
|-
|Jump
|Small, Middle
|Jumps
|-
|Damage
|All
|Damages enemy
|-
|Stun
|All
|Stuns enemy
|-
|KnockOut
|Small, Middle
|Knocks back enemy (static)
|-
|KnockOutByMotion
|Small, Middle
|Knocks back enemy (dynamic?)
|-
|Combo
|Small, Middle
|Juggles enemy when hit
|-
|Dead
|All
|Death state
|}

=== Middle Enemy States ===
{| class="wikitable"
|+MiddleEnemy Specific StateNames
!StateName
!Enemy
!Variant
!Function
|-
|Attack
|Egg Fighter, Master, Killer Bee
|All but Egg Shooters, All, All
|
* Combined state for all Egg Fighters attack (punches, sword strike, shield bashes)
* Close-range hit for Masters
* Both rush and near attack for Killer Bees
|-
|Shot
|Egg Fighter
|Egg Shooter
|Shooting at player
|-
|ShootChibi
|Egg Fighter
|Egg Chibi Fighter
|Shooting chibi fighter out of hands.
|-
|AttackOneHand
|Nightmare
|All
|Single hand attack (close and far)
|-
|AttackBothHand
|Nightmare
|All
|Double hand attack (close and far)
|-
|AttackJump
|Nightmare
|All
|Jump attack
|-
|SummonSpooky
|Master
|Spooky Master
|Summons spooky's and other enemies
|-
|MagicRecovery
|Master
|Heal Master
|Heals enemies
|-
|MagicPowerUp
|Master
|Power Master
|Powers enemies
|-
|MagicFire
|Master
|Fire Master
|Fire ball
|-
|MagicLightning
|Master
|Lightning Master
|Lightning ball
|-
|Dodge
|Nightmare
|All
|Dodges against attack
|-
|Idle
|Dark Eel (Moleel)
|N/A
|Idle state
|-
|Appear
|Dark Eel (Moleel)
|N/A
|Appears from hole
|-
|AttackSlash
|Dark Eel (Moleel)
|N/A
|Straight bite attack
|-
|AttackRolling
|Dark Eel (Moleel)
|N/A
|Horizontal spinning attack
|-
|AttackRollingOnce
|Dark Eel (Moleel)
|N/A
|Horizontal sweep attack
|-
|Fireball
|Dark Eel (Moleel)
|N/A
|Fire ball
|}

=== Miniboss Enemy States ===
{| class="wikitable"
|+Miniboss Enemy States (Variants N/A)
!StateName
!Enemy
!Variant
!Function
|-
|AttackIdle
|Titan, Big Mother
|N/A
|Prepares for attack
|-
|AttackRolling
|Titan, Big Mother
|N/A
|Large swipe attack, Spinning attack
|-
|AttackNear
|Titan
|N/A
|Close-range attack
|-
|AttackOneStrike
|Titan
|N/A
|Single strike attack
|-
|AttackThreeStrike
|Titan
|N/A
|Triple strike attack
|-
|AttackStreightShockwave
|Titan
|N/A
|Charged strike attack
|-
|AttackJumpShockwave
|Titan, Big Mother
|N/A
|Jumping shockwave attack
|}

Enemy States (Werehog)

2026-09-07T05:02:03Z

King Galactix:

Enemy States (Werehog)

2026-09-07T05:00:59Z

King Galactix:

Enemy States (Werehog)

2026-09-07T05:00:06Z

King Galactix: Included the Enemy Specific section.

Enemy States (Werehog)

2026-09-07T04:53:13Z

King Galactix: More information provided for Common States

Enemy States (Werehog)

2026-08-21T01:40:14Z

King Galactix: Included other entires to the StateName table

Enemy States (Werehog)

2026-08-21T00:37:58Z

King Galactix:

Enemy States (Werehog)

2026-08-21T00:33:20Z

King Galactix:

Enemy States (Werehog)

2026-08-21T00:32:20Z

King Galactix:

Enemy States (Werehog)

2026-08-21T00:31:55Z

King Galactix: Undo revision 1559 by King Galactix (talk)

Enemy States (Werehog)

2026-08-21T00:31:17Z

King Galactix: fix the formatting

Enemy States (Werehog)

2026-08-20T20:40:17Z

King Galactix: Included a StateName section, which goes over common and enemy specific states (which will be explained more closely in the enemy ai/behaviour section)

Enemy States (Werehog)

2026-08-19T22:39:54Z

King Galactix: Added more information on StateNames and the different attack types

Enemy States (Werehog)

2026-08-19T21:39:41Z

King Galactix: Included a heading for StateChartInfo, and relocated the image to the left.

The Werehog's enemies have a character state xml, found in their respective archive files (e.g. #EvilEnemyNightmareR.ar.00 >> EvilEnemyNightmareR.chr.xml). This XML file deals with the different states of the enemies, and how the enemies react to the player's attack types.

{{Notice|type=note|content=Each enemy has distinct states (hard-coded), so we will view common values between enemies.}}

== StateChartInfo ==
[[File:StateChartInfo.png|thumb|The StateChartInfo identifies the enemy's state as "Rise", and receives "KnockOut" when hit with a "KnockBackSoft" attack type from the player.|left]]"StatChart" is what the game calls the StateChart, which contains every individual information of the different states.

"StateChartInfo" represents an individual state of a nighttime enemy. These vary between enemies, but there are common states such as "Tell", "Rise", "Walk", "KnockOut", and so on.

Enemy States (Werehog)

2026-08-19T03:32:29Z

King Galactix:

The Werehog's enemies have a character state xml, found in their respective archive files (e.g. #EvilEnemyNightmareR.ar.00 >> EvilEnemyNightmareR.chr.xml). This XML file deals with the different states of the enemies, and how the enemies react to the player's attack types.

{{Notice|type=note|content=Each enemy has distinct states (hard-coded), so we will view common values between enemies.}}"StateChartInfo" represents an individual state of a nighttime enemy. These vary between enemies, but there are common states such as "Tell", "Rise", "Walk", etc.
[[File:StateChartInfo.png|thumb|333x333px|The StateChartInfo identifies the enemy's state as "Rise", and receives "KnockOut" when hit with a "KnockBackSoft" attack type from the player.]]

File:StateChartInfo.png

2026-08-19T02:53:10Z

King Galactix:

This is an example of a StateChartInfo cell, which identifies the night enemy's state and how it reacts to the player's attack types.

Enemy States (Werehog)

2026-08-18T16:30:49Z

King Galactix:

Enemy States (Nighttime)

2026-08-18T15:51:01Z

King Galactix: Blanked the page

Enemy States (Nighttime)

2026-08-18T15:49:21Z

King Galactix: King Galactix moved page Enemy States (Nighttime) to Enemy States (Werehog): Misspelled title

#REDIRECT [[Enemy States (Werehog)]]

Enemy States (Werehog)

2026-08-18T15:49:21Z

King Galactix: King Galactix moved page Enemy States (Nighttime) to Enemy States (Werehog): Misspelled title

Enemy States (Werehog)

2026-08-18T15:49:02Z

King Galactix:

Enemy States (Werehog)

2026-08-18T15:45:47Z

King Galactix: removed text to relocate

Enemy States (Werehog)

2026-08-17T19:59:33Z

King Galactix: Wrote the initial paragraph for this documentation of the enemy states.

Creating & Customizing Attack Actions (Combo Routes)

2026-07-31T02:00:05Z

King Galactix: adjusted the input registration bulletins for StartFrame, EndFrame, and WEMEF.

The ActionList is a compilation of different ‘Actions’. Actions work together like a family tree, with individual attacks being stems and their connections being branches. All combos are just multiple branches of other moves, spawning a wide range of moveset paths. Here’s an example:

{{Notice|type=example|content=NSA > NSB > NSC > NSD > NSE (YYYYY) = Feral/Normal Were-Hammer

NSA > JF > JKC (Y-XX) = Double Kick Combo

NSA > NSB > SC > SC2 > SD (YY-XXX) = Donkey Kick Combo}}

We’ll go over making custom actions, combinations of the variables and parameters, several cases of Action’s variables, unique methods of move-set inputs, and combining them into one whole move.<syntaxhighlight lang="xml" line="1" start="9547"><Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>
<KEY__YDown>MOVE_B</KEY__YDown>
<KEY__XDown>MOVE_C</KEY__XDown>
<KEY__ADown></KEY__ADown>
<KEY__Land></KEY__Land>
<KEY__AirCombo />
<KEY__End></KEY__End>
<Guard>true</Guard>
<Avoid>true</Avoid>
<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>9</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
<WaitEndMotionSpeed>1</WaitEndMotionSpeed>
<EndMotionSpeed>1</EndMotionSpeed>
<LandStartFrame>-1</LandStartFrame>
<ActionValidHeightMin>-1</ActionValidHeightMin>
</Action></syntaxhighlight>

== Names: ==
Making a custom action is pretty simple. Let’s try making an action called “MOVE_A”, based on the previous Motion “MOVE_A”. We’d start by making the main Action variable and writing down the Action/Motion Name. It’s important to know there’s a few combinations.

* Same Action, Same Motion: This is the default setting for most moves, with an exact Motion translating into an Action.<syntaxhighlight lang="xml" line="1"> <Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A</MotionName>
</Action></syntaxhighlight>

* Different Action, Same Motion: This is generally used in two situations… a) This divides one large move into a few separate pieces of a larger move. A good example is the Werewheel Rush (YYYY-XXXX), a.k.a. the cartwheel move. b) This makes a separate combo but with the same attributes as another. You’d see a couple of examples from ‘Foreign Input System’.<syntaxhighlight lang="xml" line="1"> <Action>
<ActionName>MOVE_A2</ActionName>
<MotionName>MOVE_A</MotionName>
</Action></syntaxhighlight>
* Same Action, Different Motion: This is self-explanatory, since a similar move within a combo, however, has different properties or even entirely different… EVERYTHING! But within the base game, Unleashed Knuckle Sandwich /Wild Combo is a strong example of the same actions but with different properties (which is found in the Unleashed Infinite)<syntaxhighlight lang="xml" line="1"> <Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A3</MotionName>
</Action></syntaxhighlight>
* This here is a very unique situation. We will refer to these as “Root Actions”, which are used for beginning attacks (Ground/Aerial) or Special Attacks within the game. You can add different Motions, but you cannot fully customize OR make a custom “Root Action” without code-modding.
Ground, Straight<syntaxhighlight lang="xml" start="9524"><Action>
<ActionName>Start_YButtonUP</ActionName>
<MotionName>NSA</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>

</Action></syntaxhighlight>Aerial, Hook<syntaxhighlight lang="xml" start="9524"><Action>
<ActionName>Start_Air_XButtonDown</ActionName>
<MotionName>JCA2</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>

</Action></syntaxhighlight>Special Attacks<syntaxhighlight lang="xml" line="1"><Action>
<ActionName>Start_Dash_Air_YButtonDown</ActionName>
<MotionName>DC</MotionName>
<ValidLevel_Min>12</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>

</Action></syntaxhighlight>

== Common Values: ==
Now it’s time to look at the next few Action variables:

* ValidLevel_Min determines at what level a combo is enabled/unlocked
* ValidLevel_Max determines what level a combo is disabled/locked
* We set the respective values at Level 1 (Beginner) and Level 99, unless you want 99 combos or something.
** The top images show the beginner’s Were-Hammer (YYYY), which its finisher had a knockback. At Level 15, this move will be deactivated because of one reason…<syntaxhighlight lang="xml"><Action>
<ActionName>NSD_2</ActionName>
<MotionName>NSD_2</MotionName>
<ValidLevel_Min>1</ValidLevel_Min> 
<ValidLevel_Max>15</ValidLevel_Max> 
</Action></syntaxhighlight>
** … Level 16 is when Feral Were-Hammer unlocks (YYYY-Y)! The new finisher has knockback and the original now has normal damage! Plus, it allows for new combo avenues!<syntaxhighlight lang="xml"> <Action>
<ActionName>NSD</ActionName>
<MotionName>NSD</MotionName>
<ValidLevel_Min>16</ValidLevel_Min> 
<ValidLevel_Max>99</ValidLevel_Max> 
</Action></syntaxhighlight>
*It is important to mention that to disable an old combo and enable a new combo, the preceding action (with the same ActionName) must be follow the same Level Up parameters, where the new combo is included in the preceding action's inputs.<syntaxhighlight lang="xml">

<Action>
<ActionName>NSC</ActionName>
<MotionName>NSC</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>15</ValidLevel_Max>
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>
<KEY__YDown>NSD_2</KEY__YDown>

</Action>

<Action>
<ActionName>NSC</ActionName>
<MotionName>NSC</MotionName>
<ValidLevel_Min>16</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>
<KEY__YDown>NSD</KEY__YDown>

</Action>
</syntaxhighlight>

Let’s look at some other important variables.

* ValidCommon determines if a move works in Normal Mode, using true or false.
* ValidBerserker determines if a move works in Unleashed Mode, using true or false.

* Guard and Avoid (meaning Dodge) are self-explanatory. Enable the ability to guard and dodge when doing an action. It should also be mentioned that neither of these work for aerial combos.
<syntaxhighlight lang="xml">
<Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>

<Guard>true</Guard>
<Avoid>true</Avoid>

</Action>
</syntaxhighlight>

== Creating Combo Routes: ==
Making a combo route is simple, as shown in the example below. Here are MoveA and MoveB, which we want to connect into a consecutive move. It’s as simple as putting the ID for “MOVE_B” into one of the following KEY variables.

* '''KEY__''Button''Down''' transitions to another move by pressing the Y, X, A, or B buttons.
* '''KEY__''Button''UP''' transitions to another move by releasing the Y, X, A, or B buttons, usually before the next input (a.k.a very quickly).
* '''KEY__''Button''Ing''' is an unused input system that is activated by holding inputs for a given length of time, and can overridden ButtonDown and ButtonUp inputs (with bugged limitations).
* '''KEY__Land''' activates a move when the player lands on/falls to the ground.
* '''KEY__AirCombo''' activates when the player is in the air and when the player makes contact with the enemy hitbox.
* '''KEY__End''' activates a move when inputs are no longer received, meaning that you stop pressing ANYTHING.
<syntaxhighlight lang="xml">
<Action>

<KEY__YDown>MOVE_B</KEY__YDown> 
<KEY__YUp></KEY__YUp> 
<KEY__YIng></KEY__YIng> 
<KEY__XDown>MOVE_C</KEY__XDown>
<KEY__XUp></KEY__XUp>
<KEY__XIng></KEY__XIng>
<KEY__ADown></KEY__ADown>
<KEY__AUp></KEY__AUp>
<KEY__AIng></KEY__AIng>
<KEY__BDown>
<KEY__BUp></KEY__BUp>
<KEY__BIng></KEY__BIng>
<KEY__Land></KEY__Land>
<KEY__AirCombo />
<KEY__End></KEY__End>

</Action>
</syntaxhighlight>

== Input Registration: ==
While this is all good, it doesn’t matter if the game can’t register our inputs. We should fix that so you can execute your combo effectively! Let’s focus on the following three variables, which allows you to register the input for the next move:

* KEY__StartFrame is the start value of the input range (inclusive). Any inputs pressed before this frame will not result in the execution of the next input.
* KEY__EndFrame is the end value of the input range (inclusive). Any inputs pressed after this value will not result in the execution of the next input, unless WaitEndMotionEndFrame is set to a value higher than the KEY__EndFrame value.
* WaitEndMotionEndFrame (WEMEF) extends the range time where you can input a combo. This is found in almost all combos besides finishers and certain attacks.
<syntaxhighlight lang="xml">
<Action>

<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>9</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
</Action>
</syntaxhighlight>The three parameters below allow you to register the input while holding down on a button. This section was further documented by MajoraOX.

* KEY__IngStartFrame is the start value of holding the button input.
* KEY__IngEndFrame is the end value of holding the button input. This value is only unresponsive when its value is greater than the EndFrame and/or WEMEF value.
* KEY__IngFrameTIme is the time value of how long you hold the button for. Despite this variable existing, it actually contributes nothing to the frame time, but rather is contributed by a hard coded variable set to 0.12.
<syntaxhighlight lang="xml">
<Action>

<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>9</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
<KEY__IngStartFrame>2</KEY__IngStartFrame>
<KEY__IngEndFrame>9</KEY__IngEndFrame>
<KEY__IngFrameTime>7</KEY__IngFrameTime>
</Action>
</syntaxhighlight>The following variables assist with attack speed and more:

* WaitEndMotionSpeed (WEMS) is the speed of WEMEF, which works inversely proportionately.
* EndMotionSpeed is just the general speed of the whole action.
* LandStartFrame is self-explanatory, which is the frame when the player starts landing.
* ActionValidHeightMin is the minimum height for a move to work.
** Ground moves have a value of -1, so they work on the ground and maybe in the air.
** Aerial Attacks have a value of 1 or 2, which varies between moves.
<syntaxhighlight lang="xml"><Action>

<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>9</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
<WaitEndMotionSpeed>1</WaitEndMotionSpeed>
<EndMotionSpeed>1</EndMotionSpeed>
<LandStartFrame>-1</LandStartFrame>
<ActionValidHeightMin>-1</ActionValidHeightMin>
</Action></syntaxhighlight>

Aerial Attacks follow the same principle but with two new variables:

* AirCatchStartFrame is the frame where the player can use the Aerial Piledriver.
* AddVelocityY increases or decreases the player's upward velocity, depending on whether the value is positive or negative.<syntaxhighlight lang="xml"><Action>

<AirCatchStartFrame>9</AirCatchStartFrame>
<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>9</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
<WaitEndMotionSpeed>1</WaitEndMotionSpeed>
<EndMotionSpeed>1</EndMotionSpeed>
<LandStartFrame>-1</LandStartFrame>
<AddVelocityY>-0.25</AddVelocityY>
<ActionValidHeightMin>-1</ActionValidHeightMin>
</Action></syntaxhighlight>

Special Moves and Attack Finishers have empty Start/End frames, and any variables below have a value of -1.

Creating & Customizing Attack Actions (Combo Routes)

2026-07-31T01:58:07Z

King Galactix: Updated the ButtonIng Input registration section

The ActionList is a compilation of different ‘Actions’. Actions work together like a family tree, with individual attacks being stems and their connections being branches. All combos are just multiple branches of other moves, spawning a wide range of moveset paths. Here’s an example:

{{Notice|type=example|content=NSA > NSB > NSC > NSD > NSE (YYYYY) = Feral/Normal Were-Hammer

NSA > JF > JKC (Y-XX) = Double Kick Combo

NSA > NSB > SC > SC2 > SD (YY-XXX) = Donkey Kick Combo}}

We’ll go over making custom actions, combinations of the variables and parameters, several cases of Action’s variables, unique methods of move-set inputs, and combining them into one whole move.<syntaxhighlight lang="xml" line="1" start="9547"><Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>
<KEY__YDown>MOVE_B</KEY__YDown>
<KEY__XDown>MOVE_C</KEY__XDown>
<KEY__ADown></KEY__ADown>
<KEY__Land></KEY__Land>
<KEY__AirCombo />
<KEY__End></KEY__End>
<Guard>true</Guard>
<Avoid>true</Avoid>
<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>9</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
<WaitEndMotionSpeed>1</WaitEndMotionSpeed>
<EndMotionSpeed>1</EndMotionSpeed>
<LandStartFrame>-1</LandStartFrame>
<ActionValidHeightMin>-1</ActionValidHeightMin>
</Action></syntaxhighlight>

== Names: ==
Making a custom action is pretty simple. Let’s try making an action called “MOVE_A”, based on the previous Motion “MOVE_A”. We’d start by making the main Action variable and writing down the Action/Motion Name. It’s important to know there’s a few combinations.

* Same Action, Same Motion: This is the default setting for most moves, with an exact Motion translating into an Action.<syntaxhighlight lang="xml" line="1"> <Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A</MotionName>
</Action></syntaxhighlight>

* Different Action, Same Motion: This is generally used in two situations… a) This divides one large move into a few separate pieces of a larger move. A good example is the Werewheel Rush (YYYY-XXXX), a.k.a. the cartwheel move. b) This makes a separate combo but with the same attributes as another. You’d see a couple of examples from ‘Foreign Input System’.<syntaxhighlight lang="xml" line="1"> <Action>
<ActionName>MOVE_A2</ActionName>
<MotionName>MOVE_A</MotionName>
</Action></syntaxhighlight>
* Same Action, Different Motion: This is self-explanatory, since a similar move within a combo, however, has different properties or even entirely different… EVERYTHING! But within the base game, Unleashed Knuckle Sandwich /Wild Combo is a strong example of the same actions but with different properties (which is found in the Unleashed Infinite)<syntaxhighlight lang="xml" line="1"> <Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A3</MotionName>
</Action></syntaxhighlight>
* This here is a very unique situation. We will refer to these as “Root Actions”, which are used for beginning attacks (Ground/Aerial) or Special Attacks within the game. You can add different Motions, but you cannot fully customize OR make a custom “Root Action” without code-modding.
Ground, Straight<syntaxhighlight lang="xml" start="9524"><Action>
<ActionName>Start_YButtonUP</ActionName>
<MotionName>NSA</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>

</Action></syntaxhighlight>Aerial, Hook<syntaxhighlight lang="xml" start="9524"><Action>
<ActionName>Start_Air_XButtonDown</ActionName>
<MotionName>JCA2</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>

</Action></syntaxhighlight>Special Attacks<syntaxhighlight lang="xml" line="1"><Action>
<ActionName>Start_Dash_Air_YButtonDown</ActionName>
<MotionName>DC</MotionName>
<ValidLevel_Min>12</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>

</Action></syntaxhighlight>

== Common Values: ==
Now it’s time to look at the next few Action variables:

* ValidLevel_Min determines at what level a combo is enabled/unlocked
* ValidLevel_Max determines what level a combo is disabled/locked
* We set the respective values at Level 1 (Beginner) and Level 99, unless you want 99 combos or something.
** The top images show the beginner’s Were-Hammer (YYYY), which its finisher had a knockback. At Level 15, this move will be deactivated because of one reason…<syntaxhighlight lang="xml"><Action>
<ActionName>NSD_2</ActionName>
<MotionName>NSD_2</MotionName>
<ValidLevel_Min>1</ValidLevel_Min> 
<ValidLevel_Max>15</ValidLevel_Max> 
</Action></syntaxhighlight>
** … Level 16 is when Feral Were-Hammer unlocks (YYYY-Y)! The new finisher has knockback and the original now has normal damage! Plus, it allows for new combo avenues!<syntaxhighlight lang="xml"> <Action>
<ActionName>NSD</ActionName>
<MotionName>NSD</MotionName>
<ValidLevel_Min>16</ValidLevel_Min> 
<ValidLevel_Max>99</ValidLevel_Max> 
</Action></syntaxhighlight>
*It is important to mention that to disable an old combo and enable a new combo, the preceding action (with the same ActionName) must be follow the same Level Up parameters, where the new combo is included in the preceding action's inputs.<syntaxhighlight lang="xml">

<Action>
<ActionName>NSC</ActionName>
<MotionName>NSC</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>15</ValidLevel_Max>
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>
<KEY__YDown>NSD_2</KEY__YDown>

</Action>

<Action>
<ActionName>NSC</ActionName>
<MotionName>NSC</MotionName>
<ValidLevel_Min>16</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>
<KEY__YDown>NSD</KEY__YDown>

</Action>
</syntaxhighlight>

Let’s look at some other important variables.

* ValidCommon determines if a move works in Normal Mode, using true or false.
* ValidBerserker determines if a move works in Unleashed Mode, using true or false.

* Guard and Avoid (meaning Dodge) are self-explanatory. Enable the ability to guard and dodge when doing an action. It should also be mentioned that neither of these work for aerial combos.
<syntaxhighlight lang="xml">
<Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>

<Guard>true</Guard>
<Avoid>true</Avoid>

</Action>
</syntaxhighlight>

== Creating Combo Routes: ==
Making a combo route is simple, as shown in the example below. Here are MoveA and MoveB, which we want to connect into a consecutive move. It’s as simple as putting the ID for “MOVE_B” into one of the following KEY variables.

* '''KEY__''Button''Down''' transitions to another move by pressing the Y, X, A, or B buttons.
* '''KEY__''Button''UP''' transitions to another move by releasing the Y, X, A, or B buttons, usually before the next input (a.k.a very quickly).
* '''KEY__''Button''Ing''' is an unused input system that is activated by holding inputs for a given length of time, and can overridden ButtonDown and ButtonUp inputs (with bugged limitations).
* '''KEY__Land''' activates a move when the player lands on/falls to the ground.
* '''KEY__AirCombo''' activates when the player is in the air and when the player makes contact with the enemy hitbox.
* '''KEY__End''' activates a move when inputs are no longer received, meaning that you stop pressing ANYTHING.
<syntaxhighlight lang="xml">
<Action>

<KEY__YDown>MOVE_B</KEY__YDown> 
<KEY__YUp></KEY__YUp> 
<KEY__YIng></KEY__YIng> 
<KEY__XDown>MOVE_C</KEY__XDown>
<KEY__XUp></KEY__XUp>
<KEY__XIng></KEY__XIng>
<KEY__ADown></KEY__ADown>
<KEY__AUp></KEY__AUp>
<KEY__AIng></KEY__AIng>
<KEY__BDown>
<KEY__BUp></KEY__BUp>
<KEY__BIng></KEY__BIng>
<KEY__Land></KEY__Land>
<KEY__AirCombo />
<KEY__End></KEY__End>

</Action>
</syntaxhighlight>

== Input Registration: ==
While this is all good, it doesn’t matter if the game can’t register our inputs. We should fix that so you can execute your combo effectively! Let’s focus on the following three variables, which allows you to register the input for the next move:

* KEY__StartFrame is the start value of the input range (inclusive). Any inputs pressed before this value will not result in the next input.
* KEY__EndFrame is the end value of the input range (inclusive). Any inputs pressed after this value will not result in the next input, unless WaitEndMotionEndFrame is set to a value higher than 0.
* WaitEndMotionEndFrame (WEMEF) extends the range time where you can input a combo. This is found in almost all combos besides finishers and certain attacks.
<syntaxhighlight lang="xml">
<Action>

<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>9</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
</Action>
</syntaxhighlight>The three parameters below allow you to register the input while holding down on a button. This section was further documented by MajoraOX.

* KEY__IngStartFrame is the start value of holding the button input.
* KEY__IngEndFrame is the end value of holding the button input. This value is only unresponsive when its value is greater than the EndFrame and/or WEMEF value.
* KEY__IngFrameTIme is the time value of how long you hold the button for. Despite this variable existing, it actually contributes nothing to the frame time, but rather is contributed by a hard coded variable set to 0.12.
<syntaxhighlight lang="xml">
<Action>

<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>9</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
<KEY__IngStartFrame>2</KEY__IngStartFrame>
<KEY__IngEndFrame>9</KEY__IngEndFrame>
<KEY__IngFrameTime>7</KEY__IngFrameTime>
</Action>
</syntaxhighlight>The following variables assist with attack speed and more:

* WaitEndMotionSpeed (WEMS) is the speed of WEMEF, which works inversely proportionately.
* EndMotionSpeed is just the general speed of the whole action.
* LandStartFrame is self-explanatory, which is the frame when the player starts landing.
* ActionValidHeightMin is the minimum height for a move to work.
** Ground moves have a value of -1, so they work on the ground and maybe in the air.
** Aerial Attacks have a value of 1 or 2, which varies between moves.
<syntaxhighlight lang="xml"><Action>

<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>9</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
<WaitEndMotionSpeed>1</WaitEndMotionSpeed>
<EndMotionSpeed>1</EndMotionSpeed>
<LandStartFrame>-1</LandStartFrame>
<ActionValidHeightMin>-1</ActionValidHeightMin>
</Action></syntaxhighlight>

Aerial Attacks follow the same principle but with two new variables:

* AirCatchStartFrame is the frame where the player can use the Aerial Piledriver.
* AddVelocityY increases or decreases the player's upward velocity, depending on whether the value is positive or negative.<syntaxhighlight lang="xml"><Action>

<AirCatchStartFrame>9</AirCatchStartFrame>
<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>9</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
<WaitEndMotionSpeed>1</WaitEndMotionSpeed>
<EndMotionSpeed>1</EndMotionSpeed>
<LandStartFrame>-1</LandStartFrame>
<AddVelocityY>-0.25</AddVelocityY>
<ActionValidHeightMin>-1</ActionValidHeightMin>
</Action></syntaxhighlight>

Special Moves and Attack Finishers have empty Start/End frames, and any variables below have a value of -1.

Creating & Customizing Attack Actions (Combo Routes)

2026-07-31T01:54:25Z

King Galactix: Included a disclaimer toward KEY__IngFrameTime

The ActionList is a compilation of different ‘Actions’. Actions work together like a family tree, with individual attacks being stems and their connections being branches. All combos are just multiple branches of other moves, spawning a wide range of moveset paths. Here’s an example:

{{Notice|type=example|content=NSA > NSB > NSC > NSD > NSE (YYYYY) = Feral/Normal Were-Hammer

NSA > JF > JKC (Y-XX) = Double Kick Combo

NSA > NSB > SC > SC2 > SD (YY-XXX) = Donkey Kick Combo}}

We’ll go over making custom actions, combinations of the variables and parameters, several cases of Action’s variables, unique methods of move-set inputs, and combining them into one whole move.<syntaxhighlight lang="xml" line="1" start="9547"><Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>
<KEY__YDown>MOVE_B</KEY__YDown>
<KEY__XDown>MOVE_C</KEY__XDown>
<KEY__ADown></KEY__ADown>
<KEY__Land></KEY__Land>
<KEY__AirCombo />
<KEY__End></KEY__End>
<Guard>true</Guard>
<Avoid>true</Avoid>
<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>9</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
<WaitEndMotionSpeed>1</WaitEndMotionSpeed>
<EndMotionSpeed>1</EndMotionSpeed>
<LandStartFrame>-1</LandStartFrame>
<ActionValidHeightMin>-1</ActionValidHeightMin>
</Action></syntaxhighlight>

== Names: ==
Making a custom action is pretty simple. Let’s try making an action called “MOVE_A”, based on the previous Motion “MOVE_A”. We’d start by making the main Action variable and writing down the Action/Motion Name. It’s important to know there’s a few combinations.

* Same Action, Same Motion: This is the default setting for most moves, with an exact Motion translating into an Action.<syntaxhighlight lang="xml" line="1"> <Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A</MotionName>
</Action></syntaxhighlight>

* Different Action, Same Motion: This is generally used in two situations… a) This divides one large move into a few separate pieces of a larger move. A good example is the Werewheel Rush (YYYY-XXXX), a.k.a. the cartwheel move. b) This makes a separate combo but with the same attributes as another. You’d see a couple of examples from ‘Foreign Input System’.<syntaxhighlight lang="xml" line="1"> <Action>
<ActionName>MOVE_A2</ActionName>
<MotionName>MOVE_A</MotionName>
</Action></syntaxhighlight>
* Same Action, Different Motion: This is self-explanatory, since a similar move within a combo, however, has different properties or even entirely different… EVERYTHING! But within the base game, Unleashed Knuckle Sandwich /Wild Combo is a strong example of the same actions but with different properties (which is found in the Unleashed Infinite)<syntaxhighlight lang="xml" line="1"> <Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A3</MotionName>
</Action></syntaxhighlight>
* This here is a very unique situation. We will refer to these as “Root Actions”, which are used for beginning attacks (Ground/Aerial) or Special Attacks within the game. You can add different Motions, but you cannot fully customize OR make a custom “Root Action” without code-modding.
Ground, Straight<syntaxhighlight lang="xml" start="9524"><Action>
<ActionName>Start_YButtonUP</ActionName>
<MotionName>NSA</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>

</Action></syntaxhighlight>Aerial, Hook<syntaxhighlight lang="xml" start="9524"><Action>
<ActionName>Start_Air_XButtonDown</ActionName>
<MotionName>JCA2</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>

</Action></syntaxhighlight>Special Attacks<syntaxhighlight lang="xml" line="1"><Action>
<ActionName>Start_Dash_Air_YButtonDown</ActionName>
<MotionName>DC</MotionName>
<ValidLevel_Min>12</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>

</Action></syntaxhighlight>

== Common Values: ==
Now it’s time to look at the next few Action variables:

* ValidLevel_Min determines at what level a combo is enabled/unlocked
* ValidLevel_Max determines what level a combo is disabled/locked
* We set the respective values at Level 1 (Beginner) and Level 99, unless you want 99 combos or something.
** The top images show the beginner’s Were-Hammer (YYYY), which its finisher had a knockback. At Level 15, this move will be deactivated because of one reason…<syntaxhighlight lang="xml"><Action>
<ActionName>NSD_2</ActionName>
<MotionName>NSD_2</MotionName>
<ValidLevel_Min>1</ValidLevel_Min> 
<ValidLevel_Max>15</ValidLevel_Max> 
</Action></syntaxhighlight>
** … Level 16 is when Feral Were-Hammer unlocks (YYYY-Y)! The new finisher has knockback and the original now has normal damage! Plus, it allows for new combo avenues!<syntaxhighlight lang="xml"> <Action>
<ActionName>NSD</ActionName>
<MotionName>NSD</MotionName>
<ValidLevel_Min>16</ValidLevel_Min> 
<ValidLevel_Max>99</ValidLevel_Max> 
</Action></syntaxhighlight>
*It is important to mention that to disable an old combo and enable a new combo, the preceding action (with the same ActionName) must be follow the same Level Up parameters, where the new combo is included in the preceding action's inputs.<syntaxhighlight lang="xml">

<Action>
<ActionName>NSC</ActionName>
<MotionName>NSC</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>15</ValidLevel_Max>
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>
<KEY__YDown>NSD_2</KEY__YDown>

</Action>

<Action>
<ActionName>NSC</ActionName>
<MotionName>NSC</MotionName>
<ValidLevel_Min>16</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>
<KEY__YDown>NSD</KEY__YDown>

</Action>
</syntaxhighlight>

Let’s look at some other important variables.

* ValidCommon determines if a move works in Normal Mode, using true or false.
* ValidBerserker determines if a move works in Unleashed Mode, using true or false.

* Guard and Avoid (meaning Dodge) are self-explanatory. Enable the ability to guard and dodge when doing an action. It should also be mentioned that neither of these work for aerial combos.
<syntaxhighlight lang="xml">
<Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>

<Guard>true</Guard>
<Avoid>true</Avoid>

</Action>
</syntaxhighlight>

== Creating Combo Routes: ==
Making a combo route is simple, as shown in the example below. Here are MoveA and MoveB, which we want to connect into a consecutive move. It’s as simple as putting the ID for “MOVE_B” into one of the following KEY variables.

* '''KEY__''Button''Down''' transitions to another move by pressing the Y, X, A, or B buttons.
* '''KEY__''Button''UP''' transitions to another move by releasing the Y, X, A, or B buttons, usually before the next input (a.k.a very quickly).
* '''KEY__''Button''Ing''' is an unused input system that is activated by holding inputs for a given length of time, and can overridden ButtonDown and ButtonUp inputs (with bugged limitations).
* '''KEY__Land''' activates a move when the player lands on/falls to the ground.
* '''KEY__AirCombo''' activates when the player is in the air and when the player makes contact with the enemy hitbox.
* '''KEY__End''' activates a move when inputs are no longer received, meaning that you stop pressing ANYTHING.
<syntaxhighlight lang="xml">
<Action>

<KEY__YDown>MOVE_B</KEY__YDown> 
<KEY__YUp></KEY__YUp> 
<KEY__YIng></KEY__YIng> 
<KEY__XDown>MOVE_C</KEY__XDown>
<KEY__XUp></KEY__XUp>
<KEY__XIng></KEY__XIng>
<KEY__ADown></KEY__ADown>
<KEY__AUp></KEY__AUp>
<KEY__AIng></KEY__AIng>
<KEY__BDown>
<KEY__BUp></KEY__BUp>
<KEY__BIng></KEY__BIng>
<KEY__Land></KEY__Land>
<KEY__AirCombo />
<KEY__End></KEY__End>

</Action>
</syntaxhighlight>

== Input Registration: ==
While this is all good, it doesn’t matter if the game can’t register our inputs. We should fix that so you can execute your combo effectively! Let’s focus on the following three variables, which allows you to register the input for the next move:

* KEY__StartFrame is the start value of the input range (inclusive). Any inputs pressed before this value will not result in the next input.
* KEY__EndFrame is the end value of the input range (inclusive). Any inputs pressed after this value will not result in the next input, unless WaitEndMotionEndFrame is set to a value higher than 0.
* WaitEndMotionEndFrame (WEMEF) extends the range time where you can input a combo. This is found in almost all combos besides finishers and certain attacks.
<syntaxhighlight lang="xml">
<Action>

<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>9</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
</Action>
</syntaxhighlight>The three parameters below allow you to register the input while holding down on a button. This section was further documented by MajoraOX.

* KEY__IngStartFrame is the start value of holding the button input.
* KEY__IngEndFrame is the end value of holding the button input. This value is only unresponsive when its value is greater than the EndFrame and/or WEMEF value.
* KEY__IngFrameTIme is the time value of how long you hold the button for. Despite this variable existing, it actually contributes nothing to the time that it takes for a "ButtonIng" Combo to execute, but rather a hard coded variable set to 0.12 (potentially Daytime Sonic's JumpShortReleaseTime variable).
<syntaxhighlight lang="xml">
<Action>

<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>9</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
<KEY__IngStartFrame>2</KEY__IngStartFrame>
<KEY__IngEndFrame>9</KEY__IngEndFrame>
<KEY__IngFrameTime>7</KEY__IngFrameTime>
</Action>
</syntaxhighlight>The following variables assist with attack speed and more:

* WaitEndMotionSpeed (WEMS) is the speed of WEMEF, which works inversely proportionately.
* EndMotionSpeed is just the general speed of the whole action.
* LandStartFrame is self-explanatory, which is the frame when the player starts landing.
* ActionValidHeightMin is the minimum height for a move to work.
** Ground moves have a value of -1, so they work on the ground and maybe in the air.
** Aerial Attacks have a value of 1 or 2, which varies between moves.
<syntaxhighlight lang="xml"><Action>

<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>9</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
<WaitEndMotionSpeed>1</WaitEndMotionSpeed>
<EndMotionSpeed>1</EndMotionSpeed>
<LandStartFrame>-1</LandStartFrame>
<ActionValidHeightMin>-1</ActionValidHeightMin>
</Action></syntaxhighlight>

Aerial Attacks follow the same principle but with two new variables:

* AirCatchStartFrame is the frame where the player can use the Aerial Piledriver.
* AddVelocityY increases or decreases the player's upward velocity, depending on whether the value is positive or negative.<syntaxhighlight lang="xml"><Action>

<AirCatchStartFrame>9</AirCatchStartFrame>
<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>9</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
<WaitEndMotionSpeed>1</WaitEndMotionSpeed>
<EndMotionSpeed>1</EndMotionSpeed>
<LandStartFrame>-1</LandStartFrame>
<AddVelocityY>-0.25</AddVelocityY>
<ActionValidHeightMin>-1</ActionValidHeightMin>
</Action></syntaxhighlight>

Special Moves and Attack Finishers have empty Start/End frames, and any variables below have a value of -1.

Creating & Customizing Attack Actions (Combo Routes)

2026-07-29T23:43:39Z

King Galactix:

The ActionList is a compilation of different ‘Actions’. Actions work together like a family tree, with individual attacks being stems and their connections being branches. All combos are just multiple branches of other moves, spawning a wide range of moveset paths. Here’s an example:

{{Notice|type=example|content=NSA > NSB > NSC > NSD > NSE (YYYYY) = Feral/Normal Were-Hammer

NSA > JF > JKC (Y-XX) = Double Kick Combo

NSA > NSB > SC > SC2 > SD (YY-XXX) = Donkey Kick Combo}}

We’ll go over making custom actions, combinations of the variables and parameters, several cases of Action’s variables, unique methods of move-set inputs, and combining them into one whole move.<syntaxhighlight lang="xml" line="1" start="9547"><Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>
<KEY__YDown>MOVE_B</KEY__YDown>
<KEY__XDown>MOVE_C</KEY__XDown>
<KEY__ADown></KEY__ADown>
<KEY__Land></KEY__Land>
<KEY__AirCombo />
<KEY__End></KEY__End>
<Guard>true</Guard>
<Avoid>true</Avoid>
<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>9</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
<WaitEndMotionSpeed>1</WaitEndMotionSpeed>
<EndMotionSpeed>1</EndMotionSpeed>
<LandStartFrame>-1</LandStartFrame>
<ActionValidHeightMin>-1</ActionValidHeightMin>
</Action></syntaxhighlight>

== Names: ==
Making a custom action is pretty simple. Let’s try making an action called “MOVE_A”, based on the previous Motion “MOVE_A”. We’d start by making the main Action variable and writing down the Action/Motion Name. It’s important to know there’s a few combinations.

* Same Action, Same Motion: This is the default setting for most moves, with an exact Motion translating into an Action.<syntaxhighlight lang="xml" line="1"> <Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A</MotionName>
</Action></syntaxhighlight>

* Different Action, Same Motion: This is generally used in two situations… a) This divides one large move into a few separate pieces of a larger move. A good example is the Werewheel Rush (YYYY-XXXX), a.k.a. the cartwheel move. b) This makes a separate combo but with the same attributes as another. You’d see a couple of examples from ‘Foreign Input System’.<syntaxhighlight lang="xml" line="1"> <Action>
<ActionName>MOVE_A2</ActionName>
<MotionName>MOVE_A</MotionName>
</Action></syntaxhighlight>
* Same Action, Different Motion: This is self-explanatory, since a similar move within a combo, however, has different properties or even entirely different… EVERYTHING! But within the base game, Unleashed Knuckle Sandwich /Wild Combo is a strong example of the same actions but with different properties (which is found in the Unleashed Infinite)<syntaxhighlight lang="xml" line="1"> <Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A3</MotionName>
</Action></syntaxhighlight>
* This here is a very unique situation. We will refer to these as “Root Actions”, which are used for beginning attacks (Ground/Aerial) or Special Attacks within the game. You can add different Motions, but you cannot fully customize OR make a custom “Root Action” without code-modding.
Ground, Straight<syntaxhighlight lang="xml" start="9524"><Action>
<ActionName>Start_YButtonUP</ActionName>
<MotionName>NSA</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>

</Action></syntaxhighlight>Aerial, Hook<syntaxhighlight lang="xml" start="9524"><Action>
<ActionName>Start_Air_XButtonDown</ActionName>
<MotionName>JCA2</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>

</Action></syntaxhighlight>Special Attacks<syntaxhighlight lang="xml" line="1"><Action>
<ActionName>Start_Dash_Air_YButtonDown</ActionName>
<MotionName>DC</MotionName>
<ValidLevel_Min>12</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>

</Action></syntaxhighlight>

== Common Values: ==
Now it’s time to look at the next few Action variables:

* ValidLevel_Min determines at what level a combo is enabled/unlocked
* ValidLevel_Max determines what level a combo is disabled/locked
* We set the respective values at Level 1 (Beginner) and Level 99, unless you want 99 combos or something.
** The top images show the beginner’s Were-Hammer (YYYY), which its finisher had a knockback. At Level 15, this move will be deactivated because of one reason…<syntaxhighlight lang="xml"><Action>
<ActionName>NSD_2</ActionName>
<MotionName>NSD_2</MotionName>
<ValidLevel_Min>1</ValidLevel_Min> 
<ValidLevel_Max>15</ValidLevel_Max> 
</Action></syntaxhighlight>
** … Level 16 is when Feral Were-Hammer unlocks (YYYY-Y)! The new finisher has knockback and the original now has normal damage! Plus, it allows for new combo avenues!<syntaxhighlight lang="xml"> <Action>
<ActionName>NSD</ActionName>
<MotionName>NSD</MotionName>
<ValidLevel_Min>16</ValidLevel_Min> 
<ValidLevel_Max>99</ValidLevel_Max> 
</Action></syntaxhighlight>
*It is important to mention that to disable an old combo and enable a new combo, the preceding action (with the same ActionName) must be follow the same Level Up parameters, where the new combo is included in the preceding action's inputs.<syntaxhighlight lang="xml">

<Action>
<ActionName>NSC</ActionName>
<MotionName>NSC</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>15</ValidLevel_Max>
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>
<KEY__YDown>NSD_2</KEY__YDown>

</Action>

<Action>
<ActionName>NSC</ActionName>
<MotionName>NSC</MotionName>
<ValidLevel_Min>16</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>
<KEY__YDown>NSD</KEY__YDown>

</Action>
</syntaxhighlight>

Let’s look at some other important variables.

* ValidCommon determines if a move works in Normal Mode, using true or false.
* ValidBerserker determines if a move works in Unleashed Mode, using true or false.

* Guard and Avoid (meaning Dodge) are self-explanatory. Enable the ability to guard and dodge when doing an action. It should also be mentioned that neither of these work for aerial combos.
<syntaxhighlight lang="xml">
<Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>

<Guard>true</Guard>
<Avoid>true</Avoid>

</Action>
</syntaxhighlight>

== Creating Combo Routes: ==
Making a combo route is simple, as shown in the example below. Here are MoveA and MoveB, which we want to connect into a consecutive move. It’s as simple as putting the ID for “MOVE_B” into one of the following KEY variables.

* '''KEY__''Button''Down''' transitions to another move by pressing the Y, X, A, or B buttons.
* '''KEY__''Button''UP''' transitions to another move by releasing the Y, X, A, or B buttons, usually before the next input (a.k.a very quickly).
* '''KEY__''Button''Ing''' is an unused input system that is activated by holding inputs for a given length of time, and can overridden ButtonDown and ButtonUp inputs (with bugged limitations).
* '''KEY__Land''' activates a move when the player lands on/falls to the ground.
* '''KEY__AirCombo''' activates when the player is in the air and when the player makes contact with the enemy hitbox.
* '''KEY__End''' activates a move when inputs are no longer received, meaning that you stop pressing ANYTHING.
<syntaxhighlight lang="xml">
<Action>

<KEY__YDown>MOVE_B</KEY__YDown> 
<KEY__YUp></KEY__YUp> 
<KEY__YIng></KEY__YIng> 
<KEY__XDown>MOVE_C</KEY__XDown>
<KEY__XUp></KEY__XUp>
<KEY__XIng></KEY__XIng>
<KEY__ADown></KEY__ADown>
<KEY__AUp></KEY__AUp>
<KEY__AIng></KEY__AIng>
<KEY__BDown>
<KEY__BUp></KEY__BUp>
<KEY__BIng></KEY__BIng>
<KEY__Land></KEY__Land>
<KEY__AirCombo />
<KEY__End></KEY__End>

</Action>
</syntaxhighlight>

== Input Registration: ==
While this is all good, it doesn’t matter if the game can’t register our inputs. We should fix that so you can execute your combo effectively! Let’s focus on the following three variables, which allows you to register the input for the next move:

* KEY__StartFrame is the start value of the input range (inclusive). Any inputs pressed before this value will not result in the next input.
* KEY__EndFrame is the end value of the input range (inclusive). Any inputs pressed after this value will not result in the next input, unless WaitEndMotionEndFrame is set to a value higher than 0.
* WaitEndMotionEndFrame (WEMEF) extends the range time where you can input a combo. This is found in almost all combos besides finishers and certain attacks.
<syntaxhighlight lang="xml">
<Action>

<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>9</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
</Action>
</syntaxhighlight>The three parameters below allow you to register the input while holding down on a button.

* KEY__IngStartFrame is the start value of holding the button input.
* KEY__IngEndFrame is the end value of holding the button input. This value is only unresponsive when its value is greater than the EndFrame and/or WEMEF value.
* KEY__IngFrameTIme is how long you hold the button for. The button
<syntaxhighlight lang="xml">
<Action>

<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>9</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
<KEY__IngStartFrame>2</KEY__IngStartFrame>
<KEY__IngEndFrame>9</KEY__IngEndFrame>
<KEY__IngFrameTime>7</KEY__IngFrameTime>
</Action>
</syntaxhighlight>The following variables assist with attack speed and more:

* WaitEndMotionSpeed (WEMS) is the speed of WEMEF, which works inversely proportionately.
* EndMotionSpeed is just the general speed of the whole action.
* LandStartFrame is self-explanatory, which is the frame when the player starts landing.
* ActionValidHeightMin is the minimum height for a move to work.
** Ground moves have a value of -1, so they work on the ground and maybe in the air.
** Aerial Attacks have a value of 1 or 2, which varies between moves.
<syntaxhighlight lang="xml"><Action>

<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>9</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
<WaitEndMotionSpeed>1</WaitEndMotionSpeed>
<EndMotionSpeed>1</EndMotionSpeed>
<LandStartFrame>-1</LandStartFrame>
<ActionValidHeightMin>-1</ActionValidHeightMin>
</Action></syntaxhighlight>

Aerial Attacks follow the same principle but with two new variables:

* AirCatchStartFrame is the frame where the player can use the Aerial Piledriver.
* AddVelocityY increases or decreases the player's upward velocity, depending on whether the value is positive or negative.<syntaxhighlight lang="xml"><Action>

<AirCatchStartFrame>9</AirCatchStartFrame>
<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>9</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
<WaitEndMotionSpeed>1</WaitEndMotionSpeed>
<EndMotionSpeed>1</EndMotionSpeed>
<LandStartFrame>-1</LandStartFrame>
<AddVelocityY>-0.25</AddVelocityY>
<ActionValidHeightMin>-1</ActionValidHeightMin>
</Action></syntaxhighlight>

Special Moves and Attack Finishers have empty Start/End frames, and any variables below have a value of -1.

Creating & Customizing Attack Actions (Combo Routes)

2026-07-29T23:27:53Z

King Galactix:

The ActionList is a compilation of different ‘Actions’. Actions work together like a family tree, with individual attacks being stems and their connections being branches. All combos are just multiple branches of other moves, spawning a wide range of moveset paths. Here’s an example:

{{Notice|type=example|content=NSA > NSB > NSC > NSD > NSE (YYYYY) = Feral/Normal Were-Hammer

NSA > JF > JKC (Y-XX) = Double Kick Combo

NSA > NSB > SC > SC2 > SD (YY-XXX) = Donkey Kick Combo}}

We’ll go over making custom actions, combinations of the variables and parameters, several cases of Action’s variables, unique methods of move-set inputs, and combining them into one whole move.<syntaxhighlight lang="xml" line="1" start="9547"><Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>
<KEY__YDown>MOVE_B</KEY__YDown>
<KEY__XDown>MOVE_C</KEY__XDown>
<KEY__ADown></KEY__ADown>
<KEY__Land></KEY__Land>
<KEY__AirCombo />
<KEY__End></KEY__End>
<Guard>true</Guard>
<Avoid>true</Avoid>
<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>9</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
<WaitEndMotionSpeed>1</WaitEndMotionSpeed>
<EndMotionSpeed>1</EndMotionSpeed>
<LandStartFrame>-1</LandStartFrame>
<ActionValidHeightMin>-1</ActionValidHeightMin>
</Action></syntaxhighlight>

== Names: ==
Making a custom action is pretty simple. Let’s try making an action called “MOVE_A”, based on the previous Motion “MOVE_A”. We’d start by making the main Action variable and writing down the Action/Motion Name. It’s important to know there’s a few combinations.

* Same Action, Same Motion: This is the default setting for most moves, with an exact Motion translating into an Action.<syntaxhighlight lang="xml" line="1"> <Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A</MotionName>
</Action></syntaxhighlight>

* Different Action, Same Motion: This is generally used in two situations… a) This divides one large move into a few separate pieces of a larger move. A good example is the Werewheel Rush (YYYY-XXXX), a.k.a. the cartwheel move. b) This makes a separate combo but with the same attributes as another. You’d see a couple of examples from ‘Foreign Input System’.<syntaxhighlight lang="xml" line="1"> <Action>
<ActionName>MOVE_A2</ActionName>
<MotionName>MOVE_A</MotionName>
</Action></syntaxhighlight>
* Same Action, Different Motion: This is self-explanatory, since a similar move within a combo, however, has different properties or even entirely different… EVERYTHING! But within the base game, Unleashed Knuckle Sandwich /Wild Combo is a strong example of the same actions but with different properties (which is found in the Unleashed Infinite)<syntaxhighlight lang="xml" line="1"> <Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A3</MotionName>
</Action></syntaxhighlight>
* This here is a very unique situation. We will refer to these as “Root Actions”, which are used for beginning attacks (Ground/Aerial) or Special Attacks within the game. You can add different Motions, but you cannot fully customize OR make a custom “Root Action” without code-modding.
Ground, Straight<syntaxhighlight lang="xml" start="9524"><Action>
<ActionName>Start_YButtonUP</ActionName>
<MotionName>NSA</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>

</Action></syntaxhighlight>Aerial, Hook<syntaxhighlight lang="xml" start="9524"><Action>
<ActionName>Start_Air_XButtonDown</ActionName>
<MotionName>JCA2</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>

</Action></syntaxhighlight>Special Attacks<syntaxhighlight lang="xml" line="1"><Action>
<ActionName>Start_Dash_Air_YButtonDown</ActionName>
<MotionName>DC</MotionName>
<ValidLevel_Min>12</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>

</Action></syntaxhighlight>

== Common Values: ==
Now it’s time to look at the next few Action variables:

* ValidLevel_Min determines at what level a combo is enabled/unlocked
* ValidLevel_Max determines what level a combo is disabled/locked
* We set the respective values at Level 1 (Beginner) and Level 99, unless you want 99 combos or something.
** The top images show the beginner’s Were-Hammer (YYYY), which its finisher had a knockback. At Level 15, this move will be deactivated because of one reason…<syntaxhighlight lang="xml">
<Action>
<ActionName>NSD_2</ActionName>
<MotionName>NSD_2</MotionName>
<ValidLevel_Min>1</ValidLevel_Min> 
<ValidLevel_Max>15</ValidLevel_Max> 
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>
<KEY__YDown></KEY__YDown>
<KEY__XDown></KEY__XDown>
<KEY__ADown></KEY__ADown>
<KEY__Land></KEY__Land>
<KEY__AirCombo></KEY__AirCombo>
<KEY__End></KEY__End>
<Guard>true</Guard>
<Avoid>true</Avoid>
<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>13</KEY__EndFrame>
<WaitEndMotionEndFrame>-1</WaitEndMotionEndFrame>
<WaitEndMotionSpeed>-1</WaitEndMotionSpeed>
<EndMotionSpeed>-1</EndMotionSpeed>
<LandStartFrame>-1</LandStartFrame>
<ActionValidHeightMin>-1</ActionValidHeightMin>
</Action>
</syntaxhighlight>
** … Level 16 is when Feral Were-Hammer unlocks (YYYY-Y)! The new finisher has knockback and the original now has normal damage! Plus, it allows for new combo avenues!<syntaxhighlight lang="xml">
<Action>
<ActionName>NSD</ActionName>
<MotionName>NSD</MotionName>
<ValidLevel_Min>16</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>
<KEY__YDown>NSE</KEY__YDown>
<KEY__XDown>JH1S</KEY__XDown>
<KEY__ADown>JDH</KEY__ADown>
<KEY__Land></KEY__Land>
<KEY__AirCombo></KEY__AirCombo>
<KEY__End></KEY__End>
<Guard>true</Guard>
<Avoid>true</Avoid>
<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>13</KEY__EndFrame>
<WaitEndMotionEndFrame>21</WaitEndMotionEndFrame>
<WaitEndMotionSpeed>0.5</WaitEndMotionSpeed>
<EndMotionSpeed>1</EndMotionSpeed>
<LandStartFrame>-1</LandStartFrame>
<ActionValidHeightMin>-1</ActionValidHeightMin>
</Action>
</syntaxhighlight>

Let’s look at some other variables. These are fairly important.

* ValidCommon determines if a move works in Normal Mode, using true or false.
* ValidBerserker determines if a move works in Unleashed Mode, using true or false.

* Guard and Avoid (meaning Dodge) are self-explanatory. Enable the ability to guard and dodge when doing an action. It should also be mentioned that neither of these work for aerial combos.
<syntaxhighlight lang="xml">
<Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>

<Guard>true</Guard>
<Avoid>true</Avoid>

</Action>
</syntaxhighlight>

== Creating Combo Routes: ==
Making a combo route is simple, as shown in the example below. Here are MoveA and MoveB, which we want to connect into a consecutive move. It’s as simple as putting the ID for “MOVE_B” into one of the following KEY variables.

* '''KEY__''Button''Down''' transitions to another move by pressing the Y, X, A, or B buttons.
* '''KEY__''Button''UP''' transitions to another move by releasing the Y, X, A, or B buttons, usually before the next input (a.k.a very quickly).
* '''KEY__''Button''Ing''' is an unused input system that is activated by holding inputs for a given length of time, and can overridden ButtonDown and ButtonUp inputs (with bugged limitations).
* '''KEY__Land''' activates a move when the player lands on/falls to the ground.
* '''KEY__AirCombo''' activates when the player is in the air and when the player makes contact with the enemy hitbox.
* '''KEY__End''' activates a move when inputs are no longer received, meaning that you stop pressing ANYTHING.
<syntaxhighlight lang="xml">
<Action>

<KEY__YDown>MOVE_B</KEY__YDown> 
<KEY__YUp></KEY__YUp> 
<KEY__YIng></KEY__YIng> 
<KEY__XDown>MOVE_C</KEY__XDown>
<KEY__XUp></KEY__XUp>
<KEY__XIng></KEY__XIng>
<KEY__ADown></KEY__ADown>
<KEY__AUp></KEY__AUp>
<KEY__AIng></KEY__AIng>
<KEY__BDown>
<KEY__BUp></KEY__BUp>
<KEY__BIng></KEY__BIng>
<KEY__Land></KEY__Land>
<KEY__AirCombo />
<KEY__End></KEY__End>

</Action>
</syntaxhighlight>

== Input Registration: ==
While this is all good, it doesn’t matter if the game can’t register our inputs. We should fix that so you can execute your combo effectively! Let’s focus on the following three variables, which allows you to register the input for the next move:

* KEY__StartFrame is the start value of the input range (inclusive). Any inputs pressed before this value will not result in the next input.
* KEY__EndFrame is the end value of the input range (inclusive). Any inputs pressed after this value will not result in the next input, unless WaitEndMotionEndFrame is set to a value higher than 0.
* WaitEndMotionEndFrame (WEMEF) extends the range time where you can input a combo. This is found in almost all combos besides finishers and certain attacks.
<syntaxhighlight lang="xml">
<Action>

<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>9</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
</Action>
</syntaxhighlight>The three parameters below allow you to register the input while holding down on a button.

* KEY__IngStartFrame is the start value of holding the button input.
* KEY__IngEndFrame is the end value of holding the button input. This value is only unresponsive when its value is greater than the EndFrame and/or WEMEF value.
* KEY__IngFrameTIme is how long you hold the button for. The button
<syntaxhighlight lang="xml">
<Action>

<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>9</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
<KEY__IngStartFrame>2</KEY__IngStartFrame>
<KEY__IngEndFrame>9</KEY__IngEndFrame>
<KEY__IngFrameTime>7</KEY__IngFrameTime>
</Action>
</syntaxhighlight>The following variables assist with attack speed and more:

* WaitEndMotionSpeed (WEMS) is the speed of WEMEF, which works inversely proportionately.
* EndMotionSpeed is just the general speed of the whole action.
* LandStartFrame is self-explanatory, which is the frame when the player starts landing.
* ActionValidHeightMin is the minimum height for a move to work.
** Ground moves have a value of -1, so they work on the ground and maybe in the air.
** Aerial Attacks have a value of 1 or 2, which varies between moves.
<syntaxhighlight lang="xml"><Action>

<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>9</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
<WaitEndMotionSpeed>1</WaitEndMotionSpeed>
<EndMotionSpeed>1</EndMotionSpeed>
<LandStartFrame>-1</LandStartFrame>
<ActionValidHeightMin>-1</ActionValidHeightMin>
</Action></syntaxhighlight>

Aerial Attacks follow the same principle but with two new variables:

* AirCatchStartFrame is the frame where the player can use the Aerial Piledriver.
* AddVelocityY increases or decreases the player's upward velocity, depending on whether the value is positive or negative.<syntaxhighlight lang="xml"><Action>

<AirCatchStartFrame>9</AirCatchStartFrame>
<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>9</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
<WaitEndMotionSpeed>1</WaitEndMotionSpeed>
<EndMotionSpeed>1</EndMotionSpeed>
<LandStartFrame>-1</LandStartFrame>
<AddVelocityY>-0.25</AddVelocityY>
<ActionValidHeightMin>-1</ActionValidHeightMin>
</Action></syntaxhighlight>

Special Moves and Attack Finishers have empty Start/End frames, and any variables below have a value of -1.

Creating & Customizing Attack Actions (Combo Routes)

2026-07-29T23:22:35Z

King Galactix:

The ActionList is a compilation of different ‘Actions’. Actions work together like a family tree, with individual attacks being stems and their connections being branches. All combos are just multiple branches of other moves, spawning a wide range of moveset paths. Here’s an example:

{{Notice|type=example|content=NSA > NSB > NSC > NSD > NSE (YYYYY) = Feral/Normal Were-Hammer

NSA > JF > JKC (Y-XX) = Double Kick Combo

NSA > NSB > SC > SC2 > SD (YY-XXX) = Donkey Kick Combo}}

We’ll go over making custom actions, combinations of the variables and parameters, several cases of Action’s variables, unique methods of move-set inputs, and combining them into one whole move.<syntaxhighlight lang="xml" line="1" start="9547"><Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>
<KEY__YDown>MOVE_B</KEY__YDown>
<KEY__XDown>MOVE_C</KEY__XDown>
<KEY__ADown></KEY__ADown>
<KEY__Land></KEY__Land>
<KEY__AirCombo />
<KEY__End></KEY__End>
<Guard>true</Guard>
<Avoid>true</Avoid>
<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>9</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
<WaitEndMotionSpeed>1</WaitEndMotionSpeed>
<EndMotionSpeed>1</EndMotionSpeed>
<LandStartFrame>-1</LandStartFrame>
<ActionValidHeightMin>-1</ActionValidHeightMin>
</Action></syntaxhighlight>

== Names: ==
Making a custom action is pretty simple. Let’s try making an action called “MOVE_A”, based on the previous Motion “MOVE_A”. We’d start by making the main Action variable and writing down the Action/Motion Name. It’s important to know there’s a few combinations.

* Same Action, Same Motion: This is the default setting for most moves, with an exact Motion translating into an Action.<syntaxhighlight lang="xml" line="1"> <Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A</MotionName>
</Action></syntaxhighlight>

* Different Action, Same Motion: This is generally used in two situations… a) This divides one large move into a few separate pieces of a larger move. A good example is the Werewheel Rush (YYYY-XXXX), a.k.a. the cartwheel move. b) This makes a separate combo but with the same attributes as another. You’d see a couple of examples from ‘Foreign Input System’.<syntaxhighlight lang="xml" line="1"> <Action>
<ActionName>MOVE_A2</ActionName>
<MotionName>MOVE_A</MotionName>
</Action></syntaxhighlight>
* Same Action, Different Motion: This is self-explanatory, since a similar move within a combo, however, has different properties or even entirely different… EVERYTHING! But within the base game, Unleashed Knuckle Sandwich /Wild Combo is a strong example of the same actions but with different properties (which is found in the Unleashed Infinite)<syntaxhighlight lang="xml" line="1"> <Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A3</MotionName>
</Action></syntaxhighlight>
* This here is a very unique situation. We will refer to these as “Root Actions”, which are used for beginning attacks (Ground/Aerial) or Special Attacks within the game. You can add different Motions, but you cannot fully customize OR make a custom “Root Action” without code-modding.
Ground, Straight<syntaxhighlight lang="xml" start="9524"><Action>
<ActionName>Start_YButtonUP</ActionName>
<MotionName>NSA</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>

</Action></syntaxhighlight>Aerial, Hook<syntaxhighlight lang="xml" start="9524"><Action>
<ActionName>Start_Air_XButtonDown</ActionName>
<MotionName>JCA2</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>

</Action></syntaxhighlight>Special Attacks<syntaxhighlight lang="xml" line="1"><Action>
<ActionName>Start_Dash_Air_YButtonDown</ActionName>
<MotionName>DC</MotionName>
<ValidLevel_Min>12</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>

</Action></syntaxhighlight>

== Common Values: ==
Now it’s time to look at the next few Action variables:

* ValidLevel_Min determines at what level a combo is enabled/unlocked
* ValidLevel_Max determines what level a combo is disabled/locked
* We set the respective values at Level 1 (Beginner) and Level 99, unless you want 99 combos or something.
** The top images show the beginner’s Were-Hammer (YYYY), which its finisher had a knockback. At Level 15, this move will be deactivated because of one reason…<syntaxhighlight lang="xml">
<Action>
<ActionName>NSD_2</ActionName>
<MotionName>NSD_2</MotionName>
<ValidLevel_Min>1</ValidLevel_Min> 
<ValidLevel_Max>15</ValidLevel_Max> 
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>
<KEY__YDown></KEY__YDown>
<KEY__XDown></KEY__XDown>
<KEY__ADown></KEY__ADown>
<KEY__Land></KEY__Land>
<KEY__AirCombo></KEY__AirCombo>
<KEY__End></KEY__End>
<Guard>true</Guard>
<Avoid>true</Avoid>
<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>13</KEY__EndFrame>
<WaitEndMotionEndFrame>-1</WaitEndMotionEndFrame>
<WaitEndMotionSpeed>-1</WaitEndMotionSpeed>
<EndMotionSpeed>-1</EndMotionSpeed>
<LandStartFrame>-1</LandStartFrame>
<ActionValidHeightMin>-1</ActionValidHeightMin>
</Action>
</syntaxhighlight>
** … Level 16 is when Feral Were-Hammer unlocks (YYYY-Y)! The new finisher has knockback and the original now has normal damage! Plus, it allows for new combo avenues!<syntaxhighlight lang="xml">
<Action>
<ActionName>NSD</ActionName>
<MotionName>NSD</MotionName>
<ValidLevel_Min>16</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>
<KEY__YDown>NSE</KEY__YDown>
<KEY__XDown>JH1S</KEY__XDown>
<KEY__ADown>JDH</KEY__ADown>
<KEY__Land></KEY__Land>
<KEY__AirCombo></KEY__AirCombo>
<KEY__End></KEY__End>
<Guard>true</Guard>
<Avoid>true</Avoid>
<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>13</KEY__EndFrame>
<WaitEndMotionEndFrame>21</WaitEndMotionEndFrame>
<WaitEndMotionSpeed>0.5</WaitEndMotionSpeed>
<EndMotionSpeed>1</EndMotionSpeed>
<LandStartFrame>-1</LandStartFrame>
<ActionValidHeightMin>-1</ActionValidHeightMin>
</Action>
</syntaxhighlight>

Let’s look at some other variables. These are fairly important.

* ValidCommon determines if a move works in Normal Mode, using true or false.
* ValidBerserker determines if a move works in Unleashed Mode, using true or false.

* Guard and Avoid (meaning Dodge) are self-explanatory. Enable the ability to guard and dodge when doing an action. It should also be mentioned that neither of these work for aerial combos.
<syntaxhighlight lang="xml">
<Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>

<Guard>true</Guard>
<Avoid>true</Avoid>

</Action>
</syntaxhighlight>

== Creating Combo Routes: ==
Making a combo route is simple, as shown in the example below. Here are MoveA and MoveB, which we want to connect into a consecutive move. It’s as simple as putting the ID for “MOVE_B” into one of the following KEY variables.

* '''KEY__''Button''Down''' transitions to another move by pressing the Y, X, A, or B buttons.
* '''KEY__''Button''UP''' transitions to another move by releasing the Y, X, A, or B buttons, usually before the next input (a.k.a very quickly).
* '''KEY__''Button''Ing''' is an unused input system that is activated by holding inputs for a given length of time, and can overridden ButtonDown and ButtonUp inputs (with bugged limitations).
* '''KEY__Land''' activates a move when the player lands on/falls to the ground.
* '''KEY__AirCombo''' activates when the player is in the air and when the player makes contact with the enemy hitbox.
* '''KEY__End''' activates a move when inputs are no longer received, meaning that you stop pressing ANYTHING.
<syntaxhighlight lang="xml">
<Action>

<KEY__YDown>MOVE_B</KEY__YDown> 
<KEY__YUp></KEY__YUp> 
<KEY__YIng></KEY__YIng> 
<KEY__XDown>MOVE_C</KEY__XDown>
<KEY__XUp></KEY__XUp>
<KEY__XIng></KEY__XIng>
<KEY__ADown></KEY__ADown>
<KEY__AUp></KEY__AUp>
<KEY__AIng></KEY__AIng>
<KEY__BDown>
<KEY__BUp></KEY__BUp>
<KEY__BIng></KEY__BIng>
<KEY__Land></KEY__Land>
<KEY__AirCombo />
<KEY__End></KEY__End>

</Action>
</syntaxhighlight>

== Input Registration: ==
While this is all good, it doesn’t matter if the game can’t register our inputs. We should fix that so you can execute your combo effectively! Let’s focus on the following three variables, which allows you to register the input for the next move:

* KEY__StartFrame is the start value of the input range (inclusive). Any inputs pressed before this value will not result in the next input.
* KEY__EndFrame is the end value of the input range (inclusive). Any inputs pressed after this value will not result in the next input, unless WaitEndMotionEndFrame is set to a value higher than 0.
* WaitEndMotionEndFrame (WEMEF) extends the range time where you can input a combo. This is found in almost all combos besides finishers and certain attacks.
<syntaxhighlight lang="xml">
<Action>

<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>9</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
</Action>
</syntaxhighlight>The three parameters below allow you to register the input while holding down on a button.

* KEY__IngStartFrame is the start value of holding the button input.
* KEY__IngEndFrame is the end value of holding the button input. This value is only unresponsive when its value is greater than the EndFrame and/or WEMEF value.
* KEY__IngFrameTIme is how long you hold the button for. The button
<syntaxhighlight lang="xml">
<Action>

<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>9</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
<KEY__IngStartFrame>2</KEY__IngStartFrame>
<KEY__IngEndFrame>9</KEY__IngEndFrame>
<KEY__IngFrameTime>7</KEY__IngFrameTime>
</Action>
</syntaxhighlight>The following variables assist with attack speed and more:

* WaitEndMotionSpeed (WEMS) is the speed of WEMEF, which works inversely proportionately.
* EndMotionSpeed is just the general speed of the whole action.
* LandStartFrame is self-explanatory, so most moves have a ‘-1’ value… with exception.
* ActionValidHeightMin is the minimum height for a move to work. a) Ground moves have a value of -1, so they work on the ground and maybe in the air. b) Aerial Attacks have a value of 1 or 2, which varies between moves.

Aerial Attacks follow the same principle but with two new variables:

* AirCatchStartFrame is the frame where the player can use the Aerial Piledriver.
* AddVelocityY increases or decreases the player's upward velocity, depending on whether the value is positive or negative.

Special Moves and Attack Finishers have empty Start/End frames, and any variables below have a value of -1.

Creating & Customizing Attack Actions (Combo Routes)

2026-07-29T23:11:29Z

King Galactix:

The ActionList is a compilation of different ‘Actions’. Actions work together like a family tree, with individual attacks being stems and their connections being branches. All combos are just multiple branches of other moves, spawning a wide range of moveset paths. Here’s an example:

{{Notice|type=example|content=NSA > NSB > NSC > NSD > NSE (YYYYY) = Feral/Normal Were-Hammer

NSA > JF > JKC (Y-XX) = Double Kick Combo

NSA > NSB > SC > SC2 > SD (YY-XXX) = Donkey Kick Combo}}

We’ll go over making custom actions, combinations of the variables and parameters, several cases of Action’s variables, unique methods of move-set inputs, and combining them into one whole move.<syntaxhighlight lang="xml" line="1" start="9547"> <Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>
<KEY__YDown>NSB</KEY__YDown>
<KEY__XDown>JF</KEY__XDown>
<KEY__ADown></KEY__ADown>
<KEY__Land></KEY__Land>
<KEY__AirCombo />
<KEY__End></KEY__End>
<Guard>true</Guard>
<Avoid>true</Avoid>
<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>9</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
<WaitEndMotionSpeed>1</WaitEndMotionSpeed>
<EndMotionSpeed>1</EndMotionSpeed>
<LandStartFrame>-1</LandStartFrame>
<ActionValidHeightMin>-1</ActionValidHeightMin>
</Action></syntaxhighlight>

== Names: ==
Making a custom action is pretty simple. Let’s try making an action called “MOVE_A”, based on the previous Motion “MOVE_A”. We’d start by making the main Action variable and writing down the Action/Motion Name. It’s important to know there’s a few combinations.

* Same Action, Same Motion: This is the default setting for most moves, with an exact Motion translating into an Action.<syntaxhighlight lang="xml" line="1"> <Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A</MotionName>
</Action></syntaxhighlight>

* Different Action, Same Motion: This is generally used in two situations… a) This divides one large move into a few separate pieces of a larger move. A good example is the Werewheel Rush (YYYY-XXXX), a.k.a. the cartwheel move. b) This makes a separate combo but with the same attributes as another. You’d see a couple of examples from ‘Foreign Input System’.<syntaxhighlight lang="xml" line="1"> <Action>
<ActionName>MOVE_A2</ActionName>
<MotionName>MOVE_A</MotionName>
</Action></syntaxhighlight>
* Same Action, Different Motion: This is self-explanatory, since a similar move within a combo, however, has different properties or even entirely different… EVERYTHING! But within the base game, Unleashed Knuckle Sandwich /Wild Combo is a strong example of the same actions but with different properties (which is found in the Unleashed Infinite)<syntaxhighlight lang="xml" line="1"> <Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A3</MotionName>
</Action></syntaxhighlight>
* This here is a very unique situation. We will refer to these as “Root Actions”, which are used for beginning attacks (Ground/Aerial) or Special Attacks within the game. You can add different Motions, but you cannot fully customize OR make a custom “Root Action” without code-modding.
Ground, Straight<syntaxhighlight lang="xml" start="9524"><Action>
<ActionName>Start_YButtonUP</ActionName>
<MotionName>NSA</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>

</Action></syntaxhighlight>Aerial, Hook<syntaxhighlight lang="xml" start="9524"><Action>
<ActionName>Start_Air_XButtonDown</ActionName>
<MotionName>JCA2</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>

</Action></syntaxhighlight>Special Attacks<syntaxhighlight lang="xml" line="1"><Action>
<ActionName>Start_Dash_Air_YButtonDown</ActionName>
<MotionName>DC</MotionName>
<ValidLevel_Min>12</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>

</Action></syntaxhighlight>

== Common Values: ==
Now it’s time to look at the next few Action variables:

* ValidLevel_Min determines at what level a combo is enabled/unlocked
* ValidLevel_Max determines what level a combo is disabled/locked
* We set the respective values at Level 1 (Beginner) and Level 99, unless you want 99 combos or something.
** The top images show the beginner’s Were-Hammer (YYYY), which its finisher had a knockback. At Level 15, this move will be deactivated because of one reason…<syntaxhighlight lang="xml">
<Action>
<ActionName>NSD_2</ActionName>
<MotionName>NSD_2</MotionName>
<ValidLevel_Min>1</ValidLevel_Min> 
<ValidLevel_Max>15</ValidLevel_Max> 
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>
<KEY__YDown></KEY__YDown>
<KEY__XDown></KEY__XDown>
<KEY__ADown></KEY__ADown>
<KEY__Land></KEY__Land>
<KEY__AirCombo></KEY__AirCombo>
<KEY__End></KEY__End>
<Guard>true</Guard>
<Avoid>true</Avoid>
<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>13</KEY__EndFrame>
<WaitEndMotionEndFrame>-1</WaitEndMotionEndFrame>
<WaitEndMotionSpeed>-1</WaitEndMotionSpeed>
<EndMotionSpeed>-1</EndMotionSpeed>
<LandStartFrame>-1</LandStartFrame>
<ActionValidHeightMin>-1</ActionValidHeightMin>
</Action>
</syntaxhighlight>
** … Level 16 is when Feral Were-Hammer unlocks (YYYY-Y)! The new finisher has knockback and the original now has normal damage! Plus, it allows for new combo avenues!

Let’s look at some other variables, then. These are fairly important.

* ValidCommon determines if a move works in Normal Mode
* ValidBerserker determines if a move works in Unleash Mode

A few combinations of the two allow for the creation of moves meant ONLY for Normal or Unleash Mode. The Unleash Infinites primarily use this, but you can also make regular infinite attacks.

* Guard and Avoid (meaning Dodge) are self-explanatory. Enable them for ground moves, and disable them for Aerial moves.
<syntaxhighlight lang="xml">
<Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>

<Guard>true</Guard>
<Avoid>true</Avoid>

</Action>
</syntaxhighlight>

== Creating Combo Routes: ==
Making a combo route is simple, as shown in the example below. Here are MoveA and MoveB, which we want to connect into a consecutive move. It’s as simple as putting the ID for “MOVE_B” into one of the following KEY variables.

* '''KEY__''Button''Down''' transitions to another move by pressing the Y, X, A, or B buttons.
* '''KEY__''Button''UP''' transitions to another move by releasing the Y, X, A, or B buttons, usually before the next input (a.k.a very quickly).
* '''KEY__''Button''Ing''' is an unused input system that is activated by holding inputs for a given length of time, and can overridden ButtonDown and ButtonUp inputs (with bugged limitations).
* '''KEY__Land''' activates a move when the player lands on/falls to the ground.
* '''KEY__AirCombo''' activates when the player is in the air and when the player makes contact with the enemy hitbox.
* '''KEY__End''' activates a move when inputs are no longer received, meaning that you stop pressing ANYTHING.

== Input Registration: ==
While this is all good, it doesn’t matter if the game can’t register our inputs. We should fix that so you can execute your combo effectively! Let’s focus on the following three variables, which allows you to register the input for the next move:

* KEY__StartFrame is the start value of the input range (inclusive). Any inputs pressed before this value will not result in the next input.
* KEY__EndFrame is the end value of the input range (inclusive). Any inputs pressed after this value will not result in the next input, unless WaitEndMotionEndFrame is set to a value higher than 0.
* WaitEndMotionEndFrame (WEMEF) extends the range time where you can input a combo. This is found in almost all combos besides finishers and certain attacks.

The three parameters below allow you to register the input while holding down on a button.

* KEY__IngStartFrame is the start value of holding the button input.
* KEY__IngEndFrame is the end value of holding the button input. This value is only unresponsive when its value is greater than the EndFrame and/or WEMEF value.
* KEY__IngFrameTIme is how long you hold the button for.

The following variables assist with attack speed and more:

* WaitEndMotionSpeed (WEMS) is the speed of WEMEF, which works inversely proportionately.
* EndMotionSpeed is just the general speed of the whole action.
* LandStartFrame is self-explanatory, so most moves have a ‘-1’ value… with exception.
* ActionValidHeightMin is the minimum height for a move to work. a) Ground moves have a value of -1, so they work on the ground and maybe in the air. b) Aerial Attacks have a value of 1 or 2, which varies between moves.

Aerial Attacks follow the same principle but with two new variables:

* AirCatchStartFrame is the frame where the player can use the Aerial Piledriver.
* AddVelocityY increases or decreases the player's upward velocity, depending on whether the value is positive or negative.

Special Moves and Attack Finishers have empty Start/End frames, and any variables below have a value of -1.

Creating & Customizing Attack Actions (Combo Routes)

2026-07-29T23:08:28Z

King Galactix:

The ActionList is a compilation of different ‘Actions’. Actions work together like a family tree, with individual attacks being stems and their connections being branches. All combos are just multiple branches of other moves, spawning a wide range of moveset paths. Here’s an example:

{{Notice|type=example|content=NSA > NSB > NSC > NSD > NSE (YYYYY) = Feral/Normal Were-Hammer

NSA > JF > JKC (Y-XX) = Double Kick Combo

NSA > NSB > SC > SC2 > SD (YY-XXX) = Donkey Kick Combo}}

We’ll go over making custom actions, combinations of the variables and parameters, several cases of Action’s variables, unique methods of move-set inputs, and combining them into one whole move.<syntaxhighlight lang="xml" line="1" start="9547"> <Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>
<KEY__YDown>NSB</KEY__YDown>
<KEY__XDown>JF</KEY__XDown>
<KEY__ADown></KEY__ADown>
<KEY__Land></KEY__Land>
<KEY__AirCombo />
<KEY__End></KEY__End>
<Guard>true</Guard>
<Avoid>true</Avoid>
<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>9</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
<WaitEndMotionSpeed>1</WaitEndMotionSpeed>
<EndMotionSpeed>1</EndMotionSpeed>
<LandStartFrame>-1</LandStartFrame>
<ActionValidHeightMin>-1</ActionValidHeightMin>
</Action></syntaxhighlight>

== Names: ==
Making a custom action is pretty simple. Let’s try making an action called “MOVE_A”, based on the previous Motion “MOVE_A”. We’d start by making the main Action variable and writing down the Action/Motion Name. It’s important to know there’s a few combinations.

* Same Action, Same Motion: This is the default setting for most moves, with an exact Motion translating into an Action.<syntaxhighlight lang="xml" line="1"> <Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A</MotionName>
</Action></syntaxhighlight>

* Different Action, Same Motion: This is generally used in two situations… a) This divides one large move into a few separate pieces of a larger move. A good example is the Werewheel Rush (YYYY-XXXX), a.k.a. the cartwheel move. b) This makes a separate combo but with the same attributes as another. You’d see a couple of examples from ‘Foreign Input System’.<syntaxhighlight lang="xml" line="1"> <Action>
<ActionName>MOVE_A2</ActionName>
<MotionName>MOVE_A</MotionName>
</Action></syntaxhighlight>
* Same Action, Different Motion: This is self-explanatory, since a similar move within a combo, however, has different properties or even entirely different… EVERYTHING! But within the base game, Unleashed Knuckle Sandwich /Wild Combo is a strong example of the same actions but with different properties (which is found in the Unleashed Infinite)<syntaxhighlight lang="xml" line="1"> <Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A3</MotionName>
</Action></syntaxhighlight>
* This here is a very unique situation. We will refer to these as “Root Actions”, which are used for beginning attacks (Ground/Aerial) or Special Attacks within the game. You can add different Motions, but you cannot fully customize OR make a custom “Root Action” without code-modding.
Ground, Straight<syntaxhighlight lang="xml" start="9524"><Action>
<ActionName>Start_YButtonUP</ActionName>
<MotionName>NSA</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>

</Action></syntaxhighlight>Aerial, Hook<syntaxhighlight lang="xml" start="9524"><Action>
<ActionName>Start_Air_XButtonDown</ActionName>
<MotionName>JCA2</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>

</Action></syntaxhighlight>Special Attacks<syntaxhighlight lang="xml" line="1"><Action>
<ActionName>Start_Dash_Air_YButtonDown</ActionName>
<MotionName>DC</MotionName>
<ValidLevel_Min>12</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>

</Action></syntaxhighlight>

== Common Values: ==
Now it’s time to look at the next few Action variables:

* ValidLevel_Min determines at what level a combo is enabled/unlocked
* ValidLevel_Max determines what level a combo is disabled/locked
* We set the respective values at Level 1 (Beginner) and Level 99, unless you want 99 combos or something.
** The top images show the beginner’s Were-Hammer (YYYY), which its finisher had a knockback. At Level 15, this move will be deactivated because of one reason…
** … Level 16 is when Feral Were-Hammer unlocks (YYYY-Y)! The new finisher has knockback and the original now has normal damage! Plus, it allows for new combo avenues!

Let’s look at some other variables, then. These are fairly important.

* ValidCommon determines if a move works in Normal Mode
* ValidBerserker determines if a move works in Unleash Mode

A few combinations of the two allow for the creation of moves meant ONLY for Normal or Unleash Mode. The Unleash Infinites primarily use this, but you can also make regular infinite attacks.

* Guard and Avoid (meaning Dodge) are self-explanatory. Enable them for ground moves, and disable them for Aerial moves.
<syntaxhighlight lang="xml">
<Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>

<Guard>true</Guard>
<Avoid>true</Avoid>

</Action>
</syntaxhighlight>

== Creating Combo Routes: ==
Making a combo route is simple, as shown in the example below. Here are MoveA and MoveB, which we want to connect into a consecutive move. It’s as simple as putting the ID for “MOVE_B” into one of the following KEY variables.

* '''KEY__''Button''Down''' transitions to another move by pressing the Y, X, A, or B buttons.
* '''KEY__''Button''UP''' transitions to another move by releasing the Y, X, A, or B buttons, usually before the next input (a.k.a very quickly).
* '''KEY__''Button''Ing''' is an unused input system that is activated by holding inputs for a given length of time, and can overridden ButtonDown and ButtonUp inputs (with bugged limitations).
* '''KEY__Land''' activates a move when the player lands on/falls to the ground.
* '''KEY__AirCombo''' activates when the player is in the air and when the player makes contact with the enemy hitbox.
* '''KEY__End''' activates a move when inputs are no longer received, meaning that you stop pressing ANYTHING.

== Input Registration: ==
While this is all good, it doesn’t matter if the game can’t register our inputs. We should fix that so you can execute your combo effectively! Let’s focus on the following three variables, which allows you to register the input for the next move:

* KEY__StartFrame is the start value of the input range (inclusive). Any inputs pressed before this value will not result in the next input.
* KEY__EndFrame is the end value of the input range (inclusive). Any inputs pressed after this value will not result in the next input, unless WaitEndMotionEndFrame is set to a value higher than 0.
* WaitEndMotionEndFrame (WEMEF) extends the range time where you can input a combo. This is found in almost all combos besides finishers and certain attacks.

The three parameters below allow you to register the input while holding down on a button.

* KEY__IngStartFrame is the start value of holding the button input.
* KEY__IngEndFrame is the end value of holding the button input. This value is only unresponsive when its value is greater than the EndFrame and/or WEMEF value.
* KEY__IngFrameTIme is how long you hold the button for.

The following variables assist with attack speed and more:

* WaitEndMotionSpeed (WEMS) is the speed of WEMEF, which works inversely proportionately.
* EndMotionSpeed is just the general speed of the whole action.
* LandStartFrame is self-explanatory, so most moves have a ‘-1’ value… with exception.
* ActionValidHeightMin is the minimum height for a move to work. a) Ground moves have a value of -1, so they work on the ground and maybe in the air. b) Aerial Attacks have a value of 1 or 2, which varies between moves.

Aerial Attacks follow the same principle but with two new variables:

* AirCatchStartFrame is the frame where the player can use the Aerial Piledriver.
* AddVelocityY increases or decreases the player's upward velocity, depending on whether the value is positive or negative.

Special Moves and Attack Finishers have empty Start/End frames, and any variables below have a value of -1.

Creating & Customizing Attack Actions (Combo Routes)

2026-07-26T04:08:47Z

King Galactix:

The ActionList is a compilation of different ‘Actions’. Actions work together like a family tree, with individual attacks being stems and their connections being branches. All combos are just multiple branches of other moves, spawning a wide range of moveset paths. Here’s an example:

{{Notice|type=example|content=NSA > NSB > NSC > NSD > NSE (YYYYY) = Feral/Normal Were-Hammer

NSA > JF > JKC (Y-XX) = Double Kick Combo

NSA > NSB > SC > SC2 > SD (YY-XXX) = Donkey Kick Combo}}

We’ll go over making custom actions, combinations of the variables and parameters, several cases of Action’s variables, unique methods of move-set inputs, and combining them into one whole move.<syntaxhighlight lang="xml" line="1" start="9547"> <Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>
<KEY__YDown>NSB</KEY__YDown>
<KEY__XDown>JF</KEY__XDown>
<KEY__ADown></KEY__ADown>
<KEY__Land></KEY__Land>
<KEY__AirCombo />
<KEY__End></KEY__End>
<Guard>true</Guard>
<Avoid>true</Avoid>
<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>9</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
<WaitEndMotionSpeed>1</WaitEndMotionSpeed>
<EndMotionSpeed>1</EndMotionSpeed>
<LandStartFrame>-1</LandStartFrame>
<ActionValidHeightMin>-1</ActionValidHeightMin>
</Action></syntaxhighlight>

== Names: ==
Making a custom action is pretty simple. Let’s try making an action called “MOVE_A”, based on the previous Motion “MOVE_A”. We’d start by making the main Action variable and writing down the Action/Motion Name. It’s important to know there’s a few combinations.

* Same Action, Same Motion: This is the default setting for most moves, with an exact Motion translating into an Action.<syntaxhighlight lang="xml" line="1"><Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A</MotionName>
</Action></syntaxhighlight>

* Different Action, Same Motion: This is generally used in two situations… a) This divides one large move into a few separate pieces of a larger move. A good example is the Werewheel Rush (YYYY-XXXX), a.k.a. the cartwheel move. b) This makes a separate combo but with the same attributes as another. You’d see a couple of examples from ‘Foreign Input System’.<syntaxhighlight lang="xml" line="1"><Action>
<ActionName>MOVE_A2</ActionName>
<MotionName>MOVE_A</MotionName>
</Action></syntaxhighlight>
* Same Action, Different Motion: This is self-explanatory, since a similar move within a combo, however, has different properties or even entirely different… EVERYTHING! But within the base game, Unleashed Knuckle Sandwich /Wild Combo is a strong example of the same actions but with different properties (which is found in the Unleashed Infinite)<syntaxhighlight lang="xml" line="1"> <Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A3</MotionName>
</Action></syntaxhighlight>
* This here is a very unique situation. We will refer to these as “Root Actions”, which are used for beginning attacks (Ground/Aerial) or Special Attacks within the game. You can add different Motions, but you cannot fully customize OR make a custom “Root Action” without code-modding.
Ground, Straight<syntaxhighlight lang="xml" start="9524">
<Action>
<ActionName>Start_YButtonUP</ActionName>
<MotionName>NSA</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>

</Action>
</syntaxhighlight>Aerial, Hook<syntaxhighlight lang="xml" start="9524">
<Action>
<ActionName>Start_Air_XButtonDown</ActionName>
<MotionName>JCA2</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>

</Action>
</syntaxhighlight>Special Attacks<syntaxhighlight lang="xml" line="1"> <Action>
<ActionName>Start_Dash_Air_YButtonDown</ActionName>
<MotionName>DC</MotionName>
<ValidLevel_Min>12</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>

</Action></syntaxhighlight>

== Common Values: ==
Now it’s time to look at the next few Action variables:

* ValidLevel_Min determines at what level a combo is enabled/unlocked
* ValidLevel_Max determines what level a combo is disabled/locked
* We set the respective values at Level 1 (Beginner) and Level 99, unless you want 99 combos or something.

* The top images show the beginner’s Were-Hammer (YYYY), which its finisher had a knockback. At Level 15, this move will be deactivated because of one reason…
* … Level 16 is when Feral Were-Hammer unlocks (YYYY-Y)! The new finisher has knockback and the original now has normal damage! Plus, it allows for new combo avenues!

Let’s look at some other variables, then. These are fairly important.

* ValidCommon determines if a move works in Normal Mode
* ValidBerserker determines if a move works in Unleash Mode

A few combinations of the two allow for the creation of moves meant ONLY for Normal or Unleash Mode. The Unleash Infinites primarily use this, but you can also make regular infinite attacks.

* Guard and Avoid (meaning Dodge) are self-explanatory. Enable them for ground moves, and disable them for Aerial moves.
<syntaxhighlight lang="xml">
<Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>

<Guard>true</Guard>
<Avoid>true</Avoid>

</Action>
</syntaxhighlight>

== Creating Combo Routes: ==
Making a combo route is simple, as shown in the example below. Here are MoveA and MoveB, which we want to connect into a consecutive move. It’s as simple as putting the ID for “MOVE_B” into one of the following KEY variables.

* '''KEY__''Button''Down''' transitions to another move by pressing the Y, X, A, or B buttons.
* '''KEY__''Button''UP''' transitions to another move by releasing the Y, X, A, or B buttons, usually before the next input (a.k.a very quickly).
* '''KEY__''Button''Ing''' is an unused input system that is activated by holding inputs for a given length of time, and can overridden ButtonDown and ButtonUp inputs (with bugged limitations).
* '''KEY__Land''' activates a move when the player lands on/falls to the ground.
* '''KEY__AirCombo''' activates when the player is in the air and when the player makes contact with the enemy hitbox.
* '''KEY__End''' activates a move when inputs are no longer received, meaning that you stop pressing ANYTHING.

== Input Registration: ==
While this is all good, it doesn’t matter if the game can’t register our inputs. We should fix that so you can execute your combo effectively! Let’s focus on the following three variables, which allows you to register the input for the next move:

* KEY__StartFrame is the start value of the input range (inclusive). Any inputs pressed before this value will not result in the next input.
* KEY__EndFrame is the end value of the input range (inclusive). Any inputs pressed after this value will not result in the next input, unless WaitEndMotionEndFrame is set to a value higher than 0.
* WaitEndMotionEndFrame (WEMEF) extends the range time where you can input a combo. This is found in almost all combos besides finishers and certain attacks.

The three parameters below allow you to register the input while holding down on a button.

* KEY__IngStartFrame is the start value of holding the button input.
* KEY__IngEndFrame is the end value of holding the button input. This value is only unresponsive when its value is greater than the EndFrame and/or WEMEF value.
* KEY__IngFrameTIme is how long you hold the button for.

The following variables assist with attack speed and more:

* WaitEndMotionSpeed (WEMS) is the speed of WEMEF, which works inversely proportionately.
* EndMotionSpeed is just the general speed of the whole action.
* LandStartFrame is self-explanatory, so most moves have a ‘-1’ value… with exception.
* ActionValidHeightMin is the minimum height for a move to work. a) Ground moves have a value of -1, so they work on the ground and maybe in the air. b) Aerial Attacks have a value of 1 or 2, which varies between moves.

Aerial Attacks follow the same principle but with two new variables:

* AirCatchStartFrame is the frame where the player can use the Aerial Piledriver.
* AddVelocityY increases or decreases the player's upward velocity, depending on whether the value is positive or negative.

Special Moves and Attack Finishers have empty Start/End frames, and any variables below have a value of -1.

Creating & Customizing Attack Actions (Combo Routes)

2026-07-23T17:09:30Z

King Galactix:

Creating & Customizing Attack Actions (Combo Routes)

2026-07-23T01:05:37Z

King Galactix: Included the Aerial Hook Section

The ActionList is a compilation of different ‘Actions’. Actions work together like a family tree, with individual attacks being stems and their connections being branches. All combos are just multiple branches of other moves, spawning a wide range of moveset paths. Here’s an example:

{{Notice|type=example|content=NSA > NSB > NSC > NSD > NSE (YYYYY) = Feral/Normal Were-Hammer

NSA > JF > JKC (Y-XX) = Double Kick Combo

NSA > NSB > SC > SC2 > SD (YY-XXX) = Donkey Kick Combo}}

We’ll go over making custom actions, combinations of the variables and parameters, several cases of Action’s variables, unique methods of move-set inputs, and combining them into one whole move.<syntaxhighlight lang="xml" line="1" start="9547">
<Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>
<KEY__YDown>NSB</KEY__YDown>
<KEY__XDown>JF</KEY__XDown>
<KEY__ADown></KEY__ADown>
<KEY__Land></KEY__Land>
<KEY__AirCombo />
<KEY__End></KEY__End>
<Guard>true</Guard>
<Avoid>true</Avoid>
<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>9</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
<WaitEndMotionSpeed>1</WaitEndMotionSpeed>
<EndMotionSpeed>1</EndMotionSpeed>
<LandStartFrame>-1</LandStartFrame>
<ActionValidHeightMin>-1</ActionValidHeightMin>
</Action>
</syntaxhighlight>

== Names: ==
Making a custom action is pretty simple. Let’s try making an action called “MOVE_A”, based on the previous Motion “MOVE_A”. We’d start by making the main Action variable and writing down the Action/Motion Name. It’s important to know there’s a few combinations.

* Same Action, Same Motion: This is the default setting for most moves, with an exact Motion translating into an Action.<syntaxhighlight lang="xml" line="1">
<Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A</MotionName>
</Action>
</syntaxhighlight>

* Different Action, Same Motion: This is generally used in two situations… a) This divides one large move into a few separate pieces of a larger move. A good example is the Werewheel Rush (YYYY-XXXX), a.k.a. the cartwheel move. b) This makes a separate combo but with the same attributes as another. You’d see a couple of examples from ‘Foreign Input System’.<syntaxhighlight lang="xml" line="1">
<Action>
<ActionName>MOVE_A2</ActionName>
<MotionName>MOVE_A</MotionName>
</Action>
</syntaxhighlight>
* Same Action, Different Motion: This is self-explanatory, since a similar move within a combo, however, has different properties or even entirely different… EVERYTHING! But within the base game, Unleashed Knuckle Sandwich /Wild Combo is a strong example of the same actions but with different properties (which is found in the Unleashed Infinite)<syntaxhighlight lang="xml" line="1">
<Action>
<ActionName>MOVE_A</ActionName>
<MotionName>MOVE_A3</MotionName>
</Action>
</syntaxhighlight>
* This here is a very unique situation. We will refer to these as “Root Actions”, which are used for beginning attacks (Ground/Aerial) or Special Attacks within the game. You can add different Motions, but you cannot fully customize OR make a custom “Root Action” without code-modding.
Ground, Straight<syntaxhighlight lang="xml" line="1" start="9524">
<Action>
<ActionName>Start_YButtonUP</ActionName>
<MotionName>NSA</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>
<KEY__YDown>NSB</KEY__YDown>
<KEY__XDown>JF</KEY__XDown>
<KEY__ADown></KEY__ADown>
<KEY__Land></KEY__Land>
<KEY__AirCombo />
<KEY__End></KEY__End>
<Guard>true</Guard>
<Avoid>true</Avoid>
<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>10</KEY__EndFrame>
<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
<WaitEndMotionSpeed>1</WaitEndMotionSpeed>
<EndMotionSpeed>1</EndMotionSpeed>
<LandStartFrame>-1</LandStartFrame>
<ActionValidHeightMin>-1</ActionValidHeightMin>
</Action>
</syntaxhighlight>Aerial, Hook<syntaxhighlight lang="xml" line="1" start="9524">
<Action>
<ActionName>Start_Air_XButtonDown</ActionName>
<MotionName>JCA2</MotionName>
<ValidLevel_Min>1</ValidLevel_Min>
<ValidLevel_Max>99</ValidLevel_Max>
<ValidCommon>true</ValidCommon>
<ValidBerserker>true</ValidBerserker>
<KEY__YDown></KEY__YDown>
<KEY__XDown>JCB2</KEY__XDown>
<KEY__ADown></KEY__ADown>
<KEY__Land></KEY__Land>
<KEY__AirCombo />
<KEY__End></KEY__End>
<Guard>true</Guard>
<Avoid>false</Avoid>
<KEY__StartFrame>2</KEY__StartFrame>
<KEY__EndFrame>10</KEY__EndFrame>
<WaitEndMotionEndFrame>21</WaitEndMotionEndFrame>
<WaitEndMotionSpeed>0.833</WaitEndMotionSpeed>
<EndMotionSpeed>0.833</EndMotionSpeed>
<AddVelocityY>-0.25</AddVelocityY>
<LandStartFrame>-1</LandStartFrame>
<ActionValidHeightMin>1</ActionValidHeightMin>
</Action>
</syntaxhighlight>Special Attacks

== Common Values: ==
Now it’s time to look at the next few Action variables:

* ValidLevel_Min determines at what level a combo is enabled/unlocked
* ValidLevel_Max determines what level a combo is disabled/locked
* We set the respective values at Level 1 (Beginner) and Level 99, unless you want 99 combos or something.

* The top images show the beginner’s Were-Hammer (YYYY), which its finisher had a knockback. At Level 15, this move will be deactivated because of one reason…
* … Level 16 is when Feral Were-Hammer unlocks (YYYY-Y)! The new finisher has knockback and the original now has normal damage! Plus, it allows for new combo avenues!

Let’s look at some other variables, then. These are fairly important.

* ValidCommon determines if a move works in Normal Mode
* ValidBerserker determines if a move works in Unleash Mode

A few combinations of the two allow for the creation of moves meant ONLY for Normal or Unleash Mode. The Unleash Infinites primarily use this, but you can also make regular infinite attacks.

* Guard and Avoid (meaning Dodge) are self-explanatory. Enable them for ground moves, and disable them for Aerial moves.

== Creating Combo Routes: ==
Making a combo route is simple, as shown in the example below. Here are MoveA and MoveB, which we want to connect into a consecutive move. It’s as simple as putting the ID for “MOVE_B” into one of the following KEY variables.

* '''KEY__''Button''Down''' transitions to another move by pressing the Y, X, A, or B buttons.
* '''KEY__''Button''UP''' transitions to another move by releasing the Y, X, A, or B buttons, usually before the next input (a.k.a very quickly).
* '''KEY__''Button''Ing''' is an unused input system that is activated by holding inputs for a given length of time, and can overridden ButtonDown and ButtonUp inputs (with bugged limitations).
* '''KEY__Land''' activates a move when the player lands on/falls to the ground.
* '''KEY__AirCombo''' activates when the player is in the air and when the player makes contact with the enemy hitbox.
* '''KEY__End''' activates a move when inputs are no longer received, meaning that you stop pressing ANYTHING.

== Input Registration: ==
While this is all good, it doesn’t matter if the game can’t register our inputs. We should fix that so you can execute your combo effectively! Let’s focus on the following three variables, which allows you to register the input for the next move:

* KEY__StartFrame is the start value of the input range (inclusive). Any inputs pressed before this value will not result in the next input.
* KEY__EndFrame is the end value of the input range (inclusive). Any inputs pressed after this value will not result in the next input, unless WaitEndMotionEndFrame is set to a value higher than 0.
* WaitEndMotionEndFrame (WEMEF) extends the range time where you can input a combo. This is found in almost all combos besides finishers and certain attacks.

The three parameters below allow you to register the input while holding down on a button.

* KEY__IngStartFrame is the start value of holding the button input.
* KEY__IngEndFrame is the end value of holding the button input. This value is only unresponsive when its value is greater than the EndFrame and/or WEMEF value.
* KEY__IngFrameTIme is how long you hold the button for.

The following variables assist with attack speed and more:

* WaitEndMotionSpeed (WEMS) is the speed of WEMEF, which works inversely proportionately.
* EndMotionSpeed is just the general speed of the whole action.
* LandStartFrame is self-explanatory, so most moves have a ‘-1’ value… with exception.
* ActionValidHeightMin is the minimum height for a move to work. a) Ground moves have a value of -1, so they work on the ground and maybe in the air. b) Aerial Attacks have a value of 1 or 2, which varies between moves.

Aerial Attacks follow the same principle but with two new variables:

* AirCatchStartFrame is the frame where the player can use the Aerial Piledriver.
* AddVelocityY increases or decreases the player's upward velocity, depending on whether the value is positive or negative.

Special Moves and Attack Finishers have empty Start/End frames, and any variables below have a value of -1.

Creating & Customizing Attack Actions (Combo Routes)

2026-04-27T21:56:24Z

King Galactix:

Creating & Customizing Attack Motions (Unique Inputs)

2026-04-27T21:50:28Z

King Galactix:

The '''MotionList''' contains a series of '''Motions''', or the '''Unique Inputs (UIs)''' in the Werehog’s combos. These Motion are XML cells which determine the value of the animation, movement, collision, attack types, and other attributes of each and every unique input of the Werehog's attacks. These elements are extensively long for the purpose of explaining how each variable works and what use cases exist for them, however, it will allow for a greater understanding and application of the mechanics. For convenience's sake, we will create a new scenario by making a new Motion (individual attack) called “MOVE_A” and explain what each variable does.{{Notice|type=note|content=You will need the following files from the #Application archive file:
* EvilAttackAction1.xml
* EvilAttackMotionFile.xml}}

By the end of this guide, you'll have a fairly comprehensive and complete Motion file, such as the example below.<syntaxhighlight lang="xml" line="1" start="125"><Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>
<MotionMoveSpeedRatio>0.875f</MotionMoveSpeedRatio>
<MotionMoveSpeedRatio_Y>1.f</MotionMoveSpeedRatio_Y>
<MotionMoveSpeedRatioFrameStart_1>-1</MotionMoveSpeedRatioFrameStart_1>
<MotionMoveSpeedRatioFrame_1>10.f</MotionMoveSpeedRatioFrame_1>
<MotionMoveSpeedRatioFrameY_1>10.f</MotionMoveSpeedRatioFrameY_1>
<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
<DontCatchTime>0</DontCatchTime>
<DontJump>false</DontJump>
<ShakeCameraStartFrame>-1</ShakeCameraStartFrame>
<GroundHeightRepair>0.1f</GroundHeightRepair>
<MoveType>IngAutoTarget</MoveType>
<AutoTargetEndFrame>9</AutoTargetEndFrame>
<AutoTargetPower>0.2</AutoTargetPower>
<PadRotationIntensity>20</PadRotationIntensity>
<IsGravity>true</IsGravity>
<GravityArray_Start1>-1</GravityArray_Start1>
<IsGravityArray1>true</IsGravityArray1>
<PadRotationIntensity_Start1>0</PadRotationIntensity_Start1>
<PadRotationIntensity_Power1>20</PadRotationIntensity_Power1>
<PadRotationValid1>true</PadRotationValid1>
<PadRotationIntensity_Start2>8</PadRotationIntensity_Start2>
<PadRotationIntensity_Power2>0</PadRotationIntensity_Power2>
<PadRotationValid2>false</PadRotationValid2>
<PadRotationIntensity_Start3>22</PadRotationIntensity_Start3>
<PadRotationIntensity_Power3>20</PadRotationIntensity_Power3>
<PadRotationValid3>true</PadRotationValid3>
<GameSpeed_Start1>0</GameSpeed_Start1>
<GameSpeed_Power1>1</GameSpeed_Power1>
<GameSpeed_CollPower1>1</GameSpeed_CollPower1>
<GuardStartFrame>8</GuardStartFrame>
<GuardEndFrame>27</GuardEndFrame>

<Effect>
<REffect_Start1>4</REffect_Start1>
<REffect_End1>16</REffect_End1>
<REffect_Size1>2</REffect_Size1>
<REffect_Name1>evil_punch_01</REffect_Name1>
</Effect>
<Sound></Sound>
<Collision>
<DebugDraw>true</DebugDraw>
<Size1>0.75f</Size1>
<SizeDelta1>0.f</SizeDelta1>
<RHandStart1>6</RHandStart1>
<RHandEnd1>16</RHandEnd1>
</Collision>
<Vibration>
<StartFrame>-1</StartFrame>
<EndFrame>-1</EndFrame>
<BigMoter>0.f</BigMoter>
<SmallMoter>0.f</SmallMoter>
<SuccessTimeLength>0.01</SuccessTimeLength>
<SuccessBigMoter>0.5f</SuccessBigMoter>
<SuccessSmallMoter>0.5f</SuccessSmallMoter>
</Vibration>
<Attack>
<Type1>NormalHard</Type1>
<DamagePower1>95</DamagePower1>
<KnockOutPower_Y1>0.f</KnockOutPower_Y1>
<KnockOutPower_Dir1>2.2f</KnockOutPower_Dir1>
<KnockOutAnglePowerRatio1>0.5f</KnockOutAnglePowerRatio1>
<Attribute1>VerticalAttack</Attribute1>
</Attack>
</Motion></syntaxhighlight>
== Names ==
We start with the '''MotionName''' and '''FileName'''. The MotionName can be whatever it wants, but the FileName must be exactly as it’s written within EvilAttackMotionFile.xml<syntaxhighlight lang="xml">
<Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
</Motion>
</syntaxhighlight>For the most part, changing the filename is an entirely arbitrary case. But if you’re planning to change the filename anyways:

# Find the name of your animation file (formatted as *.anm.hkx)
# Look for EvilAttackMotionFile.xml, and look within that XML
# You can either change the filename or make a new MotionFileList. However, there are some limitations… so this is an arbitrary action unless you’re using the Beta Combos.
<syntaxhighlight lang="xml" line="1" start="1">
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<Start>
<StartPoint>

<MotionFileList>
<MotionName>NSA</MotionName>
<FileName>evilsonic_attackNSA</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSB</MotionName>
<FileName>evilsonic_attackNSB</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSC</MotionName>
<FileName>evilsonic_attackNSC</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSD</MotionName>
<FileName>evilsonic_attackNSD</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSE</MotionName>
<FileName>evilsonic_attackNSE</FileName>
</MotionFileList>


<MotionFileList>
<MotionName>MOVE_A</MotionName>
<FileName>evilsonic_attackNSE</FileName>
</MotionFileList>
</Start>
</StartPoint>
</syntaxhighlight>

== Animation ==
The animation and movement values here determine how your Motion looks and moves visually and physically.

* '''MotionBlendTimeS''', '''MotionBlendTimeE''', and '''MotionBlendTimeEIdle''' blend the animations between a previous and following combo. Keep the values as 0.02f.

* '''MotionFirstSpeed''', '''MiddleSpeed''', and '''EndSpeed''' all affect the Attack’s animation speed.
* '''MotionSpeed_First'''/'''MiddleFrame''' represents when the MotionFirstSpeed and MiddleSpeed params are executed (corresponding with the animation frames).
<syntaxhighlight lang="xml" line="1">
<Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>

<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
</Motion>
</syntaxhighlight>

== Movement ==
Now we can take a look at more general variables. These are equally important for combat and visual aspects of the Werehog.

* '''MotionMoveSpeedRatio''' (MMSR for convenience) and '''MotionMoveSpeedRatio_Y''' control the player’s movement ratio when making the entire attack. You can experiment with these values, but remember to write it in the form of “A.Bf”
* '''MotionMoveSpeedRatioFrameStart_N,''' '''MotionMoveSpeedRatioFrame_N,''' and '''MotionMoveSpeedRatioFrameY_N''' apply the same movement/distance ratio, except it’s done within a certain frame. Reference other moves if you want to make an attack move more or less in a certain direction.
** For example: moves that rise up at a certain frame, such as a launcher, should multiply MotionMoveSpeedRatioFrameY_N by a significant amount, more than MotionMoveSpeedRatioFrame_N.
*'''EndSkipTimeWhenPad''' determines when the move can skip itself after being moved by the PadRotation variables (refer to PadRotation section).
*'''AttackScope''' sets the maximum scope of turning while attacking. You have None, Scope90, and Scope360 to use, which only work with enabled PadRotation variables (more in the Gravity/PadRotation section).
*'''DontCatchTime''' states how long it takes before the player can use the grab. Set it to 0 for ground moves, 2 for aerial moves.
* '''DontJump''' is self-explanatory. You apply it for whatever moves you DON'T want to have an enabled jump afterwards, such as Sho-Hog-Ken (YYA), and disable it for combo that you want to jump with, such as Unleashed Wild Combo (XX-YY-XX-YY).
* '''OnceSendDamage''' determines how long a combo can continually send damage. The default value is usually zero, and many moves use this as a way of implementing multiple hits for combos with a single or more number of hitboxes.
* '''ShakeCameraStartFrame''' is the start frame for when the Camera Shake can happen for certain moves. Unfortunately, there are no specific variables to affect the number or intensity of shakes.
* '''GroundHeightRepair''' determines the floatiness of a move. Lower values mean more floaty and higher values mean less floaty.
* '''MoveType''' has two values: Default and IngAutoTarget (the variables below only work when IngAutoTarget is enabled.
* '''AutoTargetEndFrame''' can be set to 0 for Default, and any value for IngAutoTarget
* '''AutoTargetPower''' can be set to 0 for Default, and any value for IngAutoTarget
<syntaxhighlight lang="xml"> <Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>
<MotionMoveSpeedRatio>0.875f</MotionMoveSpeedRatio> 
<MotionMoveSpeedRatio_Y>1.f</MotionMoveSpeedRatio_Y>
<MotionMoveSpeedRatioFrameStart_1>-1</MotionMoveSpeedRatioFrameStart_1>
<MotionMoveSpeedRatioFrame_1>10.f</MotionMoveSpeedRatioFrame_1>
<MotionMoveSpeedRatioFrameY_1>10.f</MotionMoveSpeedRatioFrameY_1>
<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<EndSkipTimeWhenPad>0.f</EndSkipTimeWhenPad>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
<DontCatchTime>0</DontCatchTime>
<DontJump>false</DontJump>
<OnceSendDamage>0</OnceSendDamage> 
<ShakeCameraStartFrame>-1</ShakeCameraStartFrame>
<GroundHeightRepair>0.1f</GroundHeightRepair>
<MoveType>IngAutoTarget</MoveType>
<AutoTargetEndFrame>9</AutoTargetEndFrame>
<AutoTargetPower>0.2</AutoTargetPower>
</Motion></syntaxhighlight>

== Gravity and PadRotation ==
The following Gravity and PadRotation variables are interpreted and explained by Nec0Arc and myself, so you can understand how to adjust the player’s movement across the X, Y, and Z axis. The value of these variables depend on what kind of attack you would want (grounded, launcher, aerial, unidirectional, multidirectional, etc.)

* '''PadRotationIntensity''' is a general value that of the attack's rotation via the left stick. It is assumed the value is represented in degrees or whatever value is used by the controller's left-stick.
* '''IsGravity''' and its subsequent parameters, '''GravityArray_StartX''' and '''IsGravityArrayX''' determines the combos's application of gravity while doing a combo. IsGravity and IsGravityX use true/false.
** Ground moves follow the setup below for its gravity arrays and values.
** Launcher moves follow the setup below for its gravity arrays and values.
** Aerial moves follow the setup below for its gravity arrays and values:
* '''PadRotationIntensity_StartX''' sets the frame that this instance of PadRotationcan start executing.
* '''PadRotationIntensity_PowerX''' sets the degrees of PadRotation that your player can move when executing the combo.
* '''PadRotationValidX''' enables or disables the PadRotation with true or false.
<syntaxhighlight lang="xml"> <Motion>

<PadRotationIntensity>20</PadRotationIntensity>
<IsGravity>true</IsGravity>
<GravityArray_Start1>-1</GravityArray_Start1>
<IsGravityArray1>true</IsGravityArray1>
<PadRotationIntensity_Start1>0</PadRotationIntensity_Start1>
<PadRotationIntensity_Power1>20</PadRotationIntensity_Power1>
<PadRotationValid1>true</PadRotationValid1>
<PadRotationIntensity_Start2>8</PadRotationIntensity_Start2>
<PadRotationIntensity_Power2>0</PadRotationIntensity_Power2>
<PadRotationValid2>false</PadRotationValid2>
<PadRotationIntensity_Start3>22</PadRotationIntensity_Start3>
<PadRotationIntensity_Power3>20</PadRotationIntensity_Power3>
<PadRotationValid3>true</PadRotationValid3>
</Motion></syntaxhighlight>

== GameSpeed and Guarding ==
The following discoveries were made by BaconYum and myself: GameSpeed represents the “Slow Motion” moments that happen with attacks, so let’s look at the variables:

* GameSpeed_StartX refers to the specific frame that starts the GameSpeed variable.
* GameSpeed_PowerX refers to the power of this GameSpeed modifier, which is simple to understand.
** A value of 1 means the game’s speed is normal
** 1 > X > 0 means the game’s speed is slowed down by that amount. So if you have a value of 0.5, the game’s speed is halved.
** A value above 1 means the game’s speed is sped up by that amount. A value of 2 means the game’s speed is doubled.
* GameSpeed_CollPowerX does the same thing, except it refers to the player’s collision when doing the attack.
* GuardStart/EndFrame are self-explanatory, and they surprisingly explain the mechanic of Shield Cancelling… neat!
* There are unused parameter values, called GameSpeedColl. At this time, they have not been tested to see their functionality.
<syntaxhighlight lang="xml"> <Motion>

<GameSpeed_Start1>0</GameSpeed_Start1>
<GameSpeed_Power1>1</GameSpeed_Power1>
<GameSpeed_CollPower1>1</GameSpeed_CollPower1>
<GuardStartFrame>8</GuardStartFrame>
<GuardEndFrame>27</GuardEndFrame>

</Motion></syntaxhighlight>

== Sound and Effects ==
The Sound element is unused in the main game’s Attack XML, mostly used in the TBRES XMLs. The Effect element, however, can be used generally for hand and feet attacks.

* Effect_StartX is the start time value for the effect to take place. L/R is for hands, LF/RF is for feet.
* Effect_EndX is the end time value for the effect to take place.
* Effect_SizeX is self explanatory
* Effect_NameX is also self-explanatory. If you want to look for the effect names for the Werehog, look at EvilSonic’s ar files.
<syntaxhighlight lang="xml">
<Motion>

<Effect>
<REffect_Start1>4</REffect_Start1>
<REffect_End1>16</REffect_End1>
<REffect_Size1>2</REffect_Size1>
<REffect_Name1>evil_punch_01</REffect_Name1>
</Effect>
<Sound></Sound>
</Motion>
</syntaxhighlight>

== Collision ==
The Collision Element deals with the attack’s hitbox, which registers the hits and damage. Both Nec0Arc and NextinFRFX interpreted and discovered the following variables to help you understand what they do:

* The DebugDraw here is potentially an unused debug feature to view the player's attack hitbox collision.
* SizeX is the initial or start size of the attack’s hitbox.
* SizeDeltaX is the final or end size of the attack’s hitbox
* RHandStartX is the frame where the collision hitbox starts, applying the SizeX variable. The specific body hitbox can be changed to any of the following ('''refer to this link''').
* RHandEndX is the frame where the collision hitbox ends, applying the SizeDeltaX variable.
* You can also apply more than one collision hitbox per Size instance. An example would be the followaing:
** Size1/SizeDelta1 uses RHand collision hitbox.
** Size2/SizeDelta2 uses RHand and LHand, or RLeg and Hips
<syntaxhighlight lang="xml">
<Motion>

<Collision>
<DebugDraw>true</DebugDraw>
<Size1>0.75f</Size1>
<SizeDelta1>0.f</SizeDelta1>
<RHandStart1>6</RHandStart1>
<RHandEnd1>16</RHandEnd1>
</Collision>
</Motion>
</syntaxhighlight>

== Camera ==
This element deals with the player’s camera when doing certain attacks. These values were taken from Sho-Hog-Ken (SHAS).

* StartEaseInFrame/StartEaseOutFrame are used to set the range of when the camera eases in and out.
* EaseIn/EaseOut is the value that the camera pulls in or pulls out.
* Fovy probably means FOV (field of view). The Y could be a type or mean the Y-Axis.
* HopeLength… your guess is as good as mine.
* Height is self-explanatory.
<syntaxhighlight lang="xml">
<Motion>

<Camera>
<StartEaseInFrame>15</StartEaseInFrame>
<StartEaseOutFrame>35</StartEaseOutFrame>
<EaseIn>0.5</EaseIn>
<EaseOut>0.75</EaseOut>
<Fovy>10</Fovy>
<HopeLength>1</HopeLength>
<Height>-1.5</Height>
</Camera>
</Motion>
</syntaxhighlight>

== Vibration ==
This element deals with the controller’s vibration, usually when a hit is registered.

* Start/EndFrame are self-explanatory
* BigMoter and SmallMoter are the vibration motors of the control, meaning left or right.
* SuccessTimeLength is how long the vibration lasts if you land a hit
* SuccessBig/SmallMoter is the same thing but for the motors specifically.
<syntaxhighlight lang="xml">
<Motion>

<Vibration>
<StartFrame>-1</StartFrame>
<EndFrame>-1</EndFrame>
<BigMoter>0.f</BigMoter>
<SmallMoter>0.f</SmallMoter>
<SuccessTimeLength>0.01</SuccessTimeLength>
<SuccessBigMoter>0.5f</SuccessBigMoter>
<SuccessSmallMoter>0.5f</SuccessSmallMoter>
</Vibration>
</Motion>
</syntaxhighlight>

== Attack ==
These are the primary Attack values, which we know are connected to the Collision (thanks to Nec0Arc). Let’s take a look at the Attack Variables, which are the final variables you’ll need to complete your Motion:

* Type is one of many different Attack Types that you can use. Refer to the Attack Types documentation
* DamagePower is self-explanatory, and its value is multiplied by the Strength Stat
* KnockOutPower_Y determines the vertical knockback distance for enemies. It seems to be broken in retail.
* KnockOutPower_Dir determines the horizontal knockback distance for enemies. It seems to be broken in retail.
* KnockOutAnglePowerRatio is just a multiplier for both KnockOutPower variables.
* The Attribute variable can be set to Vertical, Side, or FinishAttack.
<syntaxhighlight lang="xml">
<Motion>

<Attack>
<Type1>NormalHard</Type1>
<DamagePower1>100</DamagePower1>
<KnockOutPower_Y1>0.f</KnockOutPower_Y1>
<KnockOutPower_Dir1>2.2f</KnockOutPower_Dir1>
<KnockOutAnglePowerRatio1>0.5f</KnockOutAnglePowerRatio1>
<Attribute1>VerticalAttack</Attribute1>
</Attack>
</Motion>
</syntaxhighlight>

Creating & Customizing Attack Motions (Unique Inputs)

2026-04-20T01:37:42Z

King Galactix:

The '''MotionList''' contains a series of '''Motions''', or the '''Unique Inputs (UIs)''' in the Werehog’s combos. These Motion are XML cells which determine the value of the animation, movement, collision, attack types, and other attributes of each and every unique input of the Werehog's attacks. These elements are extensively long for the purpose of explaining how each variable works and what use cases exist for them, however, it will allow for a greater understanding and application of the mechanics. For convenience's sake, we will create a new scenario by making a new Motion (individual attack) called “MOVE_A” and explain what each variable does.{{Notice|type=note|content=You will need the following files from the #Application archive file:
* EvilAttackAction1.xml
* EvilAttackMotionFile.xml}}

By the end of this guide, you'll have a fairly comprehensive and complete Motion file, such as the example below.<syntaxhighlight lang="xml" line="1" start="125"><Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>
<MotionMoveSpeedRatio>0.875f</MotionMoveSpeedRatio>
<MotionMoveSpeedRatio_Y>1.f</MotionMoveSpeedRatio_Y>
<MotionMoveSpeedRatioFrameStart_1>-1</MotionMoveSpeedRatioFrameStart_1>
<MotionMoveSpeedRatioFrame_1>10.f</MotionMoveSpeedRatioFrame_1>
<MotionMoveSpeedRatioFrameY_1>10.f</MotionMoveSpeedRatioFrameY_1>
<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
<DontCatchTime>0</DontCatchTime>
<DontJump>false</DontJump>
<ShakeCameraStartFrame>-1</ShakeCameraStartFrame>
<GroundHeightRepair>0.1f</GroundHeightRepair>
<MoveType>IngAutoTarget</MoveType>
<AutoTargetEndFrame>9</AutoTargetEndFrame>
<AutoTargetPower>0.2</AutoTargetPower>
<PadRotationIntensity>20</PadRotationIntensity>
<IsGravity>true</IsGravity>
<GravityArray_Start1>-1</GravityArray_Start1>
<IsGravityArray1>true</IsGravityArray1>
<PadRotationIntensity_Start1>0</PadRotationIntensity_Start1>
<PadRotationIntensity_Power1>20</PadRotationIntensity_Power1>
<PadRotationValid1>true</PadRotationValid1>
<PadRotationIntensity_Start2>8</PadRotationIntensity_Start2>
<PadRotationIntensity_Power2>0</PadRotationIntensity_Power2>
<PadRotationValid2>false</PadRotationValid2>
<PadRotationIntensity_Start3>22</PadRotationIntensity_Start3>
<PadRotationIntensity_Power3>20</PadRotationIntensity_Power3>
<PadRotationValid3>true</PadRotationValid3>
<GameSpeed_Start1>0</GameSpeed_Start1>
<GameSpeed_Power1>1</GameSpeed_Power1>
<GameSpeed_CollPower1>1</GameSpeed_CollPower1>
<GuardStartFrame>8</GuardStartFrame>
<GuardEndFrame>27</GuardEndFrame>

<Effect>
<REffect_Start1>4</REffect_Start1>
<REffect_End1>16</REffect_End1>
<REffect_Size1>2</REffect_Size1>
<REffect_Name1>evil_punch_01</REffect_Name1>
</Effect>
<Sound></Sound>
<Collision>
<DebugDraw>true</DebugDraw>
<Size1>0.75f</Size1>
<SizeDelta1>0.f</SizeDelta1>
<RHandStart1>6</RHandStart1>
<RHandEnd1>16</RHandEnd1>
</Collision>
<Vibration>
<StartFrame>-1</StartFrame>
<EndFrame>-1</EndFrame>
<BigMoter>0.f</BigMoter>
<SmallMoter>0.f</SmallMoter>
<SuccessTimeLength>0.01</SuccessTimeLength>
<SuccessBigMoter>0.5f</SuccessBigMoter>
<SuccessSmallMoter>0.5f</SuccessSmallMoter>
</Vibration>
<Attack>
<Type1>NormalHard</Type1>
<DamagePower1>95</DamagePower1>
<KnockOutPower_Y1>0.f</KnockOutPower_Y1>
<KnockOutPower_Dir1>2.2f</KnockOutPower_Dir1>
<KnockOutAnglePowerRatio1>0.5f</KnockOutAnglePowerRatio1>
<Attribute1>VerticalAttack</Attribute1>
</Attack>
</Motion></syntaxhighlight>
== Names ==
We start with the '''MotionName''' and '''FileName'''. The MotionName can be whatever it wants, but the FileName must be exactly as it’s written within EvilAttackMotionFile.xml<syntaxhighlight lang="xml">
<Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
</Motion>
</syntaxhighlight>For the most part, changing the filename is an entirely arbitrary case. But if you’re planning to change the filename anyways:

# Find the name of your animation file (formatted as *.anm.hkx)
# Look for EvilAttackMotionFile.xml, and look within that XML
# You can either change the filename or make a new MotionFileList. However, there are some limitations… so this is an arbitrary action unless you’re using the Beta Combos.
<syntaxhighlight lang="xml" line="1" start="1">
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<Start>
<StartPoint>

<MotionFileList>
<MotionName>NSA</MotionName>
<FileName>evilsonic_attackNSA</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSB</MotionName>
<FileName>evilsonic_attackNSB</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSC</MotionName>
<FileName>evilsonic_attackNSC</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSD</MotionName>
<FileName>evilsonic_attackNSD</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSE</MotionName>
<FileName>evilsonic_attackNSE</FileName>
</MotionFileList>


<MotionFileList>
<MotionName>MOVE_A</MotionName>
<FileName>evilsonic_attackNSE</FileName>
</MotionFileList>
</Start>
</StartPoint>
</syntaxhighlight>

== Animation ==
The animation and movement values here determine how your Motion looks and moves visually and physically.

* '''MotionBlendTimeS''', '''MotionBlendTimeE''', and '''MotionBlendTimeEIdle''' blend the animations between a previous and following combo. Keep the values as 0.02f.

* '''MotionFirstSpeed''', '''MiddleSpeed''', and '''EndSpeed''' all affect the Attack’s animation speed.
* '''MotionSpeed_First'''/'''MiddleFrame''' represents when the MotionFirstSpeed and MiddleSpeed params are executed (corresponding with the animation frames).
<syntaxhighlight lang="xml" line="1">
<Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>

<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
</Motion>
</syntaxhighlight>

== Movement ==
Now we can take a look at more general variables. These are equally important for combat and visual aspects of the Werehog.

* '''MotionMoveSpeedRatio''' (MMSR for convenience) and '''MotionMoveSpeedRatio_Y''' control the player’s movement ratio when making the entire attack. You can experiment with these values, but remember to write it in the form of “A.Bf”
* '''MotionMoveSpeedRatioFrameStart_N,''' '''MotionMoveSpeedRatioFrame_N,''' and '''MotionMoveSpeedRatioFrameY_N''' apply the same movement/distance ratio, except it’s done within a certain frame. Reference other moves if you want to make an attack move more or less in a certain direction.
** For example: moves that rise up at a certain frame, such as a launcher, should multiply MotionMoveSpeedRatioFrameY_N by a significant amount, more than MotionMoveSpeedRatioFrame_N.
*'''EndSkipTimeWhenPad''' determines when the move can skip itself after being moved by the PadRotation variables (refer to PadRotation section).
*'''AttackScope''' sets the maximum scope of turning while attacking. You have None, Scope90, and Scope360 to use, which only work with enabled PadRotation variables (more in the Gravity/PadRotation section).
*'''DontCatchTime''' states how long it takes before the player can use the grab. Set it to 0 for ground moves, 2 for aerial moves.
* '''DontJump''' is self-explanatory. You apply it for whatever moves you DON'T want to have an enabled jump afterwards, such as Sho-Hog-Ken (YYA), and disable it for combo that you want to jump with, such as Unleashed Wild Combo (XX-YY-XX-YY).
* '''OnceSendDamage''' determines how long a combo can continually send damage. The default value is usually zero, and many moves use this as a way of implementing multiple hits for combos with a single or more number of hitboxes.
* '''ShakeCameraStartFrame''' is the start frame for when the Camera Shake can happen for certain moves. Unfortunately, there are no specific variables to affect the number or intensity of shakes.
* '''GroundHeightRepair''' determines the floatiness of a move. Lower values mean more floaty and higher values mean less floaty.
* '''MoveType''' has two values: Default and IngAutoTarget (the variables below only work when IngAutoTarget is enabled.
* '''AutoTargetEndFrame''' can be set to 0 for Default, and any value for IngAutoTarget
* '''AutoTargetPower''' can be set to 0 for Default, and any value for IngAutoTarget
<syntaxhighlight lang="xml"> <Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>
<MotionMoveSpeedRatio>0.875f</MotionMoveSpeedRatio> 
<MotionMoveSpeedRatio_Y>1.f</MotionMoveSpeedRatio_Y>
<MotionMoveSpeedRatioFrameStart_1>-1</MotionMoveSpeedRatioFrameStart_1>
<MotionMoveSpeedRatioFrame_1>10.f</MotionMoveSpeedRatioFrame_1>
<MotionMoveSpeedRatioFrameY_1>10.f</MotionMoveSpeedRatioFrameY_1>
<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<EndSkipTimeWhenPad>0.f</EndSkipTimeWhenPad>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
<DontCatchTime>0</DontCatchTime>
<DontJump>false</DontJump>
<OnceSendDamage>0</OnceSendDamage> 
<ShakeCameraStartFrame>-1</ShakeCameraStartFrame>
<GroundHeightRepair>0.1f</GroundHeightRepair>
<MoveType>IngAutoTarget</MoveType>
<AutoTargetEndFrame>9</AutoTargetEndFrame>
<AutoTargetPower>0.2</AutoTargetPower>
</Motion></syntaxhighlight>

== Gravity and PadRotation ==
The following Gravity and PadRotation variables are interpreted and explained by Nec0Arc and myself, so you can understand how to adjust the player’s movement across the X, Y, and Z axis. The value of these variables depend on what kind of attack you would want (grounded, launcher, aerial, unidirectional, multidirectional, etc.)

* '''PadRotationIntensity''' is a general value that of the attack's rotation via the left stick. It is assumed the value is represented in degrees or whatever value is used by the controller's left-stick.
* '''IsGravity''' and its subsequent parameters, '''GravityArray_StartX''' and '''IsGravityArrayX''' determines the combos's application of gravity while doing a combo. IsGravity and IsGravityX use true/false.
** Ground moves follow the setup below for its gravity arrays and values.
** Launcher moves follow the setup below for its gravity arrays and values.
** Aerial moves follow the setup below for its gravity arrays and values:
* '''PadRotationIntensity_StartX''' sets the frame that this instance of PadRotationcan start executing.
* '''PadRotationIntensity_PowerX''' sets the degrees of PadRotation that your player can move when executing the combo.
* '''PadRotationValidX''' enables or disables the PadRotation with true or false.
<syntaxhighlight lang="xml"> <Motion>

<PadRotationIntensity>20</PadRotationIntensity>
<IsGravity>true</IsGravity>
<GravityArray_Start1>-1</GravityArray_Start1>
<IsGravityArray1>true</IsGravityArray1>
<PadRotationIntensity_Start1>0</PadRotationIntensity_Start1>
<PadRotationIntensity_Power1>20</PadRotationIntensity_Power1>
<PadRotationValid1>true</PadRotationValid1>
<PadRotationIntensity_Start2>8</PadRotationIntensity_Start2>
<PadRotationIntensity_Power2>0</PadRotationIntensity_Power2>
<PadRotationValid2>false</PadRotationValid2>
<PadRotationIntensity_Start3>22</PadRotationIntensity_Start3>
<PadRotationIntensity_Power3>20</PadRotationIntensity_Power3>
<PadRotationValid3>true</PadRotationValid3>
</Motion></syntaxhighlight>

== GameSpeed and Guarding ==
The following discoveries were made by BaconYum and myself: GameSpeed represents the “Slow Motion” moments that happen with attacks, so let’s look at the variables:

* GameSpeed_StartX refers to the specific frame that starts the GameSpeed variable.
* GameSpeed_PowerX refers to the power of this GameSpeed modifier, which is simple to understand.
** A value of 1 means the game’s speed is normal
** 1 > X > 0 means the game’s speed is slowed down by that amount. So if you have a value of 0.5, the game’s speed is halved.
** A value above 1 means the game’s speed is sped up by that amount. A value of 2 means the game’s speed is doubled.
* GameSpeed_CollPowerX does the same thing, except it refers to the player’s collision when doing the attack.
* GuardStart/EndFrame are self-explanatory, and they surprisingly explain the mechanic of Shield Cancelling… neat!
* There are unused parameter values, called GameSpeedColl. At this time, they have not been tested to see their functionality.
<syntaxhighlight lang="xml"> <Motion>

<GameSpeed_Start1>0</GameSpeed_Start1>
<GameSpeed_Power1>1</GameSpeed_Power1>
<GameSpeed_CollPower1>1</GameSpeed_CollPower1>
<GuardStartFrame>8</GuardStartFrame>
<GuardEndFrame>27</GuardEndFrame>

</Motion></syntaxhighlight>

== Sound and Effects ==
The Sound element is unused in the main game’s Attack XML, mostly used in the TBRES XMLs. The Effect element, however, can be used generally for hand and feet attacks.

* Effect_StartX is the start time value for the effect to take place. L/R is for hands, LF/RF is for feet.
* Effect_EndX is the end time value for the effect to take place.
* Effect_SizeX is self explanatory
* Effect_NameX is also self-explanatory. If you want to look for the effect names for the Werehog, look at EvilSonic’s ar files.
<syntaxhighlight lang="xml">
<Motion>

<Effect>
<REffect_Start1>4</REffect_Start1>
<REffect_End1>16</REffect_End1>
<REffect_Size1>2</REffect_Size1>
<REffect_Name1>evil_punch_01</REffect_Name1>
</Effect>
<Sound></Sound>
</Motion>
</syntaxhighlight>

== Collision ==
The Collision Element deals with the attack’s hitbox, which registers the hits and damage. Both Nec0Arc and NextinFRFX interpreted and discovered the following variables to help you understand what they do:

* The DebugDraw here is potentially an unused debug feature to view the player's attack hitbox collision.
* SizeX is the initial or start size of the attack’s hitbox.
* SizeDeltaX is the final or end size of the attack’s hitbox
* RHandStartX is the frame where the collision hitbox starts, applying the SizeX variable. The specific body hitbox can be changed to any of the following ('''refer to this link''').
* RHandEndX is the frame where the collision hitbox ends, applying the SizeDeltaX variable.
<syntaxhighlight lang="xml">
<Motion>

<Collision>
<DebugDraw>true</DebugDraw>
<Size1>0.75f</Size1>
<SizeDelta1>0.f</SizeDelta1>
<RHandStart1>6</RHandStart1>
<RHandEnd1>16</RHandEnd1>
</Collision>
</Motion>
</syntaxhighlight>

== Camera ==
This element deals with the player’s camera when doing certain attacks. These values were taken from Sho-Hog-Ken (SHAS).

* StartEaseInFrame/StartEaseOutFrame are used to set the range of when the camera eases in and out.
* EaseIn/EaseOut is the value that the camera pulls in or pulls out.
* Fovy probably means FOV (field of view). The Y could be a type or mean the Y-Axis.
* HopeLength… your guess is as good as mine.
* Height is self-explanatory.
<syntaxhighlight lang="xml">
<Motion>

<Camera>
<StartEaseInFrame>15</StartEaseInFrame>
<StartEaseOutFrame>35</StartEaseOutFrame>
<EaseIn>0.5</EaseIn>
<EaseOut>0.75</EaseOut>
<Fovy>10</Fovy>
<HopeLength>1</HopeLength>
<Height>-1.5</Height>
</Camera>
</Motion>
</syntaxhighlight>

== Vibration ==
This element deals with the controller’s vibration, usually when a hit is registered.

* Start/EndFrame are self-explanatory
* BigMoter and SmallMoter are the vibration motors of the control, meaning left or right.
* SuccessTimeLength is how long the vibration lasts if you land a hit
* SuccessBig/SmallMoter is the same thing but for the motors specifically.
<syntaxhighlight lang="xml">
<Motion>

<Vibration>
<StartFrame>-1</StartFrame>
<EndFrame>-1</EndFrame>
<BigMoter>0.f</BigMoter>
<SmallMoter>0.f</SmallMoter>
<SuccessTimeLength>0.01</SuccessTimeLength>
<SuccessBigMoter>0.5f</SuccessBigMoter>
<SuccessSmallMoter>0.5f</SuccessSmallMoter>
</Vibration>
</Motion>
</syntaxhighlight>

== Attack ==
These are the primary Attack values, which we know are connected to the Collision (thanks to Nec0Arc). Let’s take a look at the Attack Variables, which are the final variables you’ll need to complete your Motion:

* Type is one of many different Attack Types that you can use. Refer to the Attack Types documentation
* DamagePower is self-explanatory, and its value is multiplied by the Strength Stat
* KnockOutPower_Y determines the vertical knockback distance for enemies. It seems to be broken in retail.
* KnockOutPower_Dir determines the horizontal knockback distance for enemies. It seems to be broken in retail.
* KnockOutAnglePowerRatio is just a multiplier for both KnockOutPower variables.
* The Attribute variable can be set to Vertical, Side, or FinishAttack.
<syntaxhighlight lang="xml">
<Motion>

<Attack>
<Type1>NormalHard</Type1>
<DamagePower1>100</DamagePower1>
<KnockOutPower_Y1>0.f</KnockOutPower_Y1>
<KnockOutPower_Dir1>2.2f</KnockOutPower_Dir1>
<KnockOutAnglePowerRatio1>0.5f</KnockOutAnglePowerRatio1>
<Attribute1>VerticalAttack</Attribute1>
</Attack>
</Motion>
</syntaxhighlight>

Creating & Customizing Attack Motions (Unique Inputs)

2026-04-20T01:31:33Z

King Galactix:

The '''MotionList''' contains a series of '''Motions''', or the '''Unique Inputs (UIs)''' in the Werehog’s combos. These Motion are XML cells which determine the value of the animation, movement, collision, attack types, and other attributes of each and every unique input of the Werehog's attacks. These elements are extensively long for the purpose of explaining how each variable works and what use cases exist for them, however, it will allow for a greater understanding and application of the mechanics. For convenience's sake, we will create a new scenario by making a new Motion (individual attack) called “MOVE_A” and explain what each variable does.{{Notice|type=note|content=You will need the following files from the #Application archive file:
* EvilAttackAction1.xml
* EvilAttackMotionFile.xml}}

By the end of this guide, you'll have a fairly comprehensive and complete Motion file, such as the example below.<syntaxhighlight lang="xml" line="1" start="125"><Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>
<MotionMoveSpeedRatio>0.875f</MotionMoveSpeedRatio>
<MotionMoveSpeedRatio_Y>1.f</MotionMoveSpeedRatio_Y>
<MotionMoveSpeedRatioFrameStart_1>-1</MotionMoveSpeedRatioFrameStart_1>
<MotionMoveSpeedRatioFrame_1>10.f</MotionMoveSpeedRatioFrame_1>
<MotionMoveSpeedRatioFrameY_1>10.f</MotionMoveSpeedRatioFrameY_1>
<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
<DontCatchTime>0</DontCatchTime>
<DontJump>false</DontJump>
<ShakeCameraStartFrame>-1</ShakeCameraStartFrame>
<GroundHeightRepair>0.1f</GroundHeightRepair>
<MoveType>IngAutoTarget</MoveType>
<AutoTargetEndFrame>9</AutoTargetEndFrame>
<AutoTargetPower>0.2</AutoTargetPower>
<PadRotationIntensity>20</PadRotationIntensity>
<IsGravity>true</IsGravity>
<GravityArray_Start1>-1</GravityArray_Start1>
<IsGravityArray1>true</IsGravityArray1>
<PadRotationIntensity_Start1>0</PadRotationIntensity_Start1>
<PadRotationIntensity_Power1>20</PadRotationIntensity_Power1>
<PadRotationValid1>true</PadRotationValid1>
<PadRotationIntensity_Start2>8</PadRotationIntensity_Start2>
<PadRotationIntensity_Power2>0</PadRotationIntensity_Power2>
<PadRotationValid2>false</PadRotationValid2>
<PadRotationIntensity_Start3>22</PadRotationIntensity_Start3>
<PadRotationIntensity_Power3>20</PadRotationIntensity_Power3>
<PadRotationValid3>true</PadRotationValid3>
<GameSpeed_Start1>0</GameSpeed_Start1>
<GameSpeed_Power1>1</GameSpeed_Power1>
<GameSpeed_CollPower1>1</GameSpeed_CollPower1>
<GuardStartFrame>8</GuardStartFrame>
<GuardEndFrame>27</GuardEndFrame>

<Effect>
<REffect_Start1>4</REffect_Start1>
<REffect_End1>16</REffect_End1>
<REffect_Size1>2</REffect_Size1>
<REffect_Name1>evil_punch_01</REffect_Name1>
</Effect>
<Sound></Sound>
<Collision>
<DebugDraw>true</DebugDraw>
<Size1>0.75f</Size1>
<SizeDelta1>0.f</SizeDelta1>
<RHandStart1>6</RHandStart1>
<RHandEnd1>16</RHandEnd1>
</Collision>
<Vibration>
<StartFrame>-1</StartFrame>
<EndFrame>-1</EndFrame>
<BigMoter>0.f</BigMoter>
<SmallMoter>0.f</SmallMoter>
<SuccessTimeLength>0.01</SuccessTimeLength>
<SuccessBigMoter>0.5f</SuccessBigMoter>
<SuccessSmallMoter>0.5f</SuccessSmallMoter>
</Vibration>
<Attack>
<Type1>NormalHard</Type1>
<DamagePower1>95</DamagePower1>
<KnockOutPower_Y1>0.f</KnockOutPower_Y1>
<KnockOutPower_Dir1>2.2f</KnockOutPower_Dir1>
<KnockOutAnglePowerRatio1>0.5f</KnockOutAnglePowerRatio1>
<Attribute1>VerticalAttack</Attribute1>
</Attack>
</Motion></syntaxhighlight>
== Names ==
We start with the '''MotionName''' and '''FileName'''. The MotionName can be whatever it wants, but the FileName must be exactly as it’s written within EvilAttackMotionFile.xml<syntaxhighlight lang="xml">
<Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
</Motion>
</syntaxhighlight>For the most part, changing the filename is an entirely arbitrary case. But if you’re planning to change the filename anyways:

# Find the name of your animation file (formatted as *.anm.hkx)
# Look for EvilAttackMotionFile.xml, and look within that XML
# You can either change the filename or make a new MotionFileList. However, there are some limitations… so this is an arbitrary action unless you’re using the Beta Combos.
<syntaxhighlight lang="xml" line="1" start="1">
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<Start>
<StartPoint>

<MotionFileList>
<MotionName>NSA</MotionName>
<FileName>evilsonic_attackNSA</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSB</MotionName>
<FileName>evilsonic_attackNSB</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSC</MotionName>
<FileName>evilsonic_attackNSC</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSD</MotionName>
<FileName>evilsonic_attackNSD</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSE</MotionName>
<FileName>evilsonic_attackNSE</FileName>
</MotionFileList>


<MotionFileList>
<MotionName>MOVE_A</MotionName>
<FileName>evilsonic_attackNSE</FileName>
</MotionFileList>
</Start>
</StartPoint>
</syntaxhighlight>

== Animation ==
The animation and movement values here determine how your Motion looks and moves visually and physically.

* '''MotionBlendTimeS''', '''MotionBlendTimeE''', and '''MotionBlendTimeEIdle''' blend the animations between a previous and following combo. Keep the values as 0.02f.

* '''MotionFirstSpeed''', '''MiddleSpeed''', and '''EndSpeed''' all affect the Attack’s animation speed.
* '''MotionSpeed_First'''/'''MiddleFrame''' represents when the MotionFirstSpeed and MiddleSpeed params are executed (corresponding with the animation frames).
<syntaxhighlight lang="xml" line="1">
<Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>

<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
</Motion>
</syntaxhighlight>

== Movement ==
Now we can take a look at more general variables. These are equally important for combat and visual aspects of the Werehog.

* '''MotionMoveSpeedRatio''' (MMSR for convenience) and '''MotionMoveSpeedRatio_Y''' control the player’s movement ratio when making the entire attack. You can experiment with these values, but remember to write it in the form of “A.Bf”
* '''MotionMoveSpeedRatioFrameStart_N,''' '''MotionMoveSpeedRatioFrame_N,''' and '''MotionMoveSpeedRatioFrameY_N''' apply the same movement/distance ratio, except it’s done within a certain frame. Reference other moves if you want to make an attack move more or less in a certain direction.
** For example: moves that rise up at a certain frame, such as a launcher, should multiply MotionMoveSpeedRatioFrameY_N by a significant amount, more than MotionMoveSpeedRatioFrame_N.
*'''EndSkipTimeWhenPad''' determines when the move can skip itself after being moved by the PadRotation variables (refer to PadRotation section).
*'''AttackScope''' sets the maximum scope of turning while attacking. You have None, Scope90, and Scope360 to use, which only work with enabled PadRotation variables (more in the Gravity/PadRotation section).
*'''DontCatchTime''' states how long it takes before the player can use the grab. Set it to 0 for ground moves, 2 for aerial moves.
* '''DontJump''' is self-explanatory. You apply it for whatever moves you DON'T want to have an enabled jump afterwards, such as Sho-Hog-Ken (YYA), and disable it for combo that you want to jump with, such as Unleashed Wild Combo (XX-YY-XX-YY).
* '''OnceSendDamage''' determines how long a combo can continually send damage. The default value is usually zero, and many moves use this as a way of implementing multiple hits for combos with a single or more number of hitboxes.
* '''ShakeCameraStartFrame''' is the start frame for when the Camera Shake can happen for certain moves. Unfortunately, there are no specific variables to affect the number or intensity of shakes.
* '''GroundHeightRepair''' determines the floatiness of a move. Lower values mean more floaty and higher values mean less floaty.
* '''MoveType''' has two values: Default and IngAutoTarget (the variables below only work when IngAutoTarget is enabled.
* '''AutoTargetEndFrame''' can be set to 0 for Default, and any value for IngAutoTarget
* '''AutoTargetPower''' can be set to 0 for Default, and any value for IngAutoTarget
<syntaxhighlight lang="xml"> <Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>
<MotionMoveSpeedRatio>0.875f</MotionMoveSpeedRatio> 
<MotionMoveSpeedRatio_Y>1.f</MotionMoveSpeedRatio_Y>
<MotionMoveSpeedRatioFrameStart_1>-1</MotionMoveSpeedRatioFrameStart_1>
<MotionMoveSpeedRatioFrame_1>10.f</MotionMoveSpeedRatioFrame_1>
<MotionMoveSpeedRatioFrameY_1>10.f</MotionMoveSpeedRatioFrameY_1>
<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<EndSkipTimeWhenPad>0.f</EndSkipTimeWhenPad>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
<DontCatchTime>0</DontCatchTime>
<DontJump>false</DontJump>
<OnceSendDamage>0</OnceSendDamage> 
<ShakeCameraStartFrame>-1</ShakeCameraStartFrame>
<GroundHeightRepair>0.1f</GroundHeightRepair>
<MoveType>IngAutoTarget</MoveType>
<AutoTargetEndFrame>9</AutoTargetEndFrame>
<AutoTargetPower>0.2</AutoTargetPower>
</Motion></syntaxhighlight>

== Gravity and PadRotation ==
The following Gravity and PadRotation variables are interpreted and explained by Nec0Arc and myself, so you can understand how to adjust the player’s movement across the X, Y, and Z axis. The value of these variables depend on what kind of attack you would want (grounded, launcher, aerial, unidirectional, multidirectional, etc.)

* '''PadRotationIntensity''' is a general value that of the attack's rotation via the left stick. It is assumed the value is represented in degrees or whatever value is used by the controller's left-stick.
* '''IsGravity''' and its subsequent parameters, '''GravityArray_StartX''' and '''IsGravityArrayX''' determines the combos's application of gravity while doing a combo. IsGravity and IsGravityX use true/false.
** Ground moves follow the setup below for its gravity arrays and values.
** Launcher moves follow the setup below for its gravity arrays and values.
** Aerial moves follow the setup below for its gravity arrays and values:
* '''PadRotationIntensity_StartX''' sets the frame that this instance of PadRotationcan start executing.
* '''PadRotationIntensity_PowerX''' sets the degrees of PadRotation that your player can move when executing the combo.
* '''PadRotationValidX''' enables or disables the PadRotation with true or false.
<syntaxhighlight lang="xml"> <Motion>

<PadRotationIntensity>20</PadRotationIntensity>
<IsGravity>true</IsGravity>
<GravityArray_Start1>-1</GravityArray_Start1>
<IsGravityArray1>true</IsGravityArray1>
<PadRotationIntensity_Start1>0</PadRotationIntensity_Start1>
<PadRotationIntensity_Power1>20</PadRotationIntensity_Power1>
<PadRotationValid1>true</PadRotationValid1>
<PadRotationIntensity_Start2>8</PadRotationIntensity_Start2>
<PadRotationIntensity_Power2>0</PadRotationIntensity_Power2>
<PadRotationValid2>false</PadRotationValid2>
<PadRotationIntensity_Start3>22</PadRotationIntensity_Start3>
<PadRotationIntensity_Power3>20</PadRotationIntensity_Power3>
<PadRotationValid3>true</PadRotationValid3>
</Motion></syntaxhighlight>

== GameSpeed and Guarding ==
The following discoveries were made by BaconYum and myself: GameSpeed represents the “Slow Motion” moments that happen with attacks, so let’s look at the variables:

* GameSpeed_StartX refers to the specific frame that starts the GameSpeed variable.
* GameSpeed_PowerX refers to the power of this GameSpeed modifier, which is simple to understand.
** A value of 1 means the game’s speed is normal
** 1 > X > 0 means the game’s speed is slowed down by that amount. So if you have a value of 0.5, the game’s speed is halved.
** A value above 1 means the game’s speed is sped up by that amount. A value of 2 means the game’s speed is doubled.
* GameSpeed_CollPowerX does the same thing, except it refers to the player’s collision when doing the attack.
* GuardStart/EndFrame are self-explanatory, and they surprisingly explain the mechanic of Shield Cancelling… neat!
* There are unused parameter values, called GameSpeedColl. At this time, they have not been tested to see their functionality.
<syntaxhighlight lang="xml"> <Motion>

<GameSpeed_Start1>0</GameSpeed_Start1>
<GameSpeed_Power1>1</GameSpeed_Power1>
<GameSpeed_CollPower1>1</GameSpeed_CollPower1>
<GuardStartFrame>8</GuardStartFrame>
<GuardEndFrame>27</GuardEndFrame>

</Motion></syntaxhighlight>

== Sound and Effects ==
The Sound element is unused in the main game’s Attack XML, mostly used in the TBRES XMLs. The Effect element, however, can be used generally for hand and feet attacks.

* Effect_StartX is the start time value for the effect to take place. L/R is for hands, LF/RF is for feet.
* Effect_EndX is the end time value for the effect to take place.
* Effect_SizeX is self explanatory
* Effect_NameX is also self-explanatory. If you want to look for the effect names for the Werehog, look at EvilSonic’s ar files.

== Collision ==
The Collision Element deals with the attack’s hitbox, which registers the hits and damage. Both Nec0Arc and NextinFRFX interpreted and discovered the following variables to help you understand what they do:

* Just keep it as true. I don’t know what it does.
* SizeX is the initial or start size of the attack’s hitbox.
* SizeDeltaX is the final or end size of the attack’s hitbox
* RHandStartX is the frame where the collision hitbox starts, applying the SizeX variable. The specific body hitbox can be changed ('''refer to this link''').
* RHandEndX is the frame where the collision hitbox ends, applying the SizeDeltaX variable.

== Camera ==
This element deals with the player’s camera when doing certain attacks. These values were taken from Sho-Hog-Ken (SHAS).

* StartEaseInFrame/StartEaseOutFrame are used to set the range of when the camera eases in and out.
* EaseIn/EaseOut is the value that the camera pulls in or pulls out.
* Fovy probably means FOV (field of view). The Y could be a type or mean the Y-Axis.
* HopeLength… your guess is as good as mine.
* Height is self-explanatory.
<syntaxhighlight lang="xml">
<Motion>

<Camera>
<StartEaseInFrame>15</StartEaseInFrame>
<StartEaseOutFrame>35</StartEaseOutFrame>
<EaseIn>0.5</EaseIn>
<EaseOut>0.75</EaseOut>
<Fovy>10</Fovy>
<HopeLength>1</HopeLength>
<Height>-1.5</Height>
</Camera>
</Motion>
</syntaxhighlight>

== Vibration ==
This element deals with the controller’s vibration, usually when a hit is registered.

* Start/EndFrame are self-explanatory
* BigMoter and SmallMoter are the vibration motors of the control, meaning left or right.
* SuccessTimeLength is how long the vibration lasts if you land a hit
* SuccessBig/SmallMoter is the same thing but for the motors specifically.

== Attack ==
These are the primary Attack values, which we know are connected to the Collision (thanks to Nec0Arc). Let’s take a look at the Attack Variables, which are the final variables you’ll need to complete your Motion:

* Type is one of many different Attack Types that you can use. Refer to the Attack Types documentation
* DamagePower is self-explanatory, and its value is multiplied by the Strength Stat
* KnockOutPower_Y determines the vertical knockback distance for enemies. Possibly broken.
* KnockOutPower_Dir determines the horizontal knockback distance for enemies. Possibly broken.
* KnockOutAnglePowerRatio is just a multiplier for both KnockOutPower variables.
* The Attribute variable can be set to Vertical, Side, or FinishAttack.
<syntaxhighlight lang="xml">
<Motion>

<Attack>
<Type1>NormalHard</Type1>
<DamagePower1>100</DamagePower1>
<KnockOutPower_Y1>0.f</KnockOutPower_Y1>
<KnockOutPower_Dir1>2.2f</KnockOutPower_Dir1>
<KnockOutAnglePowerRatio1>0.5f</KnockOutAnglePowerRatio1>
<Attribute1>VerticalAttack</Attribute1>
</Attack>
</Motion>
</syntaxhighlight>

Creating & Customizing Attack Motions (Unique Inputs)

2026-04-18T05:01:24Z

King Galactix:

The '''MotionList''' contains a series of '''Motions''', or the '''Unique Inputs (UIs)''' in the Werehog’s combos. These Motion are XML cells which determine the value of the animation, movement, collision, attack types, and other attributes of each and every unique input of the Werehog's attacks. These elements are extensively long for the purpose of explaining how each variable works and what use cases exist for them, however, it will allow for a greater understanding and application of the mechanics. For convenience's sake, we will create a new scenario by making a new Motion (individual attack) called “MOVE_A” and explain what each variable does.{{Notice|type=note|content=You will need the following files from the #Application archive file:
* EvilAttackAction1.xml
* EvilAttackMotionFile.xml}}

By the end of this guide, you'll have a fairly comprehensive and complete Motion file, such as the example below.<syntaxhighlight lang="xml" line="1" start="125"> <Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>
<MotionMoveSpeedRatio>0.875f</MotionMoveSpeedRatio>
<MotionMoveSpeedRatio_Y>1.f</MotionMoveSpeedRatio_Y>
<MotionMoveSpeedRatioFrameStart_1>-1</MotionMoveSpeedRatioFrameStart_1>
<MotionMoveSpeedRatioFrame_1>10.f</MotionMoveSpeedRatioFrame_1>
<MotionMoveSpeedRatioFrameY_1>10.f</MotionMoveSpeedRatioFrameY_1>
<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
<DontCatchTime>0</DontCatchTime>
<DontJump>false</DontJump>
<ShakeCameraStartFrame>-1</ShakeCameraStartFrame>
<GroundHeightRepair>0.1f</GroundHeightRepair>
<MoveType>IngAutoTarget</MoveType>
<AutoTargetEndFrame>9</AutoTargetEndFrame>
<AutoTargetPower>0.2</AutoTargetPower>
<PadRotationIntensity>20</PadRotationIntensity>
<IsGravity>true</IsGravity>
<GravityArray_Start1>-1</GravityArray_Start1>
<IsGravityArray1>true</IsGravityArray1>
<PadRotationIntensity_Start1>0</PadRotationIntensity_Start1>
<PadRotationIntensity_Power1>20</PadRotationIntensity_Power1>
<PadRotationValid1>true</PadRotationValid1>
<PadRotationIntensity_Start2>8</PadRotationIntensity_Start2>
<PadRotationIntensity_Power2>0</PadRotationIntensity_Power2>
<PadRotationValid2>false</PadRotationValid2>
<PadRotationIntensity_Start3>22</PadRotationIntensity_Start3>
<PadRotationIntensity_Power3>20</PadRotationIntensity_Power3>
<PadRotationValid3>true</PadRotationValid3>
<GameSpeed_Start1>0</GameSpeed_Start1>
<GameSpeed_Power1>1</GameSpeed_Power1>
<GameSpeed_CollPower1>1</GameSpeed_CollPower1>
<GuardStartFrame>8</GuardStartFrame>
<GuardEndFrame>27</GuardEndFrame>

<Effect>
<REffect_Start1>4</REffect_Start1>
<REffect_End1>16</REffect_End1>
<REffect_Size1>2</REffect_Size1>
<REffect_Name1>evil_punch_01</REffect_Name1>
</Effect>
<Sound></Sound>
<Collision>
<DebugDraw>true</DebugDraw>
<Size1>0.75f</Size1>
<SizeDelta1>0.f</SizeDelta1>
<RHandStart1>6</RHandStart1>
<RHandEnd1>16</RHandEnd1>
</Collision>
<Vibration>
<StartFrame>-1</StartFrame>
<EndFrame>-1</EndFrame>
<BigMoter>0.f</BigMoter>
<SmallMoter>0.f</SmallMoter>
<SuccessTimeLength>0.01</SuccessTimeLength>
<SuccessBigMoter>0.5f</SuccessBigMoter>
<SuccessSmallMoter>0.5f</SuccessSmallMoter>
</Vibration>
<Attack>
<Type1>NormalHard</Type1>
<DamagePower1>95</DamagePower1>
<KnockOutPower_Y1>0.f</KnockOutPower_Y1>
<KnockOutPower_Dir1>2.2f</KnockOutPower_Dir1>
<KnockOutAnglePowerRatio1>0.5f</KnockOutAnglePowerRatio1>
<Attribute1>VerticalAttack</Attribute1>
</Attack>
</Motion></syntaxhighlight>
== Names ==
We start with the '''MotionName''' and '''FileName'''. The MotionName can be whatever it wants, but the FileName must be exactly as it’s written within EvilAttackMotionFile.xml<syntaxhighlight lang="xml">
<Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
</Motion>
</syntaxhighlight>For the most part, changing the filename is an entirely arbitrary case. But if you’re planning to change the filename anyways:

# Find the name of your animation file (formatted as *.anm.hkx)
# Look for EvilAttackMotionFile.xml, and look within that XML
# You can either change the filename or make a new MotionFileList. However, there are some limitations… so this is an arbitrary action unless you’re using the Beta Combos.
<syntaxhighlight lang="xml" line="1" start="1">
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<Start>
<StartPoint>

<MotionFileList>
<MotionName>NSA</MotionName>
<FileName>evilsonic_attackNSA</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSB</MotionName>
<FileName>evilsonic_attackNSB</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSC</MotionName>
<FileName>evilsonic_attackNSC</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSD</MotionName>
<FileName>evilsonic_attackNSD</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSE</MotionName>
<FileName>evilsonic_attackNSE</FileName>
</MotionFileList>


<MotionFileList>
<MotionName>MOVE_A</MotionName>
<FileName>evilsonic_attackNSE</FileName>
</MotionFileList>
</Start>
</StartPoint>
</syntaxhighlight>

== Animation ==
The animation and movement values here determine how your Motion looks and moves visually and physically.

* '''MotionBlendTimeS''', '''MotionBlendTimeE''', and '''MotionBlendTimeEIdle''' blend the animations between a previous and following combo. Keep the values as 0.02f.

* '''MotionFirstSpeed''', '''MiddleSpeed''', and '''EndSpeed''' all affect the Attack’s animation speed.
* '''MotionSpeed_First'''/'''MiddleFrame''' represents when the MotionFirstSpeed and MiddleSpeed params are executed (corresponding with the animation frames).
<syntaxhighlight lang="xml" line="1">
<Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>

<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
</Motion>
</syntaxhighlight>

== Movement ==
Now we can take a look at more general variables. These are equally important for combat and visual aspects of the Werehog.

* '''MotionMoveSpeedRatio''' (MMSR for convenience) and '''MotionMoveSpeedRatio_Y''' control the player’s movement ratio when making the entire attack. You can experiment with these values, but remember to write it in the form of “A.Bf”
* '''MotionMoveSpeedRatioFrameStart_N,''' '''MotionMoveSpeedRatioFrame_N,''' and '''MotionMoveSpeedRatioFrameY_N''' apply the same movement/distance ratio, except it’s done within a certain frame. Reference other moves if you want to make an attack move more or less in a certain direction.
** For example: moves that rise up at a certain frame, such as a launcher, should multiply MotionMoveSpeedRatioFrameY_N by a significant amount, more than MotionMoveSpeedRatioFrame_N.
*'''EndSkipTimeWhenPad''' determines when the move can skip itself after being moved by the PadRotation variables (refer to PadRotation section).
*'''AttackScope''' sets the maximum scope of turning while attacking. You have None, Scope90, and Scope360 to use, which only work with enabled PadRotation variables (more in the Gravity/PadRotation section).
*'''DontCatchTime''' states how long it takes before the player can use the grab. Set it to 0 for ground moves, 2 for aerial moves.
* '''DontJump''' is self-explanatory. You apply it for whatever moves you DON'T want to have an enabled jump afterwards, such as Sho-Hog-Ken (YYA), and disable it for combo that you want to jump with, such as Unleashed Wild Combo (XX-YY-XX-YY).
* '''OnceSendDamage''' determines how long a combo can continually send damage. The default value is usually zero, and many moves use this as a way of implementing multiple hits for combos with a single or more number of hitboxes.
* '''ShakeCameraStartFrame''' is the start frame for when the Camera Shake can happen for certain moves. Unfortunately, there are no specific variables to affect the number or intensity of shakes.
* '''GroundHeightRepair''' determines the floatiness of a move. Lower values mean more floaty and higher values mean less floaty.
* '''MoveType''' has two values: Default and IngAutoTarget (the variables below only work when IngAutoTarget is enabled.
* '''AutoTargetEndFrame''' can be set to 0 for Default, and any value for IngAutoTarget
* '''AutoTargetPower''' can be set to 0 for Default, and any value for IngAutoTarget
<syntaxhighlight lang="xml"><Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>
<MotionMoveSpeedRatio>0.875f</MotionMoveSpeedRatio> 
<MotionMoveSpeedRatio_Y>1.f</MotionMoveSpeedRatio_Y>
<MotionMoveSpeedRatioFrameStart_1>-1</MotionMoveSpeedRatioFrameStart_1>
<MotionMoveSpeedRatioFrame_1>10.f</MotionMoveSpeedRatioFrame_1>
<MotionMoveSpeedRatioFrameY_1>10.f</MotionMoveSpeedRatioFrameY_1>
<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<EndSkipTimeWhenPad>0.f</EndSkipTimeWhenPad>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
<DontCatchTime>0</DontCatchTime>
<DontJump>false</DontJump>
<OnceSendDamage>0</OnceSendDamage> 
<ShakeCameraStartFrame>-1</ShakeCameraStartFrame>
<GroundHeightRepair>0.1f</GroundHeightRepair>
<MoveType>IngAutoTarget</MoveType>
<AutoTargetEndFrame>9</AutoTargetEndFrame>
<AutoTargetPower>0.2</AutoTargetPower>
</Motion></syntaxhighlight>

== Gravity and PadRotation ==
The following Gravity and PadRotation variables are interpreted and explained by Nec0Arc and myself, so you can understand how to adjust the player’s movement across the X, Y, and Z axis. The value of these variables depend on what kind of attack you would want (grounded, launcher, aerial, unidirectional, multidirectional, etc.)

* '''PadRotationIntensity''' is a general value that of the attack's rotation via the left stick. It is assumed the value is represented in degrees or whatever value is used by the controller's left-stick.
* '''IsGravity''' and its subsequent parameters, '''GravityArray_StartX''' and '''IsGravityArrayX''' determines the combos's application of gravity while doing a combo. IsGravity and IsGravityX use true/false.
** Ground moves follow the setup below for its gravity arrays and values.
** Launcher moves follow the setup below for its gravity arrays and values.
** Aerial moves follow the setup below for its gravity arrays and values:
* '''PadRotationIntensity_StartX''' sets the keyframe for the player’s movement during an attack.
* '''PadRotationIntensity_PowerX''' sets the degrees of rotation your player can move.
* '''PadRotationValidX''' just sets the value to true or false.

== GameSpeed and Guarding ==
The following discoveries were made by BaconYum and myself: GameSpeed represents the “Slow Motion” moments that happen with attacks, so let’s look at the variables:

* GameSpeed_StartX refers to the specific frame that starts the GameSpeed variable.
* GameSpeed_PowerX refers to the power of this GameSpeed modifier, which is simple to understand.
** A value of 1 means the game’s speed is normal
** 1 > X > 0 means the game’s speed is slowed. So if you have a value of 0.5, the game’s speed is halved.
** A value above 1 means the game’s speed is multiplied by that amount. A value of 2 means the game’s speed is doubled.
* GameSpeed_CollPowerX does the same thing, except it refers to the player’s collision when doing the attack.
* GuardStart/EndFrame are self-explanatory, and they surprisingly explain the mechanic of Shield Cancelling… neat!

== Sound and Effects ==
The Sound element is unused in the main game’s Attack XML, mostly used in the TBRES XMLs. The Effect element, however, can be used generally for hand and feet attacks.

* Effect_StartX is the start time value for the effect to take place. L/R is for hands, LF/RF is for feet.
* Effect_EndX is the end time value for the effect to take place.
* Effect_SizeX is self explanatory
* Effect_NameX is also self-explanatory. If you want to look for the effect names for the Werehog, look at EvilSonic’s ar files.

== Collision ==
The Collision Element deals with the attack’s hitbox, which registers the hits and damage. Both Nec0Arc and NextinFRFX interpreted and discovered the following variables to help you understand what they do:

* Just keep it as true. I don’t know what it does.
* SizeX is the initial or start size of the attack’s hitbox.
* SizeDeltaX is the final or end size of the attack’s hitbox
* RHandStartX is the frame where the collision hitbox starts, applying the SizeX variable. The specific body hitbox can be changed ('''refer to this link''').
* RHandEndX is the frame where the collision hitbox ends, applying the SizeDeltaX variable.

== Camera ==
This element deals with the player’s camera when doing certain attacks. These values were taken from Sho-Hog-Ken (SHAS).

* StartEaseInFrame/StartEaseOutFrame are used to set the range of when the camera eases in and out.
* EaseIn/EaseOut is the value that the camera pulls in or pulls out.
* Fovy probably means FOV (field of view). The Y could be a type or mean the Y-Axis.
* HopeLength… your guess is as good as mine.
* Height is self-explanatory.

== Vibration ==
This element deals with the controller’s vibration, usually when a hit is registered.

* Start/EndFrame are self-explanatory
* BigMoter and SmallMoter are the vibration motors of the control, meaning left or right.
* SuccessTimeLength is how long the vibration lasts if you land a hit
* SuccessBig/SmallMoter is the same thing but for the motors specifically.

== Attack ==
These are the primary Attack values, which we know are connected to the Collision (thanks to Nec0Arc). Let’s take a look at the Attack Variables, which are the final variables you’ll need to complete your Motion:

* Type is one of many different Attack Types that you can use. Refer to the Attack Types documentation
* DamagePower is self-explanatory, and its value is multiplied by the Strength Stat
* KnockOutPower_Y determines the vertical knockback distance for enemies. Possibly broken.
* KnockOutPower_Dir determines the horizontal knockback distance for enemies. Possibly broken.
* KnockOutAnglePowerRatio is just a multiplier for both KnockOutPower variables.
* The Attribute variable can be set to Vertical, Side, or FinishAttack.
<syntaxhighlight lang="xml">
<Motion>

<Attack>
<Type1>NormalHard</Type1>
<DamagePower1>100</DamagePower1>
<KnockOutPower_Y1>0.f</KnockOutPower_Y1>
<KnockOutPower_Dir1>2.2f</KnockOutPower_Dir1>
<KnockOutAnglePowerRatio1>0.5f</KnockOutAnglePowerRatio1>
<Attribute1>VerticalAttack</Attribute1>
</Attack>
</Motion>
</syntaxhighlight>

Creating & Customizing Attack Motions (Unique Inputs)

2026-04-01T15:37:53Z

King Galactix:

The '''MotionList''' contains a series of '''Motions''', or the '''Unique Inputs (UIs)''' in the Werehog’s combos. These Motion are XML cells which determine the value of the animation, movement, collision, attack types, and other attributes of each and every unique input of the Werehog's attacks. These elements are extensively long because of their content, so we will break each section down for you. For convenience's sake, we will create a new scenario by making a new Motion (individual attack) called “MOVE_A” and explain what each variable does.{{Notice|type=note|content=You will need the following files from the #Application archive file:
* EvilAttackAction1.xml
* EvilAttackMotionFile.xml}}

By the end of this guide, you'll have a fairly comprehensive and complete Motion file, such as the example below.<syntaxhighlight lang="xml" line="1" start="125"><Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>
<MotionMoveSpeedRatio>0.875f</MotionMoveSpeedRatio>
<MotionMoveSpeedRatio_Y>1.f</MotionMoveSpeedRatio_Y>
<MotionMoveSpeedRatioFrameStart_1>-1</MotionMoveSpeedRatioFrameStart_1>
<MotionMoveSpeedRatioFrame_1>10.f</MotionMoveSpeedRatioFrame_1>
<MotionMoveSpeedRatioFrameY_1>10.f</MotionMoveSpeedRatioFrameY_1>
<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
<DontCatchTime>0</DontCatchTime>
<DontJump>false</DontJump>
<ShakeCameraStartFrame>-1</ShakeCameraStartFrame>
<GroundHeightRepair>0.1f</GroundHeightRepair>
<MoveType>IngAutoTarget</MoveType>
<AutoTargetEndFrame>9</AutoTargetEndFrame>
<AutoTargetPower>0.2</AutoTargetPower>
<PadRotationIntensity>20</PadRotationIntensity>
<IsGravity>true</IsGravity>
<GravityArray_Start1>-1</GravityArray_Start1>
<IsGravityArray1>true</IsGravityArray1>
<PadRotationIntensity_Start1>0</PadRotationIntensity_Start1>
<PadRotationIntensity_Power1>20</PadRotationIntensity_Power1>
<PadRotationValid1>true</PadRotationValid1>
<PadRotationIntensity_Start2>8</PadRotationIntensity_Start2>
<PadRotationIntensity_Power2>0</PadRotationIntensity_Power2>
<PadRotationValid2>false</PadRotationValid2>
<PadRotationIntensity_Start3>22</PadRotationIntensity_Start3>
<PadRotationIntensity_Power3>20</PadRotationIntensity_Power3>
<PadRotationValid3>true</PadRotationValid3>
<GameSpeed_Start1>0</GameSpeed_Start1>
<GameSpeed_Power1>1</GameSpeed_Power1>
<GameSpeed_CollPower1>1</GameSpeed_CollPower1>
<GuardStartFrame>8</GuardStartFrame>
<GuardEndFrame>27</GuardEndFrame>

<Effect>
<REffect_Start1>4</REffect_Start1>
<REffect_End1>16</REffect_End1>
<REffect_Size1>2</REffect_Size1>
<REffect_Name1>evil_punch_01</REffect_Name1>
</Effect>
<Sound></Sound>
<Collision>
<DebugDraw>true</DebugDraw>
<Size1>0.75f</Size1>
<SizeDelta1>0.f</SizeDelta1>
<RHandStart1>6</RHandStart1>
<RHandEnd1>16</RHandEnd1>
</Collision>
<Vibration>
<StartFrame>-1</StartFrame>
<EndFrame>-1</EndFrame>
<BigMoter>0.f</BigMoter>
<SmallMoter>0.f</SmallMoter>
<SuccessTimeLength>0.01</SuccessTimeLength>
<SuccessBigMoter>0.5f</SuccessBigMoter>
<SuccessSmallMoter>0.5f</SuccessSmallMoter>
</Vibration>
<Attack>
<Type1>NormalHard</Type1>
<DamagePower1>95</DamagePower1>
<KnockOutPower_Y1>0.f</KnockOutPower_Y1>
<KnockOutPower_Dir1>2.2f</KnockOutPower_Dir1>
<KnockOutAnglePowerRatio1>0.5f</KnockOutAnglePowerRatio1>
<Attribute1>VerticalAttack</Attribute1>
</Attack>
</Motion></syntaxhighlight>
== Names ==
We start with the '''MotionName''' and '''FileName'''. The MotionName can be whatever it wants, but the FileName must be exactly as it’s written within EvilAttackMotionFile.xml<syntaxhighlight lang="xml">
<Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
</Motion>
</syntaxhighlight>For the most part, changing the filename is an entirely arbitrary case. But if you’re planning to change the filename anyways:

# Find the name of your animation file (formatted as *.anm.hkx)
# Look for EvilAttackMotionFile.xml, and look within that XML
# You can either change the filename or make a new MotionFileList. However, there are some limitations… so this is an arbitrary action unless you’re using the Beta Combos.
<syntaxhighlight lang="xml" line="1" start="1">
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<Start>
<StartPoint>

<MotionFileList>
<MotionName>NSA</MotionName>
<FileName>evilsonic_attackNSA</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSB</MotionName>
<FileName>evilsonic_attackNSB</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSC</MotionName>
<FileName>evilsonic_attackNSC</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSD</MotionName>
<FileName>evilsonic_attackNSD</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSE</MotionName>
<FileName>evilsonic_attackNSE</FileName>
</MotionFileList>


<MotionFileList>
<MotionName>MOVE_A</MotionName>
<FileName>evilsonic_attackNSE</FileName>
</MotionFileList>
</Start>
</StartPoint>
</syntaxhighlight>

== Animation and Movement ==
The animation and movement values here determine how your Motion looks and moves visually and physically.

* '''MotionBlendTimeS''', '''MotionBlendTimeE''', and '''MotionBlendTimeEIdle''' blend the animations between a previous and following combo. Keep the values as 0.02f.
* '''MotionMoveSpeedRatio''' (MMSR for convenience) and '''MotionMoveSpeedRatio_Y''' control the player’s movement ratio when making the entire attack. You can experiment with these values, but remember to write it in the form of “A.Bf”
* '''MotionMoveSpeedRatioFrameStart_N,''' '''MotionMoveSpeedRatioFrame_N,''' and '''MotionMoveSpeedRatioFrameY_N''' apply the same movement/distance ratio, except it’s done within a certain frame. Reference other moves if you want to make an attack move more or less in a certain direction.
** For example: moves that rise up at a certain frame, such as a launcher, should multiply MotionMoveSpeedRatioFrameY_N by a significant amount, more than MotionMoveSpeedRatioFrame_N.
* '''MotionFirstSpeed''', '''MiddleSpeed''', and '''EndSpeed''' all affect the Attack’s animation speed.
* '''MotionSpeed_First'''/'''MiddleFrame''' represents when the MotionFirstSpeed and MiddleSpeed params are executed (corresponding with the animation frames).
<syntaxhighlight lang="xml" line="1">
<Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>
<MotionMoveSpeedRatio>0.875f</MotionMoveSpeedRatio>
<MotionMoveSpeedRatio_Y>1.f</MotionMoveSpeedRatio_Y>
<MotionMoveSpeedRatioFrameStart_1>-1</MotionMoveSpeedRatioFrameStart_1>
<MotionMoveSpeedRatioFrame_1>10.f</MotionMoveSpeedRatioFrame_1>
<MotionMoveSpeedRatioFrameY_1>10.f</MotionMoveSpeedRatioFrameY_1>
<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
</Motion>
</syntaxhighlight>

== General ==
Now we can take a look at more general variables. These are equally important for combat and visual aspects of the Werehog.

* '''AttackScope''' sets the maximum scope of turning while attacking. You have None, Scope90, and Scope360 to use, which only work with enabled PadRotation variables (more in the Gravity/PadRotation section).
* '''DontCatchTime''' states how long it takes before the player can use the grab. Set it to 0 for ground moves, 2 for aerial moves.
* '''DontJump''' is self-explanatory. You apply it for whatever moves you DON'T want to have an enabled jump afterwards, such as Sho-Hog-Ken (YYA), and disable it for combo that you want to jump with, such as Unleashed Wild Combo (XX-YY-XX-YY).
* '''OnceSendDamage''' determines how long a combo can continually send damage. The default value is usually zero, and many moves use this as a way of implementing multiple hits for combos with a single or more number of hitboxes.
* '''ShakeCameraStartFrame''' is the start frame for when the Camera Shake can happen for certain moves. Unfortunately, there are no specific variables to affect the number or intensity of shakes.
* '''GroundHeightRepair''' determines the floatiness of a move. Lower values mean more floaty and higher values mean less floaty.
* '''MoveType''' has two values: Default and IngAutoTarget (the variables below only work when IngAutoTarget is enabled.
* '''AutoTargetEndFrame''' can be set to 0 for Default, and any value for IngAutoTarget
* '''AutoTargetPower''' can be set to 0 for Default, and any value for IngAutoTarget
<syntaxhighlight lang="xml">
<Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>
<MotionMoveSpeedRatio>0.875f</MotionMoveSpeedRatio>
<MotionMoveSpeedRatio_Y>1.f</MotionMoveSpeedRatio_Y>
<MotionMoveSpeedRatioFrameStart_1>-1</MotionMoveSpeedRatioFrameStart_1>
<MotionMoveSpeedRatioFrame_1>10.f</MotionMoveSpeedRatioFrame_1>
<MotionMoveSpeedRatioFrameY_1>10.f</MotionMoveSpeedRatioFrameY_1>
<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
<DontCatchTime>0</DontCatchTime>
<DontJump>false</DontJump>
<OnceSendDamage>0</OnceSendDamage> 
<ShakeCameraStartFrame>-1</ShakeCameraStartFrame>
<GroundHeightRepair>0.1f</GroundHeightRepair>
<MoveType>IngAutoTarget</MoveType>
<AutoTargetEndFrame>9</AutoTargetEndFrame>
<AutoTargetPower>0.2</AutoTargetPower>
</Motion>
</syntaxhighlight>

== Gravity and PadRotation ==
The following Gravity and PadRotation variables are interpreted and explained by Nec0Arc and myself, so you can understand how to adjust the player’s movement across the X, Y, and Z axis. The value of these variables depend on what kind of attack you would want (grounded, launcher, aerial, unidirectional, multidirectional, etc.)

* PadRotationIntensity is a general value that of the attack's rotation via the left stick. It is assumed the value is represented in degrees or whatever value is used by the controller's left-stick.
* '''IsGravity''' and its subsequent parameters, '''GravityArray_StartX''' and '''IsGravityArrayX''' determines the combos's application of gravity while doing a combo. IsGravity and IsGravityX use true/false.
** Ground moves follow the setup below for its gravity arrays and values.
** Launcher moves follow the setup below for its gravity arrays and values.
** Aerial moves follow the setup below for its gravity arrays and values:
* PadRotationIntensity_StartX sets the keyframe for the player’s movement during an attack.
* PadRotationIntensity_PowerX sets the degrees of rotation your player can move.
* PadRotationValidX just sets the value to true or false.

== GameSpeed and Guarding ==
The following discoveries were made by BaconYum and myself: GameSpeed represents the “Slow Motion” moments that happen with attacks, so let’s look at the variables:

* GameSpeed_StartX refers to the specific frame that starts the GameSpeed variable.
* GameSpeed_PowerX refers to the power of this GameSpeed modifier, which is simple to understand.
** A value of 1 means the game’s speed is normal
** 1 > X > 0 means the game’s speed is slowed. So if you have a value of 0.5, the game’s speed is halved.
** A value above 1 means the game’s speed is multiplied by that amount. A value of 2 means the game’s speed is doubled.
* GameSpeed_CollPowerX does the same thing, except it refers to the player’s collision when doing the attack.
* GuardStart/EndFrame are self-explanatory, and they surprisingly explain the mechanic of Shield Cancelling… neat!

== Sound and Effects ==
The Sound element is unused in the main game’s Attack XML, mostly used in the TBRES XMLs. The Effect element, however, can be used generally for hand and feet attacks.

* Effect_StartX is the start time value for the effect to take place. L/R is for hands, LF/RF is for feet.
* Effect_EndX is the end time value for the effect to take place.
* Effect_SizeX is self explanatory
* Effect_NameX is also self-explanatory. If you want to look for the effect names for the Werehog, look at EvilSonic’s ar files.

== Collision ==
The Collision Element deals with the attack’s hitbox, which registers the hits and damage. Both Nec0Arc and NextinFRFX interpreted and discovered the following variables to help you understand what they do:

* Just keep it as true. I don’t know what it does.
* SizeX is the initial or start size of the attack’s hitbox.
* SizeDeltaX is the final or end size of the attack’s hitbox
* RHandStartX is the frame where the collision hitbox starts, applying the SizeX variable. The specific body hitbox can be changed ('''refer to this link''').
* RHandEndX is the frame where the collision hitbox ends, applying the SizeDeltaX variable.

== Camera ==
This element deals with the player’s camera when doing certain attacks. These values were taken from Sho-Hog-Ken (SHAS).

* StartEaseInFrame/StartEaseOutFrame are used to set the range of when the camera eases in and out.
* EaseIn/EaseOut is the value that the camera pulls in or pulls out.
* Fovy probably means FOV (field of view). The Y could be a type or mean the Y-Axis.
* HopeLength… your guess is as good as mine.
* Height is self-explanatory.

== Vibration ==
This element deals with the controller’s vibration, usually when a hit is registered.

* Start/EndFrame are self-explanatory
* BigMoter and SmallMoter are the vibration motors of the control, meaning left or right.
* SuccessTimeLength is how long the vibration lasts if you land a hit
* SuccessBig/SmallMoter is the same thing but for the motors specifically.

== Attack ==
These are the primary Attack values, which we know are connected to the Collision (thanks to Nec0Arc). Let’s take a look at the Attack Variables, which are the final variables you’ll need to complete your Motion:

* Type is one of many different Attack Types that you can use.
* DamagePower is self-explanatory, and its value is multiplied by the Strength Stat
* KnockOutPower_Y determines the vertical knockback distance for enemies
* KnockOutPower_Dir determines the horizontal knockback distance for enemies (I should note, for both, that it weirdly isn’t alterable when doing)
* KnockOutAnglePowerRatio is just a multiplier for both KnockOutPower variables.
* The Attribute variable can be set to Vertical, Side, or FinishAttack.

Creating & Customizing Attack Motions (Unique Inputs)

2026-04-01T15:37:42Z

King Galactix:

The '''MotionList''' contains a series of '''Motions''', or the '''Unique Inputs (UIs)''' in the Werehog’s combos. These Motion are XML cells which determine the value of the animation, movement, collision, attack types, and other attributes of each and every unique input of the Werehog's attacks. These elements are extensively long because of their content, so we will break each section down for you. For convenience's sake, we will create a new scenario by making a new Motion (individual attack) called “MOVE_A” and explain what each variable does.{{Notice|type=note|content=You will need the following files from the #Application archive file:
* EvilAttackAction1.xml
* EvilAttackMotionFile.xml}}

By the end of this guide, you'll have a fairly comprehensive and complete Motion file, such as the example below:<syntaxhighlight lang="xml" line="1" start="125"><Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>
<MotionMoveSpeedRatio>0.875f</MotionMoveSpeedRatio>
<MotionMoveSpeedRatio_Y>1.f</MotionMoveSpeedRatio_Y>
<MotionMoveSpeedRatioFrameStart_1>-1</MotionMoveSpeedRatioFrameStart_1>
<MotionMoveSpeedRatioFrame_1>10.f</MotionMoveSpeedRatioFrame_1>
<MotionMoveSpeedRatioFrameY_1>10.f</MotionMoveSpeedRatioFrameY_1>
<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
<DontCatchTime>0</DontCatchTime>
<DontJump>false</DontJump>
<ShakeCameraStartFrame>-1</ShakeCameraStartFrame>
<GroundHeightRepair>0.1f</GroundHeightRepair>
<MoveType>IngAutoTarget</MoveType>
<AutoTargetEndFrame>9</AutoTargetEndFrame>
<AutoTargetPower>0.2</AutoTargetPower>
<PadRotationIntensity>20</PadRotationIntensity>
<IsGravity>true</IsGravity>
<GravityArray_Start1>-1</GravityArray_Start1>
<IsGravityArray1>true</IsGravityArray1>
<PadRotationIntensity_Start1>0</PadRotationIntensity_Start1>
<PadRotationIntensity_Power1>20</PadRotationIntensity_Power1>
<PadRotationValid1>true</PadRotationValid1>
<PadRotationIntensity_Start2>8</PadRotationIntensity_Start2>
<PadRotationIntensity_Power2>0</PadRotationIntensity_Power2>
<PadRotationValid2>false</PadRotationValid2>
<PadRotationIntensity_Start3>22</PadRotationIntensity_Start3>
<PadRotationIntensity_Power3>20</PadRotationIntensity_Power3>
<PadRotationValid3>true</PadRotationValid3>
<GameSpeed_Start1>0</GameSpeed_Start1>
<GameSpeed_Power1>1</GameSpeed_Power1>
<GameSpeed_CollPower1>1</GameSpeed_CollPower1>
<GuardStartFrame>8</GuardStartFrame>
<GuardEndFrame>27</GuardEndFrame>

<Effect>
<REffect_Start1>4</REffect_Start1>
<REffect_End1>16</REffect_End1>
<REffect_Size1>2</REffect_Size1>
<REffect_Name1>evil_punch_01</REffect_Name1>
</Effect>
<Sound></Sound>
<Collision>
<DebugDraw>true</DebugDraw>
<Size1>0.75f</Size1>
<SizeDelta1>0.f</SizeDelta1>
<RHandStart1>6</RHandStart1>
<RHandEnd1>16</RHandEnd1>
</Collision>
<Vibration>
<StartFrame>-1</StartFrame>
<EndFrame>-1</EndFrame>
<BigMoter>0.f</BigMoter>
<SmallMoter>0.f</SmallMoter>
<SuccessTimeLength>0.01</SuccessTimeLength>
<SuccessBigMoter>0.5f</SuccessBigMoter>
<SuccessSmallMoter>0.5f</SuccessSmallMoter>
</Vibration>
<Attack>
<Type1>NormalHard</Type1>
<DamagePower1>95</DamagePower1>
<KnockOutPower_Y1>0.f</KnockOutPower_Y1>
<KnockOutPower_Dir1>2.2f</KnockOutPower_Dir1>
<KnockOutAnglePowerRatio1>0.5f</KnockOutAnglePowerRatio1>
<Attribute1>VerticalAttack</Attribute1>
</Attack>
</Motion></syntaxhighlight>
== Names ==
We start with the '''MotionName''' and '''FileName'''. The MotionName can be whatever it wants, but the FileName must be exactly as it’s written within EvilAttackMotionFile.xml<syntaxhighlight lang="xml">
<Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
</Motion>
</syntaxhighlight>For the most part, changing the filename is an entirely arbitrary case. But if you’re planning to change the filename anyways:

# Find the name of your animation file (formatted as *.anm.hkx)
# Look for EvilAttackMotionFile.xml, and look within that XML
# You can either change the filename or make a new MotionFileList. However, there are some limitations… so this is an arbitrary action unless you’re using the Beta Combos.
<syntaxhighlight lang="xml" line="1" start="1">
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<Start>
<StartPoint>

<MotionFileList>
<MotionName>NSA</MotionName>
<FileName>evilsonic_attackNSA</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSB</MotionName>
<FileName>evilsonic_attackNSB</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSC</MotionName>
<FileName>evilsonic_attackNSC</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSD</MotionName>
<FileName>evilsonic_attackNSD</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSE</MotionName>
<FileName>evilsonic_attackNSE</FileName>
</MotionFileList>


<MotionFileList>
<MotionName>MOVE_A</MotionName>
<FileName>evilsonic_attackNSE</FileName>
</MotionFileList>
</Start>
</StartPoint>
</syntaxhighlight>

== Animation and Movement ==
The animation and movement values here determine how your Motion looks and moves visually and physically.

* '''MotionBlendTimeS''', '''MotionBlendTimeE''', and '''MotionBlendTimeEIdle''' blend the animations between a previous and following combo. Keep the values as 0.02f.
* '''MotionMoveSpeedRatio''' (MMSR for convenience) and '''MotionMoveSpeedRatio_Y''' control the player’s movement ratio when making the entire attack. You can experiment with these values, but remember to write it in the form of “A.Bf”
* '''MotionMoveSpeedRatioFrameStart_N,''' '''MotionMoveSpeedRatioFrame_N,''' and '''MotionMoveSpeedRatioFrameY_N''' apply the same movement/distance ratio, except it’s done within a certain frame. Reference other moves if you want to make an attack move more or less in a certain direction.
** For example: moves that rise up at a certain frame, such as a launcher, should multiply MotionMoveSpeedRatioFrameY_N by a significant amount, more than MotionMoveSpeedRatioFrame_N.
* '''MotionFirstSpeed''', '''MiddleSpeed''', and '''EndSpeed''' all affect the Attack’s animation speed.
* '''MotionSpeed_First'''/'''MiddleFrame''' represents when the MotionFirstSpeed and MiddleSpeed params are executed (corresponding with the animation frames).
<syntaxhighlight lang="xml" line="1">
<Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>
<MotionMoveSpeedRatio>0.875f</MotionMoveSpeedRatio>
<MotionMoveSpeedRatio_Y>1.f</MotionMoveSpeedRatio_Y>
<MotionMoveSpeedRatioFrameStart_1>-1</MotionMoveSpeedRatioFrameStart_1>
<MotionMoveSpeedRatioFrame_1>10.f</MotionMoveSpeedRatioFrame_1>
<MotionMoveSpeedRatioFrameY_1>10.f</MotionMoveSpeedRatioFrameY_1>
<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
</Motion>
</syntaxhighlight>

== General ==
Now we can take a look at more general variables. These are equally important for combat and visual aspects of the Werehog.

* '''AttackScope''' sets the maximum scope of turning while attacking. You have None, Scope90, and Scope360 to use, which only work with enabled PadRotation variables (more in the Gravity/PadRotation section).
* '''DontCatchTime''' states how long it takes before the player can use the grab. Set it to 0 for ground moves, 2 for aerial moves.
* '''DontJump''' is self-explanatory. You apply it for whatever moves you DON'T want to have an enabled jump afterwards, such as Sho-Hog-Ken (YYA), and disable it for combo that you want to jump with, such as Unleashed Wild Combo (XX-YY-XX-YY).
* '''OnceSendDamage''' determines how long a combo can continually send damage. The default value is usually zero, and many moves use this as a way of implementing multiple hits for combos with a single or more number of hitboxes.
* '''ShakeCameraStartFrame''' is the start frame for when the Camera Shake can happen for certain moves. Unfortunately, there are no specific variables to affect the number or intensity of shakes.
* '''GroundHeightRepair''' determines the floatiness of a move. Lower values mean more floaty and higher values mean less floaty.
* '''MoveType''' has two values: Default and IngAutoTarget (the variables below only work when IngAutoTarget is enabled.
* '''AutoTargetEndFrame''' can be set to 0 for Default, and any value for IngAutoTarget
* '''AutoTargetPower''' can be set to 0 for Default, and any value for IngAutoTarget
<syntaxhighlight lang="xml">
<Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>
<MotionMoveSpeedRatio>0.875f</MotionMoveSpeedRatio>
<MotionMoveSpeedRatio_Y>1.f</MotionMoveSpeedRatio_Y>
<MotionMoveSpeedRatioFrameStart_1>-1</MotionMoveSpeedRatioFrameStart_1>
<MotionMoveSpeedRatioFrame_1>10.f</MotionMoveSpeedRatioFrame_1>
<MotionMoveSpeedRatioFrameY_1>10.f</MotionMoveSpeedRatioFrameY_1>
<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
<DontCatchTime>0</DontCatchTime>
<DontJump>false</DontJump>
<OnceSendDamage>0</OnceSendDamage> 
<ShakeCameraStartFrame>-1</ShakeCameraStartFrame>
<GroundHeightRepair>0.1f</GroundHeightRepair>
<MoveType>IngAutoTarget</MoveType>
<AutoTargetEndFrame>9</AutoTargetEndFrame>
<AutoTargetPower>0.2</AutoTargetPower>
</Motion>
</syntaxhighlight>

== Gravity and PadRotation ==
The following Gravity and PadRotation variables are interpreted and explained by Nec0Arc and myself, so you can understand how to adjust the player’s movement across the X, Y, and Z axis. The value of these variables depend on what kind of attack you would want (grounded, launcher, aerial, unidirectional, multidirectional, etc.)

* PadRotationIntensity is a general value that of the attack's rotation via the left stick. It is assumed the value is represented in degrees or whatever value is used by the controller's left-stick.
* '''IsGravity''' and its subsequent parameters, '''GravityArray_StartX''' and '''IsGravityArrayX''' determines the combos's application of gravity while doing a combo. IsGravity and IsGravityX use true/false.
** Ground moves follow the setup below for its gravity arrays and values.
** Launcher moves follow the setup below for its gravity arrays and values.
** Aerial moves follow the setup below for its gravity arrays and values:
* PadRotationIntensity_StartX sets the keyframe for the player’s movement during an attack.
* PadRotationIntensity_PowerX sets the degrees of rotation your player can move.
* PadRotationValidX just sets the value to true or false.

== GameSpeed and Guarding ==
The following discoveries were made by BaconYum and myself: GameSpeed represents the “Slow Motion” moments that happen with attacks, so let’s look at the variables:

* GameSpeed_StartX refers to the specific frame that starts the GameSpeed variable.
* GameSpeed_PowerX refers to the power of this GameSpeed modifier, which is simple to understand.
** A value of 1 means the game’s speed is normal
** 1 > X > 0 means the game’s speed is slowed. So if you have a value of 0.5, the game’s speed is halved.
** A value above 1 means the game’s speed is multiplied by that amount. A value of 2 means the game’s speed is doubled.
* GameSpeed_CollPowerX does the same thing, except it refers to the player’s collision when doing the attack.
* GuardStart/EndFrame are self-explanatory, and they surprisingly explain the mechanic of Shield Cancelling… neat!

== Sound and Effects ==
The Sound element is unused in the main game’s Attack XML, mostly used in the TBRES XMLs. The Effect element, however, can be used generally for hand and feet attacks.

* Effect_StartX is the start time value for the effect to take place. L/R is for hands, LF/RF is for feet.
* Effect_EndX is the end time value for the effect to take place.
* Effect_SizeX is self explanatory
* Effect_NameX is also self-explanatory. If you want to look for the effect names for the Werehog, look at EvilSonic’s ar files.

== Collision ==
The Collision Element deals with the attack’s hitbox, which registers the hits and damage. Both Nec0Arc and NextinFRFX interpreted and discovered the following variables to help you understand what they do:

* Just keep it as true. I don’t know what it does.
* SizeX is the initial or start size of the attack’s hitbox.
* SizeDeltaX is the final or end size of the attack’s hitbox
* RHandStartX is the frame where the collision hitbox starts, applying the SizeX variable. The specific body hitbox can be changed ('''refer to this link''').
* RHandEndX is the frame where the collision hitbox ends, applying the SizeDeltaX variable.

== Camera ==
This element deals with the player’s camera when doing certain attacks. These values were taken from Sho-Hog-Ken (SHAS).

* StartEaseInFrame/StartEaseOutFrame are used to set the range of when the camera eases in and out.
* EaseIn/EaseOut is the value that the camera pulls in or pulls out.
* Fovy probably means FOV (field of view). The Y could be a type or mean the Y-Axis.
* HopeLength… your guess is as good as mine.
* Height is self-explanatory.

== Vibration ==
This element deals with the controller’s vibration, usually when a hit is registered.

* Start/EndFrame are self-explanatory
* BigMoter and SmallMoter are the vibration motors of the control, meaning left or right.
* SuccessTimeLength is how long the vibration lasts if you land a hit
* SuccessBig/SmallMoter is the same thing but for the motors specifically.

== Attack ==
These are the primary Attack values, which we know are connected to the Collision (thanks to Nec0Arc). Let’s take a look at the Attack Variables, which are the final variables you’ll need to complete your Motion:

* Type is one of many different Attack Types that you can use.
* DamagePower is self-explanatory, and its value is multiplied by the Strength Stat
* KnockOutPower_Y determines the vertical knockback distance for enemies
* KnockOutPower_Dir determines the horizontal knockback distance for enemies (I should note, for both, that it weirdly isn’t alterable when doing)
* KnockOutAnglePowerRatio is just a multiplier for both KnockOutPower variables.
* The Attribute variable can be set to Vertical, Side, or FinishAttack.

Creating & Customizing Attack Actions (Combo Routes)

2026-03-30T14:47:19Z

King Galactix:

Creating & Customizing Attack Actions (Combo Routes)

2026-03-30T14:39:54Z

King Galactix:

Creating & Customizing Attack Actions (Combo Routes)

2026-03-30T14:39:26Z

King Galactix: Created page with "The ActionList is a compilation of different ‘Actions’. Actions work together like a family tree, with individual attacks being stems and their connections being branches. All combos are just multiple branches of other moves, spawning a wide range of moveset paths. Here’s an example: {{Notice|type=example|content=NSA > NSB > NSC > NSD > NSE (YYYY-Y) = Feral/Normal Were-Hammer NSA > JF > JKC (Y-XX) = Double Kick Combo NSA > NSB > SC > SC2 > SD (YY-XXX) = Donkey K..."

Creating & Customizing Attack Motions (Unique Inputs)

2026-03-30T14:31:37Z

King Galactix:

{{Notice|type=note|content=You will need the following files from the #Application archive file:
* EvilAttackAction1.xml
* EvilAttackMotionFile.xml}}

The '''MotionList''' contains a series of '''Motions''', or the '''Unique Inputs (UIs)''' in the Werehog’s combos. These Motion are XML cells which determine the value of the animation, movement, collision, attack types, and other attributes of each and every unique input of the Werehog's attacks. These elements are extensively long because of their content, so we will break each section down for you. For convenience's sake, we will create a new scenario by making a new Motion (individual attack) called “MOVE_A” and explain what each variable does.

By the end of this guide, you'll have a fairly comprehensive and complete Motion file, such as the example below.<syntaxhighlight lang="xml" line="1" start="125"><Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>
<MotionMoveSpeedRatio>0.875f</MotionMoveSpeedRatio>
<MotionMoveSpeedRatio_Y>1.f</MotionMoveSpeedRatio_Y>
<MotionMoveSpeedRatioFrameStart_1>-1</MotionMoveSpeedRatioFrameStart_1>
<MotionMoveSpeedRatioFrame_1>10.f</MotionMoveSpeedRatioFrame_1>
<MotionMoveSpeedRatioFrameY_1>10.f</MotionMoveSpeedRatioFrameY_1>
<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
<DontCatchTime>0</DontCatchTime>
<DontJump>false</DontJump>
<ShakeCameraStartFrame>-1</ShakeCameraStartFrame>
<GroundHeightRepair>0.1f</GroundHeightRepair>
<MoveType>IngAutoTarget</MoveType>
<AutoTargetEndFrame>9</AutoTargetEndFrame>
<AutoTargetPower>0.2</AutoTargetPower>
<PadRotationIntensity>20</PadRotationIntensity>
<IsGravity>true</IsGravity>
<GravityArray_Start1>-1</GravityArray_Start1>
<IsGravityArray1>true</IsGravityArray1>
<PadRotationIntensity_Start1>0</PadRotationIntensity_Start1>
<PadRotationIntensity_Power1>20</PadRotationIntensity_Power1>
<PadRotationValid1>true</PadRotationValid1>
<PadRotationIntensity_Start2>8</PadRotationIntensity_Start2>
<PadRotationIntensity_Power2>0</PadRotationIntensity_Power2>
<PadRotationValid2>false</PadRotationValid2>
<PadRotationIntensity_Start3>22</PadRotationIntensity_Start3>
<PadRotationIntensity_Power3>20</PadRotationIntensity_Power3>
<PadRotationValid3>true</PadRotationValid3>
<GameSpeed_Start1>0</GameSpeed_Start1>
<GameSpeed_Power1>1</GameSpeed_Power1>
<GameSpeed_CollPower1>1</GameSpeed_CollPower1>
<GuardStartFrame>8</GuardStartFrame>
<GuardEndFrame>27</GuardEndFrame>

<Effect>
<REffect_Start1>4</REffect_Start1>
<REffect_End1>16</REffect_End1>
<REffect_Size1>2</REffect_Size1>
<REffect_Name1>evil_punch_01</REffect_Name1>
</Effect>
<Sound></Sound>
<Collision>
<DebugDraw>true</DebugDraw>
<Size1>0.75f</Size1>
<SizeDelta1>0.f</SizeDelta1>
<RHandStart1>6</RHandStart1>
<RHandEnd1>16</RHandEnd1>
</Collision>
<Vibration>
<StartFrame>-1</StartFrame>
<EndFrame>-1</EndFrame>
<BigMoter>0.f</BigMoter>
<SmallMoter>0.f</SmallMoter>
<SuccessTimeLength>0.01</SuccessTimeLength>
<SuccessBigMoter>0.5f</SuccessBigMoter>
<SuccessSmallMoter>0.5f</SuccessSmallMoter>
</Vibration>
<Attack>
<Type1>NormalHard</Type1>
<DamagePower1>95</DamagePower1>
<KnockOutPower_Y1>0.f</KnockOutPower_Y1>
<KnockOutPower_Dir1>2.2f</KnockOutPower_Dir1>
<KnockOutAnglePowerRatio1>0.5f</KnockOutAnglePowerRatio1>
<Attribute1>VerticalAttack</Attribute1>
</Attack>
</Motion></syntaxhighlight>
== Names ==
We start with the '''MotionName''' and '''FileName'''. The MotionName can be whatever it wants, but the FileName must be exactly as it’s written within EvilAttackMotionFile.xml<syntaxhighlight lang="xml">
<Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
</Motion>
</syntaxhighlight>For the most part, changing the filename is an entirely arbitrary case. But if you’re planning to change the filename anyways:

# Find the name of your animation file (formatted as *.anm.hkx)
# Look for EvilAttackMotionFile.xml, and look within that XML
# You can either change the filename or make a new MotionFileList. However, there are some limitations… so this is an arbitrary action unless you’re using the Beta Combos.
<syntaxhighlight lang="xml" line="1" start="1">
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<Start>
<StartPoint>

<MotionFileList>
<MotionName>NSA</MotionName>
<FileName>evilsonic_attackNSA</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSB</MotionName>
<FileName>evilsonic_attackNSB</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSC</MotionName>
<FileName>evilsonic_attackNSC</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSD</MotionName>
<FileName>evilsonic_attackNSD</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSE</MotionName>
<FileName>evilsonic_attackNSE</FileName>
</MotionFileList>


<MotionFileList>
<MotionName>MOVE_A</MotionName>
<FileName>evilsonic_attackNSE</FileName>
</MotionFileList>
</Start>
</StartPoint>
</syntaxhighlight>

== Animation and Movement ==
The animation and movement values here determine how your Motion looks and moves visually and physically.

* '''MotionBlendTimeS''', '''MotionBlendTimeE''', and '''MotionBlendTimeEIdle''' blend the animations between a previous and following combo. Keep the values as 0.02f.
* '''MotionMoveSpeedRatio''' (MMSR for convenience) and '''MotionMoveSpeedRatio_Y''' control the player’s movement ratio when making the entire attack. You can experiment with these values, but remember to write it in the form of “A.Bf”
* '''MotionMoveSpeedRatioFrameStart_N,''' '''MotionMoveSpeedRatioFrame_N,''' and '''MotionMoveSpeedRatioFrameY_N''' apply the same movement/distance ratio, except it’s done within a certain frame. Reference other moves if you want to make an attack move more or less in a certain direction.
** For example: moves that rise up at a certain frame, such as a launcher, should multiply MotionMoveSpeedRatioFrameY_N by a significant amount, more than MotionMoveSpeedRatioFrame_N.
* '''MotionFirstSpeed''', '''MiddleSpeed''', and '''EndSpeed''' all affect the Attack’s animation speed.
* '''MotionSpeed_First'''/'''MiddleFrame''' represents when the MotionFirstSpeed and MiddleSpeed params are executed (corresponding with the animation frames).
<syntaxhighlight lang="xml" line="1">
<Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>
<MotionMoveSpeedRatio>0.875f</MotionMoveSpeedRatio>
<MotionMoveSpeedRatio_Y>1.f</MotionMoveSpeedRatio_Y>
<MotionMoveSpeedRatioFrameStart_1>-1</MotionMoveSpeedRatioFrameStart_1>
<MotionMoveSpeedRatioFrame_1>10.f</MotionMoveSpeedRatioFrame_1>
<MotionMoveSpeedRatioFrameY_1>10.f</MotionMoveSpeedRatioFrameY_1>
<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
</Motion>
</syntaxhighlight>

== General ==
Now we can take a look at more general variables. These are equally important for combat and visual aspects of the Werehog.

* '''AttackScope''' sets the maximum scope of turning while attacking. You have None, Scope90, and Scope360 to use, which only work with enabled PadRotation variables (more in the Gravity/PadRotation section).
* '''DontCatchTime''' states how long it takes before the player can use the grab. Set it to 0 for ground moves, 2 for aerial moves.
* '''DontJump''' is self-explanatory. You apply it for whatever moves you DON'T want to have an enabled jump afterwards, such as Sho-Hog-Ken (YYA), and disable it for combo that you want to jump with, such as Unleashed Wild Combo (XX-YY-XX-YY).
* '''OnceSendDamage''' determines how long a combo can continually send damage. The default value is usually zero, and many moves use this as a way of implementing multiple hits for combos with a single or more number of hitboxes.
* '''ShakeCameraStartFrame''' is the start frame for when the Camera Shake can happen for certain moves. Unfortunately, there are no specific variables to affect the number or intensity of shakes.
* '''GroundHeightRepair''' determines the floatiness of a move. Lower values mean more floaty and higher values mean less floaty.
* '''MoveType''' has two values: Default and IngAutoTarget (the variables below only work when IngAutoTarget is enabled.
* '''AutoTargetEndFrame''' can be set to 0 for Default, and any value for IngAutoTarget
* '''AutoTargetPower''' can be set to 0 for Default, and any value for IngAutoTarget
<syntaxhighlight lang="xml">
<Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>
<MotionMoveSpeedRatio>0.875f</MotionMoveSpeedRatio>
<MotionMoveSpeedRatio_Y>1.f</MotionMoveSpeedRatio_Y>
<MotionMoveSpeedRatioFrameStart_1>-1</MotionMoveSpeedRatioFrameStart_1>
<MotionMoveSpeedRatioFrame_1>10.f</MotionMoveSpeedRatioFrame_1>
<MotionMoveSpeedRatioFrameY_1>10.f</MotionMoveSpeedRatioFrameY_1>
<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
<DontCatchTime>0</DontCatchTime>
<DontJump>false</DontJump>
<OnceSendDamage>0</OnceSendDamage> 
<ShakeCameraStartFrame>-1</ShakeCameraStartFrame>
<GroundHeightRepair>0.1f</GroundHeightRepair>
<MoveType>IngAutoTarget</MoveType>
<AutoTargetEndFrame>9</AutoTargetEndFrame>
<AutoTargetPower>0.2</AutoTargetPower>
</Motion>
</syntaxhighlight>

== Gravity and PadRotation ==
The following Gravity and PadRotation variables are interpreted and explained by Nec0Arc and myself, so you can understand how to adjust the player’s movement across the X, Y, and Z axis. The value of these variables depend on what kind of attack you would want (grounded, launcher, aerial, unidirectional, multidirectional, etc.)

* PadRotationIntensity is a general value that of the attack's rotation via the left stick. It is assumed the value is represented in degrees or whatever value is used by the controller's left-stick.
* '''IsGravity''' and its subsequent parameters, '''GravityArray_StartX''' and '''IsGravityArrayX''' determines the combos's application of gravity while doing a combo. IsGravity and IsGravityX use true/false.
** Ground moves follow the setup below for its gravity arrays and values.
** Launcher moves follow the setup below for its gravity arrays and values.
** Aerial moves follow the setup below for its gravity arrays and values:
* PadRotationIntensity_StartX sets the keyframe for the player’s movement during an attack.
* PadRotationIntensity_PowerX sets the degrees of rotation your player can move.
* PadRotationValidX just sets the value to true or false.

== GameSpeed and Guarding ==
The following discoveries were made by BaconYum and myself: GameSpeed represents the “Slow Motion” moments that happen with attacks, so let’s look at the variables:

* GameSpeed_StartX refers to the specific frame that starts the GameSpeed variable.
* GameSpeed_PowerX refers to the power of this GameSpeed modifier, which is simple to understand.
** A value of 1 means the game’s speed is normal
** 1 > X > 0 means the game’s speed is slowed. So if you have a value of 0.5, the game’s speed is halved.
** A value above 1 means the game’s speed is multiplied by that amount. A value of 2 means the game’s speed is doubled.
* GameSpeed_CollPowerX does the same thing, except it refers to the player’s collision when doing the attack.
* GuardStart/EndFrame are self-explanatory, and they surprisingly explain the mechanic of Shield Cancelling… neat!

== Sound and Effects ==
The Sound element is unused in the main game’s Attack XML, mostly used in the TBRES XMLs. The Effect element, however, can be used generally for hand and feet attacks.

* Effect_StartX is the start time value for the effect to take place. L/R is for hands, LF/RF is for feet.
* Effect_EndX is the end time value for the effect to take place.
* Effect_SizeX is self explanatory
* Effect_NameX is also self-explanatory. If you want to look for the effect names for the Werehog, look at EvilSonic’s ar files.

== Collision ==
The Collision Element deals with the attack’s hitbox, which registers the hits and damage. Both Nec0Arc and NextinFRFX interpreted and discovered the following variables to help you understand what they do:

* Just keep it as true. I don’t know what it does.
* SizeX is the initial or start size of the attack’s hitbox.
* SizeDeltaX is the final or end size of the attack’s hitbox
* RHandStartX is the frame where the collision hitbox starts, applying the SizeX variable. The specific body hitbox can be changed ('''refer to this link''').
* RHandEndX is the frame where the collision hitbox ends, applying the SizeDeltaX variable.

== Camera ==
This element deals with the player’s camera when doing certain attacks. These values were taken from Sho-Hog-Ken (SHAS).

* StartEaseInFrame/StartEaseOutFrame are used to set the range of when the camera eases in and out.
* EaseIn/EaseOut is the value that the camera pulls in or pulls out.
* Fovy probably means FOV (field of view). The Y could be a type or mean the Y-Axis.
* HopeLength… your guess is as good as mine.
* Height is self-explanatory.

== Vibration ==
This element deals with the controller’s vibration, usually when a hit is registered.

* Start/EndFrame are self-explanatory
* BigMoter and SmallMoter are the vibration motors of the control, meaning left or right.
* SuccessTimeLength is how long the vibration lasts if you land a hit
* SuccessBig/SmallMoter is the same thing but for the motors specifically.

== Attack ==
These are the primary Attack values, which we know are connected to the Collision (thanks to Nec0Arc). Let’s take a look at the Attack Variables, which are the final variables you’ll need to complete your Motion:

* Type is one of many different Attack Types that you can use.
* DamagePower is self-explanatory, and its value is multiplied by the Strength Stat
* KnockOutPower_Y determines the vertical knockback distance for enemies
* KnockOutPower_Dir determines the horizontal knockback distance for enemies (I should note, for both, that it weirdly isn’t alterable when doing)
* KnockOutAnglePowerRatio is just a multiplier for both KnockOutPower variables.
* The Attribute variable can be set to Vertical, Side, or FinishAttack.

Creating & Customizing Attack Motions (Unique Inputs)

2026-03-28T17:28:14Z

King Galactix:

{{Notice|type=note|content=You will need the following files from the #Application archive file:
* EvilAttackAction1.xml
* EvilAttackMotionFile.xml}}

The '''MotionList''' contains a series of '''Motions''', or the '''Unique Inputs (UIs)''' in the Werehog’s combos. These Motion are XML cells which determine the value of the animation, movement, collision, attack types, and other attributes of each and every unique input of the Werehog's attacks. These elements are extensively long because of their content, so we will break each section down for you. For convenience's sake, we will create a new scenario by making a new Motion (individual attack) called “MOVE_A” and explain what each variable does.

By the end of this guide, you'll have a fairly comprehensive and complete Motion file, such as the example below.<syntaxhighlight lang="xml" line="1" start="125"><Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>
<MotionMoveSpeedRatio>0.875f</MotionMoveSpeedRatio>
<MotionMoveSpeedRatio_Y>1.f</MotionMoveSpeedRatio_Y>
<MotionMoveSpeedRatioFrameStart_1>-1</MotionMoveSpeedRatioFrameStart_1>
<MotionMoveSpeedRatioFrame_1>10.f</MotionMoveSpeedRatioFrame_1>
<MotionMoveSpeedRatioFrameY_1>10.f</MotionMoveSpeedRatioFrameY_1>
<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
<DontCatchTime>0</DontCatchTime>
<DontJump>false</DontJump>
<ShakeCameraStartFrame>-1</ShakeCameraStartFrame>
<GroundHeightRepair>0.1f</GroundHeightRepair>
<MoveType>IngAutoTarget</MoveType>
<AutoTargetEndFrame>9</AutoTargetEndFrame>
<AutoTargetPower>0.2</AutoTargetPower>
<PadRotationIntensity>20</PadRotationIntensity>
<IsGravity>true</IsGravity>
<GravityArray_Start1>-1</GravityArray_Start1>
<IsGravityArray1>true</IsGravityArray1>
<PadRotationIntensity_Start1>0</PadRotationIntensity_Start1>
<PadRotationIntensity_Power1>20</PadRotationIntensity_Power1>
<PadRotationValid1>true</PadRotationValid1>
<PadRotationIntensity_Start2>8</PadRotationIntensity_Start2>
<PadRotationIntensity_Power2>0</PadRotationIntensity_Power2>
<PadRotationValid2>false</PadRotationValid2>
<PadRotationIntensity_Start3>22</PadRotationIntensity_Start3>
<PadRotationIntensity_Power3>20</PadRotationIntensity_Power3>
<PadRotationValid3>true</PadRotationValid3>
<GameSpeed_Start1>0</GameSpeed_Start1>
<GameSpeed_Power1>1</GameSpeed_Power1>
<GameSpeed_CollPower1>1</GameSpeed_CollPower1>
<GuardStartFrame>8</GuardStartFrame>
<GuardEndFrame>27</GuardEndFrame>

<Effect>
<REffect_Start1>4</REffect_Start1>
<REffect_End1>16</REffect_End1>
<REffect_Size1>2</REffect_Size1>
<REffect_Name1>evil_punch_01</REffect_Name1>
</Effect>
<Sound></Sound>
<Collision>
<DebugDraw>true</DebugDraw>
<Size1>0.75f</Size1>
<SizeDelta1>0.f</SizeDelta1>
<RHandStart1>6</RHandStart1>
<RHandEnd1>16</RHandEnd1>
</Collision>
<Vibration>
<StartFrame>-1</StartFrame>
<EndFrame>-1</EndFrame>
<BigMoter>0.f</BigMoter>
<SmallMoter>0.f</SmallMoter>
<SuccessTimeLength>0.01</SuccessTimeLength>
<SuccessBigMoter>0.5f</SuccessBigMoter>
<SuccessSmallMoter>0.5f</SuccessSmallMoter>
</Vibration>
<Attack>
<Type1>NormalHard</Type1>
<DamagePower1>95</DamagePower1>
<KnockOutPower_Y1>0.f</KnockOutPower_Y1>
<KnockOutPower_Dir1>2.2f</KnockOutPower_Dir1>
<KnockOutAnglePowerRatio1>0.5f</KnockOutAnglePowerRatio1>
<Attribute1>VerticalAttack</Attribute1>
</Attack>
</Motion></syntaxhighlight>
== Names ==
We start with the '''MotionName''' and '''FileName'''. The MotionName can be whatever it wants, but the FileName must be exactly as it’s written within EvilAttackMotionFile.xml<syntaxhighlight lang="xml">
<Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
</Motion>
</syntaxhighlight>For the most part, changing the filename is an entirely arbitrary case. But if you’re planning to change the filename anyways:

# Find the name of your animation file (formatted as *.anm.hkx)
# Look for EvilAttackMotionFile.xml, and look within that XML
# You can either change the filename or make a new MotionFileList. However, there are some limitations… so this is an arbitrary action unless you’re using the Beta Combos.
<syntaxhighlight lang="xml" line="1" start="1">
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<Start>
<StartPoint>

<MotionFileList>
<MotionName>NSA</MotionName>
<FileName>evilsonic_attackNSA</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSB</MotionName>
<FileName>evilsonic_attackNSB</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSC</MotionName>
<FileName>evilsonic_attackNSC</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSD</MotionName>
<FileName>evilsonic_attackNSD</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSE</MotionName>
<FileName>evilsonic_attackNSE</FileName>
</MotionFileList>


<MotionFileList>
<MotionName>MOVE_A</MotionName>
<FileName>evilsonic_attackNSE</FileName>
</MotionFileList>
</Start>
</StartPoint>
</syntaxhighlight>

== Animation and Movement ==
The animation and movement values here determine how your Motion looks and moves visually and physically.

* '''MotionBlendTimeS''', '''MotionBlendTimeE''', and '''MotionBlendTimeEIdle''' blend the animations between a previous and following combo. Keep the values as 0.02f.
* '''MotionMoveSpeedRatio''' (MMSR for convenience) and '''MotionMoveSpeedRatio_Y''' control the player’s movement ratio when making the entire attack. You can experiment with these values, but remember to write it in the form of “A.Bf”
* '''MotionMoveSpeedRatioFrameStart_X,''' '''MotionMoveSpeedRatioFrame_X, and MotionMoveSpeedRatioFrameY_X'''and its subsequent variables apply the same movement/distance ratio, except it’s done within a certain frame. Reference other moves if you want to make particular adjustments.
* '''MotionFirstSpeed''', '''MiddleSpeed''', and '''EndSpeed''' all affect the Attack’s animation speed.
* '''MotionSpeed_First'''/'''MiddleFrame''' represents when the MotionFirstSpeed and MiddleSpeed params are executed (corresponding with the animation frames).
<syntaxhighlight lang="xml" line="1">
<Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>
<MotionMoveSpeedRatio>0.875f</MotionMoveSpeedRatio>
<MotionMoveSpeedRatio_Y>1.f</MotionMoveSpeedRatio_Y>
<MotionMoveSpeedRatioFrameStart_1>-1</MotionMoveSpeedRatioFrameStart_1>
<MotionMoveSpeedRatioFrame_1>10.f</MotionMoveSpeedRatioFrame_1>
<MotionMoveSpeedRatioFrameY_1>10.f</MotionMoveSpeedRatioFrameY_1>
<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
</Motion>
</syntaxhighlight>

== General ==
Now we can take a look at more general variables. These are equally important for combat and visual aspects of the Werehog.

* '''AttackScope''' sets the degrees of turning while attacking. You have None, Scope90, and Scope360 to use.
* '''DontCatchTime''' states how long it takes before the player can use the grab. Set it to 0 for ground moves, 2 for aerial moves.
* '''DontJump''' is self-explanatory. You apply it for whatever moves you DON'T want to have an enabled jump afterwards, such as Sho-Hog-Ken (YYA), and disable it for combo that you want to jump with, such as Unleashed Wild Combo (XX-YY-XX-YY).
* '''OnceSendDamage''' determines how long a combo can continually send damage. The default value is usually zero, and many moves use this as a way of implementing multiple hits for combos with a single or more number of hitboxes.
* '''ShakeCameraStartFrame''' is the start frame for when the Camera Shake can happen for certain moves. Unfortunately, there are no specific variables to affect the number or intensity of shakes.
* '''GroundHeightRepair''' determines the floatiness of a move. Lower values mean more floaty and higher values mean less floaty.
* '''MoveType''' has two values: Default and IngAutoTarget (the variables below only work when IngAutoTarget is enabled.
* '''AutoTargetEndFrame''' can be set to 0 for Default, and any value for IngAutoTarget
* '''AutoTargetPower''' can be set to 0 for Default, and any value for IngAutoTarget
<syntaxhighlight lang="xml">
<Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>
<MotionMoveSpeedRatio>0.875f</MotionMoveSpeedRatio>
<MotionMoveSpeedRatio_Y>1.f</MotionMoveSpeedRatio_Y>
<MotionMoveSpeedRatioFrameStart_1>-1</MotionMoveSpeedRatioFrameStart_1>
<MotionMoveSpeedRatioFrame_1>10.f</MotionMoveSpeedRatioFrame_1>
<MotionMoveSpeedRatioFrameY_1>10.f</MotionMoveSpeedRatioFrameY_1>
<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
<DontCatchTime>0</DontCatchTime>
<DontJump>false</DontJump>
<OnceSendDamage>0</OnceSendDamage> 
<ShakeCameraStartFrame>-1</ShakeCameraStartFrame>
<GroundHeightRepair>0.1f</GroundHeightRepair>
<MoveType>IngAutoTarget</MoveType>
<AutoTargetEndFrame>9</AutoTargetEndFrame>
<AutoTargetPower>0.2</AutoTargetPower>
</Motion>
</syntaxhighlight>

== Gravity and PadRotation ==
The following Gravity and PadRotation variables are interpreted and explained by Nec0Arc and myself, so you can understand how to adjust the player’s movement across the X, Y, and Z axis. The value of these variables depend on what kind of attack you would want (grounded, launcher, aerial, unidirectional, multidirectional, etc.)

* PadRotationIntensity is a general value that of the attack's rotation via the left stick. It is assumed the value is represented in degrees or whatever value is used by the controller's left-stick.
* IsGravity and its subsequent parameters are self-explanatory. Ground moves follow the above setup for its gravity arrays and values.
* Aerial moves follow this particular setup for IsGravity:
* PadRotationIntensity_StartX sets the keyframe for the player’s movement during an attack.
* PadRotationIntensity_PowerX sets the degrees of rotation your player can move.
* PadRotationValidX just sets the value to true or false.

== GameSpeed and Guarding ==
The following discoveries were made by BaconYum and myself: GameSpeed represents the “Slow Motion” moments that happen with attacks, so let’s look at the variables:

* GameSpeed_StartX refers to the specific frame that starts the GameSpeed variable.
* GameSpeed_PowerX refers to the power of this GameSpeed modifier, which is simple to understand.
** A value of 1 means the game’s speed is normal
** 1 > X > 0 means the game’s speed is slowed. So if you have a value of 0.5, the game’s speed is halved.
** A value above 1 means the game’s speed is multiplied by that amount. A value of 2 means the game’s speed is doubled.
* GameSpeed_CollPowerX does the same thing, except it refers to the player’s collision when doing the attack.
* GuardStart/EndFrame are self-explanatory, and they surprisingly explain the mechanic of Shield Cancelling… neat!

== Sound and Effects ==
The Sound element is unused in the main game’s Attack XML, mostly used in the TBRES XMLs. The Effect element, however, can be used generally for hand and feet attacks.

* Effect_StartX is the start time value for the effect to take place. L/R is for hands, LF/RF is for feet.
* Effect_EndX is the end time value for the effect to take place.
* Effect_SizeX is self explanatory
* Effect_NameX is also self-explanatory. If you want to look for the effect names for the Werehog, look at EvilSonic’s ar files.

== Collision ==
The Collision Element deals with the attack’s hitbox, which registers the hits and damage. Both Nec0Arc and NextinFRFX interpreted and discovered the following variables to help you understand what they do:

* Just keep it as true. I don’t know what it does.
* SizeX is the initial or start size of the attack’s hitbox.
* SizeDeltaX is the final or end size of the attack’s hitbox
* RHandStartX is the frame where the collision hitbox starts, applying the SizeX variable. The specific body hitbox can be changed ('''refer to this link''').
* RHandEndX is the frame where the collision hitbox ends, applying the SizeDeltaX variable.

== Camera ==
This element deals with the player’s camera when doing certain attacks. These values were taken from Sho-Hog-Ken (SHAS).

* StartEaseInFrame/StartEaseOutFrame are used to set the range of when the camera eases in and out.
* EaseIn/EaseOut is the value that the camera pulls in or pulls out.
* Fovy probably means FOV (field of view). The Y could be a type or mean the Y-Axis.
* HopeLength… your guess is as good as mine.
* Height is self-explanatory.

== Vibration ==
This element deals with the controller’s vibration, usually when a hit is registered.

* Start/EndFrame are self-explanatory
* BigMoter and SmallMoter are the vibration motors of the control, meaning left or right.
* SuccessTimeLength is how long the vibration lasts if you land a hit
* SuccessBig/SmallMoter is the same thing but for the motors specifically.

== Attack ==
These are the primary Attack values, which we know are connected to the Collision (thanks to Nec0Arc). Let’s take a look at the Attack Variables, which are the final variables you’ll need to complete your Motion:

* Type is one of many different Attack Types that you can use.
* DamagePower is self-explanatory, and its value is multiplied by the Strength Stat
* KnockOutPower_Y determines the vertical knockback distance for enemies
* KnockOutPower_Dir determines the horizontal knockback distance for enemies (I should note, for both, that it weirdly isn’t alterable when doing)
* KnockOutAnglePowerRatio is just a multiplier for both KnockOutPower variables.
* The Attribute variable can be set to Vertical, Side, or FinishAttack.

Creating & Customizing Attack Motions (Unique Inputs)

2026-03-28T17:26:52Z

King Galactix:

{{Notice|type=note|content=You will need the following files from the #Application archive file:
* EvilAttackAction1.xml
* EvilAttackMotionFile.xml}}

The '''MotionList''' contains a series of '''Motions''', or the '''Unique Inputs (UIs)''' in the Werehog’s combos. These Motion are XML cells which determine the value of the animation, movement, collision, attack types, and other attributes of each and every unique input of the Werehog's attacks. These elements are extensively long because of their content, so we will break each section down for you. For convenience's sake, we will create a new scenario by making a new Motion (individual attack) called “MOVE_A” and explain what each variable does.

By the end of this guide, you'll have a fairly comprehensive and complete Motion file.<syntaxhighlight lang="xml" line="1" start="125"><Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>
<MotionMoveSpeedRatio>0.875f</MotionMoveSpeedRatio>
<MotionMoveSpeedRatio_Y>1.f</MotionMoveSpeedRatio_Y>
<MotionMoveSpeedRatioFrameStart_1>-1</MotionMoveSpeedRatioFrameStart_1>
<MotionMoveSpeedRatioFrame_1>10.f</MotionMoveSpeedRatioFrame_1>
<MotionMoveSpeedRatioFrameY_1>10.f</MotionMoveSpeedRatioFrameY_1>
<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
<DontCatchTime>0</DontCatchTime>
<DontJump>false</DontJump>
<ShakeCameraStartFrame>-1</ShakeCameraStartFrame>
<GroundHeightRepair>0.1f</GroundHeightRepair>
<MoveType>IngAutoTarget</MoveType>
<AutoTargetEndFrame>9</AutoTargetEndFrame>
<AutoTargetPower>0.2</AutoTargetPower>
<PadRotationIntensity>20</PadRotationIntensity>
<IsGravity>true</IsGravity>
<GravityArray_Start1>-1</GravityArray_Start1>
<IsGravityArray1>true</IsGravityArray1>
<PadRotationIntensity_Start1>0</PadRotationIntensity_Start1>
<PadRotationIntensity_Power1>20</PadRotationIntensity_Power1>
<PadRotationValid1>true</PadRotationValid1>
<PadRotationIntensity_Start2>8</PadRotationIntensity_Start2>
<PadRotationIntensity_Power2>0</PadRotationIntensity_Power2>
<PadRotationValid2>false</PadRotationValid2>
<PadRotationIntensity_Start3>22</PadRotationIntensity_Start3>
<PadRotationIntensity_Power3>20</PadRotationIntensity_Power3>
<PadRotationValid3>true</PadRotationValid3>
<GameSpeed_Start1>0</GameSpeed_Start1>
<GameSpeed_Power1>1</GameSpeed_Power1>
<GameSpeed_CollPower1>1</GameSpeed_CollPower1>
<GuardStartFrame>8</GuardStartFrame>
<GuardEndFrame>27</GuardEndFrame>

<Effect>
<REffect_Start1>4</REffect_Start1>
<REffect_End1>16</REffect_End1>
<REffect_Size1>2</REffect_Size1>
<REffect_Name1>evil_punch_01</REffect_Name1>
</Effect>
<Sound></Sound>
<Collision>
<DebugDraw>true</DebugDraw>
<Size1>0.75f</Size1>
<SizeDelta1>0.f</SizeDelta1>
<RHandStart1>6</RHandStart1>
<RHandEnd1>16</RHandEnd1>
</Collision>
<Vibration>
<StartFrame>-1</StartFrame>
<EndFrame>-1</EndFrame>
<BigMoter>0.f</BigMoter>
<SmallMoter>0.f</SmallMoter>
<SuccessTimeLength>0.01</SuccessTimeLength>
<SuccessBigMoter>0.5f</SuccessBigMoter>
<SuccessSmallMoter>0.5f</SuccessSmallMoter>
</Vibration>
<Attack>
<Type1>NormalHard</Type1>
<DamagePower1>95</DamagePower1>
<KnockOutPower_Y1>0.f</KnockOutPower_Y1>
<KnockOutPower_Dir1>2.2f</KnockOutPower_Dir1>
<KnockOutAnglePowerRatio1>0.5f</KnockOutAnglePowerRatio1>
<Attribute1>VerticalAttack</Attribute1>
</Attack>
</Motion></syntaxhighlight>
== Names ==
We start with the MotionName and FileName. The MotionName can be whatever it wants, but the FileName must be exactly as it’s written within EvilAttackMotionFile.xml<syntaxhighlight lang="xml">
<Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
</Motion>
</syntaxhighlight>For the most part, changing the filename is an entirely arbitrary case. But if you’re planning to change the filename anyways:

# Find the name of your animation file (formatted as *.anm.hkx)
# Look for EvilAttackMotionFile.xml, and look within that XML
# You can either change the filename or make a new MotionFileList. However, there are some limitations… so this is an arbitrary action unless you’re using the Beta Combos.
<syntaxhighlight lang="xml" line="1" start="1">
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<Start>
<StartPoint>

<MotionFileList>
<MotionName>NSA</MotionName>
<FileName>evilsonic_attackNSA</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSB</MotionName>
<FileName>evilsonic_attackNSB</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSC</MotionName>
<FileName>evilsonic_attackNSC</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSD</MotionName>
<FileName>evilsonic_attackNSD</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSE</MotionName>
<FileName>evilsonic_attackNSE</FileName>
</MotionFileList>


<MotionFileList>
<MotionName>MOVE_A</MotionName>
<FileName>evilsonic_attackNSE</FileName>
</MotionFileList>
</Start>
</StartPoint>
</syntaxhighlight>

== Animation and Movement ==
The animation and movement values here determine how your Motion looks and moves visually and physically.

* '''MotionBlendTimeS''', '''MotionBlendTimeE''', and '''MotionBlendTimeEIdle''' blend the animations between a previous and following combo. Keep the values as 0.02f.
* '''MotionMoveSpeedRatio''' (MMSR for convenience) and '''MotionMoveSpeedRatio_Y''' control the player’s movement ratio when making the entire attack. You can experiment with these values, but remember to write it in the form of “A.Bf”
* '''MotionMoveSpeedRatioFrameStart_X,''' '''MotionMoveSpeedRatioFrame_X, and MotionMoveSpeedRatioFrameY_X'''and its subsequent variables apply the same movement/distance ratio, except it’s done within a certain frame. Reference other moves if you want to make particular adjustments.
* '''MotionFirstSpeed''', '''MiddleSpeed''', and '''EndSpeed''' all affect the Attack’s animation speed.
* '''MotionSpeed_First'''/'''MiddleFrame''' represents when the MotionFirstSpeed and MiddleSpeed params are executed (corresponding with the animation frames).
<syntaxhighlight lang="xml" line="1">
<Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>
<MotionMoveSpeedRatio>0.875f</MotionMoveSpeedRatio>
<MotionMoveSpeedRatio_Y>1.f</MotionMoveSpeedRatio_Y>
<MotionMoveSpeedRatioFrameStart_1>-1</MotionMoveSpeedRatioFrameStart_1>
<MotionMoveSpeedRatioFrame_1>10.f</MotionMoveSpeedRatioFrame_1>
<MotionMoveSpeedRatioFrameY_1>10.f</MotionMoveSpeedRatioFrameY_1>
<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
</Motion>
</syntaxhighlight>

== General ==
Now we can take a look at more general variables. These are equally important for combat and visual aspects of the Werehog.

* AttackScope sets the degrees of turning while attacking. You have None, Scope90, and Scope360 to use.
* DontCatchTime states how long it takes before the player can use the grab. Set it to 0 for ground moves, 2 for aerial moves.
* DontJump is self-explanatory. You apply it for whatever moves you DON'T want to have an enabled jump afterwards, such as Sho-Hog-Ken (YYA), and disable it for combo that you want to jump with, such as Unleashed Wild Combo (XX-YY-XX-YY).
* OnceSendDamage determines how long a combo can continually send damage. The default value is usually zero, and many moves use this as a way of implementing multiple hits for combos with a single or more number of hitboxes.
* ShakeCameraStartFrame is the start frame for when the Camera Shake can happen for certain moves. Unfortunately, there are no specific variables to affect the number or intensity of shakes.
* GroundHeightRepair determines the floatiness of a move. Lower values mean more floaty and higher values mean less floaty.
* MoveType has two values: Default and IngAutoTarget (the variables below only work when IngAutoTarget is enabled.
* AutoTargetEndFrame can be set to 0 for Default, and any value for IngAutoTarget
* AutoTargetPower can be set to 0 for Default, and any value for IngAutoTarget
<syntaxhighlight lang="xml">
<Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>
<MotionMoveSpeedRatio>0.875f</MotionMoveSpeedRatio>
<MotionMoveSpeedRatio_Y>1.f</MotionMoveSpeedRatio_Y>
<MotionMoveSpeedRatioFrameStart_1>-1</MotionMoveSpeedRatioFrameStart_1>
<MotionMoveSpeedRatioFrame_1>10.f</MotionMoveSpeedRatioFrame_1>
<MotionMoveSpeedRatioFrameY_1>10.f</MotionMoveSpeedRatioFrameY_1>
<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
<DontCatchTime>0</DontCatchTime>
<DontJump>false</DontJump>
<OnceSendDamage>0</OnceSendDamage> 
<ShakeCameraStartFrame>-1</ShakeCameraStartFrame>
<GroundHeightRepair>0.1f</GroundHeightRepair>
<MoveType>IngAutoTarget</MoveType>
<AutoTargetEndFrame>9</AutoTargetEndFrame>
<AutoTargetPower>0.2</AutoTargetPower>
</Motion>
</syntaxhighlight>

== Gravity and PadRotation ==
The following Gravity and PadRotation variables are interpreted and explained by Nec0Arc and myself, so you can understand how to adjust the player’s movement across the X, Y, and Z axis. The value of these variables depend on what kind of attack you would want (grounded, launcher, aerial, unidirectional, multidirectional, etc.)

* PadRotationIntensity is a general value that of the attack's rotation via the left stick. It is assumed the value is represented in degrees or whatever value is used by the controller's left-stick.
* IsGravity and its subsequent parameters are self-explanatory. Ground moves follow the above setup for its gravity arrays and values.
* Aerial moves follow this particular setup for IsGravity:
* PadRotationIntensity_StartX sets the keyframe for the player’s movement during an attack.
* PadRotationIntensity_PowerX sets the degrees of rotation your player can move.
* PadRotationValidX just sets the value to true or false.

== GameSpeed and Guarding ==
The following discoveries were made by BaconYum and myself: GameSpeed represents the “Slow Motion” moments that happen with attacks, so let’s look at the variables:

* GameSpeed_StartX refers to the specific frame that starts the GameSpeed variable.
* GameSpeed_PowerX refers to the power of this GameSpeed modifier, which is simple to understand.
** A value of 1 means the game’s speed is normal
** 1 > X > 0 means the game’s speed is slowed. So if you have a value of 0.5, the game’s speed is halved.
** A value above 1 means the game’s speed is multiplied by that amount. A value of 2 means the game’s speed is doubled.
* GameSpeed_CollPowerX does the same thing, except it refers to the player’s collision when doing the attack.
* GuardStart/EndFrame are self-explanatory, and they surprisingly explain the mechanic of Shield Cancelling… neat!

== Sound and Effects ==
The Sound element is unused in the main game’s Attack XML, mostly used in the TBRES XMLs. The Effect element, however, can be used generally for hand and feet attacks.

* Effect_StartX is the start time value for the effect to take place. L/R is for hands, LF/RF is for feet.
* Effect_EndX is the end time value for the effect to take place.
* Effect_SizeX is self explanatory
* Effect_NameX is also self-explanatory. If you want to look for the effect names for the Werehog, look at EvilSonic’s ar files.

== Collision ==
The Collision Element deals with the attack’s hitbox, which registers the hits and damage. Both Nec0Arc and NextinFRFX interpreted and discovered the following variables to help you understand what they do:

* Just keep it as true. I don’t know what it does.
* SizeX is the initial or start size of the attack’s hitbox.
* SizeDeltaX is the final or end size of the attack’s hitbox
* RHandStartX is the frame where the collision hitbox starts, applying the SizeX variable. The specific body hitbox can be changed ('''refer to this link''').
* RHandEndX is the frame where the collision hitbox ends, applying the SizeDeltaX variable.

== Camera ==
This element deals with the player’s camera when doing certain attacks. These values were taken from Sho-Hog-Ken (SHAS).

* StartEaseInFrame/StartEaseOutFrame are used to set the range of when the camera eases in and out.
* EaseIn/EaseOut is the value that the camera pulls in or pulls out.
* Fovy probably means FOV (field of view). The Y could be a type or mean the Y-Axis.
* HopeLength… your guess is as good as mine.
* Height is self-explanatory.

== Vibration ==
This element deals with the controller’s vibration, usually when a hit is registered.

* Start/EndFrame are self-explanatory
* BigMoter and SmallMoter are the vibration motors of the control, meaning left or right.
* SuccessTimeLength is how long the vibration lasts if you land a hit
* SuccessBig/SmallMoter is the same thing but for the motors specifically.

== Attack ==
These are the primary Attack values, which we know are connected to the Collision (thanks to Nec0Arc). Let’s take a look at the Attack Variables, which are the final variables you’ll need to complete your Motion:

* Type is one of many different Attack Types that you can use.
* DamagePower is self-explanatory, and its value is multiplied by the Strength Stat
* KnockOutPower_Y determines the vertical knockback distance for enemies
* KnockOutPower_Dir determines the horizontal knockback distance for enemies (I should note, for both, that it weirdly isn’t alterable when doing)
* KnockOutAnglePowerRatio is just a multiplier for both KnockOutPower variables.
* The Attribute variable can be set to Vertical, Side, or FinishAttack.

Creating & Customizing Attack Motions (Unique Inputs)

2026-03-28T01:52:16Z

King Galactix:

The '''MotionList''' contains a series of '''Motions''', or the '''Unique Inputs (UIs)''' in the Werehog’s combos. These Motion are XML cells which determine the value of the animation, movement, collision, attack types, and other attributes of each and every unique input of the Werehog's attacks. These elements are extensively long because of their content, so we will break each section down for you. For convenience's sake, we will create a new scenario by making a new Motion (individual attack) called “MOVE_A”, of which its layout is shown below, and explain what each variable does.<syntaxhighlight lang="xml" line="1" start="125"><Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>
<MotionMoveSpeedRatio>0.875f</MotionMoveSpeedRatio>
<MotionMoveSpeedRatio_Y>1.f</MotionMoveSpeedRatio_Y>
<MotionMoveSpeedRatioFrameStart_1>-1</MotionMoveSpeedRatioFrameStart_1>
<MotionMoveSpeedRatioFrame_1>10.f</MotionMoveSpeedRatioFrame_1>
<MotionMoveSpeedRatioFrameY_1>10.f</MotionMoveSpeedRatioFrameY_1>
<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
<DontCatchTime>0</DontCatchTime>
<DontJump>false</DontJump>
<ShakeCameraStartFrame>-1</ShakeCameraStartFrame>
<GroundHeightRepair>0.1f</GroundHeightRepair>
<MoveType>IngAutoTarget</MoveType>
<AutoTargetEndFrame>9</AutoTargetEndFrame>
<AutoTargetPower>0.2</AutoTargetPower>
<PadRotationIntensity>20</PadRotationIntensity>
<IsGravity>true</IsGravity>
<GravityArray_Start1>-1</GravityArray_Start1>
<IsGravityArray1>true</IsGravityArray1>
<PadRotationIntensity_Start1>0</PadRotationIntensity_Start1>
<PadRotationIntensity_Power1>20</PadRotationIntensity_Power1>
<PadRotationValid1>true</PadRotationValid1>
<PadRotationIntensity_Start2>8</PadRotationIntensity_Start2>
<PadRotationIntensity_Power2>0</PadRotationIntensity_Power2>
<PadRotationValid2>false</PadRotationValid2>
<PadRotationIntensity_Start3>22</PadRotationIntensity_Start3>
<PadRotationIntensity_Power3>20</PadRotationIntensity_Power3>
<PadRotationValid3>true</PadRotationValid3>
<GameSpeed_Start1>0</GameSpeed_Start1>
<GameSpeed_Power1>1</GameSpeed_Power1>
<GameSpeed_CollPower1>1</GameSpeed_CollPower1>
<GuardStartFrame>8</GuardStartFrame>
<GuardEndFrame>27</GuardEndFrame>

<Effect>
<REffect_Start1>4</REffect_Start1>
<REffect_End1>16</REffect_End1>
<REffect_Size1>2</REffect_Size1>
<REffect_Name1>evil_punch_01</REffect_Name1>
</Effect>
<Sound></Sound>
<Collision>
<DebugDraw>true</DebugDraw>
<Size1>0.75f</Size1>
<SizeDelta1>0.f</SizeDelta1>
<RHandStart1>6</RHandStart1>
<RHandEnd1>16</RHandEnd1>
</Collision>
<Vibration>
<StartFrame>-1</StartFrame>
<EndFrame>-1</EndFrame>
<BigMoter>0.f</BigMoter>
<SmallMoter>0.f</SmallMoter>
<SuccessTimeLength>0.01</SuccessTimeLength>
<SuccessBigMoter>0.5f</SuccessBigMoter>
<SuccessSmallMoter>0.5f</SuccessSmallMoter>
</Vibration>
<Attack>
<Type1>NormalHard</Type1>
<DamagePower1>95</DamagePower1>
<KnockOutPower_Y1>0.f</KnockOutPower_Y1>
<KnockOutPower_Dir1>2.2f</KnockOutPower_Dir1>
<KnockOutAnglePowerRatio1>0.5f</KnockOutAnglePowerRatio1>
<Attribute1>VerticalAttack</Attribute1>
</Attack>
</Motion></syntaxhighlight>You will need the following files from the #Application archive file:

* EvilAttackAction1.xml
* EvilAttackMotionFile.xml

== Names ==
We start with the MotionName and FileName. The MotionName can be whatever it wants, but the FileName must be exactly as it’s written within EvilAttackMotionFile.xml<syntaxhighlight lang="xml">
<Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
</Motion>
</syntaxhighlight>For the most part, changing the filename is an entirely arbitrary case. But if you’re planning to change the filename anyways:

# Find the name of your animation file (formatted as *.anm.hkx)
# Look for EvilAttackMotionFile.xml, and look within that XML
# You can either change the filename or make a new MotionFileList. However, there are some limitations… so this is an arbitrary action unless you’re using the Beta Combos.
<syntaxhighlight lang="xml" line="1" start="1">
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<Start>
<StartPoint>

<MotionFileList>
<MotionName>NSA</MotionName>
<FileName>evilsonic_attackNSA</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSB</MotionName>
<FileName>evilsonic_attackNSB</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSC</MotionName>
<FileName>evilsonic_attackNSC</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSD</MotionName>
<FileName>evilsonic_attackNSD</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSE</MotionName>
<FileName>evilsonic_attackNSE</FileName>
</MotionFileList>


<MotionFileList>
<MotionName>MOVE_A</MotionName>
<FileName>evilsonic_attackNSE</FileName>
</MotionFileList>
</Start>
</StartPoint>
</syntaxhighlight>

== Animation and Movement ==
The animation and movement values here determine how your Motion looks and moves visually and physically.

* '''MotionBlendTimeS''', '''MotionBlendTimeE''', and '''MotionBlendTimeEIdle''' blend the animations between a previous and following combo. Keep the values as 0.02f.
* '''MotionMoveSpeedRatio''' (MMSR for convenience) and '''MotionMoveSpeedRatio_Y''' control the player’s movement ratio when making the entire attack. You can experiment with these values, but remember to write it in the form of “A.Bf”
* '''MotionMoveSpeedRatioFrameStart_X,''' '''MotionMoveSpeedRatioFrame_X, and MotionMoveSpeedRatioFrameY_X'''and its subsequent variables apply the same movement/distance ratio, except it’s done within a certain frame. Reference other moves if you want to make particular adjustments.
* '''MotionFirstSpeed''', '''MiddleSpeed''', and '''EndSpeed''' all affect the Attack’s animation speed.
* '''MotionSpeed_First'''/'''MiddleFrame''' represents when the MotionFirstSpeed and MiddleSpeed params are executed (corresponding with the animation frames).
<syntaxhighlight lang="xml" line="1">
<Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>
<MotionMoveSpeedRatio>0.875f</MotionMoveSpeedRatio>
<MotionMoveSpeedRatio_Y>1.f</MotionMoveSpeedRatio_Y>
<MotionMoveSpeedRatioFrameStart_1>-1</MotionMoveSpeedRatioFrameStart_1>
<MotionMoveSpeedRatioFrame_1>10.f</MotionMoveSpeedRatioFrame_1>
<MotionMoveSpeedRatioFrameY_1>10.f</MotionMoveSpeedRatioFrameY_1>
<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
</Motion>
</syntaxhighlight>

== General ==
Now we can take a look at more general variables. These are equally important for combat and visual aspects of the Werehog.

* AttackScope sets the degrees of turning while attacking. You have None, Scope90, and Scope360 to use.
* DontCatchTime states how long it takes before the player can use the grab. Set it to 0 for ground moves, 2 for aerial moves.
* DontJump is self-explanatory. You apply it for whatever moves you DON'T want to have an enabled jump afterwards, such as Sho-Hog-Ken (YYA), and disable it for combo that you want to jump with, such as Unleashed Wild Combo (XX-YY-XX-YY).
* OnceSendDamage determines how long a combo can continually send damage. The default value is usually zero, and many moves use this as a way of implementing multiple hits for combos with a single or more number of hitboxes.
* ShakeCameraStartFrame is the start frame for when the Camera Shake can happen for certain moves. Unfortunately, there are no specific variables to affect the number or intensity of shakes.
* GroundHeightRepair determines the floatiness of a move. Lower values mean more floaty and higher values mean less floaty.
* MoveType has two values: Default and IngAutoTarget (the variables below only work when IngAutoTarget is enabled.
* AutoTargetEndFrame can be set to 0 for Default, and any value for IngAutoTarget
* AutoTargetPower can be set to 0 for Default, and any value for IngAutoTarget
<syntaxhighlight lang="xml">
<Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>
<MotionMoveSpeedRatio>0.875f</MotionMoveSpeedRatio>
<MotionMoveSpeedRatio_Y>1.f</MotionMoveSpeedRatio_Y>
<MotionMoveSpeedRatioFrameStart_1>-1</MotionMoveSpeedRatioFrameStart_1>
<MotionMoveSpeedRatioFrame_1>10.f</MotionMoveSpeedRatioFrame_1>
<MotionMoveSpeedRatioFrameY_1>10.f</MotionMoveSpeedRatioFrameY_1>
<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
<DontCatchTime>0</DontCatchTime>
<DontJump>false</DontJump>
<OnceSendDamage>0</OnceSendDamage> 
<ShakeCameraStartFrame>-1</ShakeCameraStartFrame>
<GroundHeightRepair>0.1f</GroundHeightRepair>
<MoveType>IngAutoTarget</MoveType>
<AutoTargetEndFrame>9</AutoTargetEndFrame>
<AutoTargetPower>0.2</AutoTargetPower>
</Motion>
</syntaxhighlight>

== Gravity and PadRotation ==
The following Gravity and PadRotation variables are interpreted and explained by Nec0Arc and myself, so you can understand how to adjust the player’s movement across the X, Y, and Z axis.

* PadRotationIntensity is a general value. It sets the value of your Left Stick’s rotation.
* IsGravity and its subsequent parameters are self-explanatory. Ground moves follow the above setup for its gravity arrays and values.
* Aerial moves follow this particular setup for IsGravity:
* PadRotationIntensity_StartX sets the keyframe for the player’s movement during an attack.
* PadRotationIntensity_PowerX sets the degrees of rotation your player can move.
* PadRotationValidX just sets the value to true or false.

== GameSpeed and Guarding ==
The following discoveries were made by BaconYum and myself: GameSpeed represents the “Slow Motion” moments that happen with attacks, so let’s look at the variables:

* GameSpeed_StartX refers to the specific frame that starts the GameSpeed variable.
* GameSpeed_PowerX refers to the power of this GameSpeed modifier, which is simple to understand.
** A value of 1 means the game’s speed is normal
** 1 > X > 0 means the game’s speed is slowed. So if you have a value of 0.5, the game’s speed is halved.
** A value above 1 means the game’s speed is multiplied by that amount. A value of 2 means the game’s speed is doubled.
* GameSpeed_CollPowerX does the same thing, except it refers to the player’s collision when doing the attack.
* GuardStart/EndFrame are self-explanatory, and they surprisingly explain the mechanic of Shield Cancelling… neat!

== Sound and Effects ==
The Sound element is unused in the main game’s Attack XML, mostly used in the TBRES XMLs. The Effect element, however, can be used generally for hand and feet attacks.

* Effect_StartX is the start time value for the effect to take place. L/R is for hands, LF/RF is for feet.
* Effect_EndX is the end time value for the effect to take place.
* Effect_SizeX is self explanatory
* Effect_NameX is also self-explanatory. If you want to look for the effect names for the Werehog, look at EvilSonic’s ar files.

== Collision ==
The Collision Element deals with the attack’s hitbox, which registers the hits and damage. Both Nec0Arc and NextinFRFX interpreted and discovered the following variables to help you understand what they do:

* Just keep it as true. I don’t know what it does.
* SizeX is the initial or start size of the attack’s hitbox.
* SizeDeltaX is the final or end size of the attack’s hitbox
* RHandStartX is the frame where the collision hitbox starts, applying the SizeX variable. The specific body hitbox can be changed ('''refer to this link''').
* RHandEndX is the frame where the collision hitbox ends, applying the SizeDeltaX variable.

== Camera ==
This element deals with the player’s camera when doing certain attacks. These values were taken from Sho-Hog-Ken (SHAS).

* StartEaseInFrame/StartEaseOutFrame are used to set the range of when the camera eases in and out.
* EaseIn/EaseOut is the value that the camera pulls in or pulls out.
* Fovy probably means FOV (field of view). The Y could be a type or mean the Y-Axis.
* HopeLength… your guess is as good as mine.
* Height is self-explanatory.

== Vibration ==
This element deals with the controller’s vibration, usually when a hit is registered.

* Start/EndFrame are self-explanatory
* BigMoter and SmallMoter are the vibration motors of the control, meaning left or right.
* SuccessTimeLength is how long the vibration lasts if you land a hit
* SuccessBig/SmallMoter is the same thing but for the motors specifically.

== Attack ==
These are the primary Attack values, which we know are connected to the Collision (thanks to Nec0Arc). Let’s take a look at the Attack Variables, which are the final variables you’ll need to complete your Motion:

* Type is one of many different Attack Types that you can use.
* DamagePower is self-explanatory, and its value is multiplied by the Strength Stat
* KnockOutPower_Y determines the vertical knockback distance for enemies
* KnockOutPower_Dir determines the horizontal knockback distance for enemies (I should note, for both, that it weirdly isn’t alterable when doing)
* KnockOutAnglePowerRatio is just a multiplier for both KnockOutPower variables.
* The Attribute variable can be set to Vertical, Side, or FinishAttack.

Creating & Customizing Attack Motions (Unique Inputs)

2026-03-28T01:51:49Z

King Galactix: Added comment code for the XMLs of the motions

The '''MotionList''' contains a series of '''Motions''', or the '''Unique Inputs (UIs)''' in the Werehog’s combos. These Motion are XML cells which determine the value of the animation, movement, collision, attack types, and other attributes of each and every unique input of the Werehog's attacks. These elements are extensively long because of their content, so we will break each section down for you. For convenience's sake, we will create a new scenario by making a new Motion (individual attack) called “MOVE_A”, of which its layout is shown below, and explain what each variable does.<syntaxhighlight lang="xml" line="1" start="125"><Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>
<MotionMoveSpeedRatio>0.875f</MotionMoveSpeedRatio>
<MotionMoveSpeedRatio_Y>1.f</MotionMoveSpeedRatio_Y>
<MotionMoveSpeedRatioFrameStart_1>-1</MotionMoveSpeedRatioFrameStart_1>
<MotionMoveSpeedRatioFrame_1>10.f</MotionMoveSpeedRatioFrame_1>
<MotionMoveSpeedRatioFrameY_1>10.f</MotionMoveSpeedRatioFrameY_1>
<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
<DontCatchTime>0</DontCatchTime>
<DontJump>false</DontJump>
<ShakeCameraStartFrame>-1</ShakeCameraStartFrame>
<GroundHeightRepair>0.1f</GroundHeightRepair>
<MoveType>IngAutoTarget</MoveType>
<AutoTargetEndFrame>9</AutoTargetEndFrame>
<AutoTargetPower>0.2</AutoTargetPower>
<PadRotationIntensity>20</PadRotationIntensity>
<IsGravity>true</IsGravity>
<GravityArray_Start1>-1</GravityArray_Start1>
<IsGravityArray1>true</IsGravityArray1>
<PadRotationIntensity_Start1>0</PadRotationIntensity_Start1>
<PadRotationIntensity_Power1>20</PadRotationIntensity_Power1>
<PadRotationValid1>true</PadRotationValid1>
<PadRotationIntensity_Start2>8</PadRotationIntensity_Start2>
<PadRotationIntensity_Power2>0</PadRotationIntensity_Power2>
<PadRotationValid2>false</PadRotationValid2>
<PadRotationIntensity_Start3>22</PadRotationIntensity_Start3>
<PadRotationIntensity_Power3>20</PadRotationIntensity_Power3>
<PadRotationValid3>true</PadRotationValid3>
<GameSpeed_Start1>0</GameSpeed_Start1>
<GameSpeed_Power1>1</GameSpeed_Power1>
<GameSpeed_CollPower1>1</GameSpeed_CollPower1>
<GuardStartFrame>8</GuardStartFrame>
<GuardEndFrame>27</GuardEndFrame>

<Effect>
<REffect_Start1>4</REffect_Start1>
<REffect_End1>16</REffect_End1>
<REffect_Size1>2</REffect_Size1>
<REffect_Name1>evil_punch_01</REffect_Name1>
</Effect>
<Sound></Sound>
<Collision>
<DebugDraw>true</DebugDraw>
<Size1>0.75f</Size1>
<SizeDelta1>0.f</SizeDelta1>
<RHandStart1>6</RHandStart1>
<RHandEnd1>16</RHandEnd1>
</Collision>
<Vibration>
<StartFrame>-1</StartFrame>
<EndFrame>-1</EndFrame>
<BigMoter>0.f</BigMoter>
<SmallMoter>0.f</SmallMoter>
<SuccessTimeLength>0.01</SuccessTimeLength>
<SuccessBigMoter>0.5f</SuccessBigMoter>
<SuccessSmallMoter>0.5f</SuccessSmallMoter>
</Vibration>
<Attack>
<Type1>NormalHard</Type1>
<DamagePower1>95</DamagePower1>
<KnockOutPower_Y1>0.f</KnockOutPower_Y1>
<KnockOutPower_Dir1>2.2f</KnockOutPower_Dir1>
<KnockOutAnglePowerRatio1>0.5f</KnockOutAnglePowerRatio1>
<Attribute1>VerticalAttack</Attribute1>
</Attack>
</Motion></syntaxhighlight>You will need the following files from the #Application archive file:

* EvilAttackAction1.xml
* EvilAttackMotionFile.xml

== Names: ==
We start with the MotionName and FileName. The MotionName can be whatever it wants, but the FileName must be exactly as it’s written within EvilAttackMotionFile.xml<syntaxhighlight lang="xml">
<Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
</Motion>
</syntaxhighlight>For the most part, changing the filename is an entirely arbitrary case. But if you’re planning to change the filename anyways:

# Find the name of your animation file (formatted as *.anm.hkx)
# Look for EvilAttackMotionFile.xml, and look within that XML
# You can either change the filename or make a new MotionFileList. However, there are some limitations… so this is an arbitrary action unless you’re using the Beta Combos.
<syntaxhighlight lang="xml" line="1" start="1">
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<Start>
<StartPoint>

<MotionFileList>
<MotionName>NSA</MotionName>
<FileName>evilsonic_attackNSA</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSB</MotionName>
<FileName>evilsonic_attackNSB</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSC</MotionName>
<FileName>evilsonic_attackNSC</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSD</MotionName>
<FileName>evilsonic_attackNSD</FileName>
</MotionFileList>
<MotionFileList>
<MotionName>NSE</MotionName>
<FileName>evilsonic_attackNSE</FileName>
</MotionFileList>


<MotionFileList>
<MotionName>MOVE_A</MotionName>
<FileName>evilsonic_attackNSE</FileName>
</MotionFileList>
</Start>
</StartPoint>
</syntaxhighlight>

== Animation and Movement: ==
The animation and movement values here determine how your Motion looks and moves visually and physically.

* '''MotionBlendTimeS''', '''MotionBlendTimeE''', and '''MotionBlendTimeEIdle''' blend the animations between a previous and following combo. Keep the values as 0.02f.
* '''MotionMoveSpeedRatio''' (MMSR for convenience) and '''MotionMoveSpeedRatio_Y''' control the player’s movement ratio when making the entire attack. You can experiment with these values, but remember to write it in the form of “A.Bf”
* '''MotionMoveSpeedRatioFrameStart_X,''' '''MotionMoveSpeedRatioFrame_X, and MotionMoveSpeedRatioFrameY_X'''and its subsequent variables apply the same movement/distance ratio, except it’s done within a certain frame. Reference other moves if you want to make particular adjustments.
* '''MotionFirstSpeed''', '''MiddleSpeed''', and '''EndSpeed''' all affect the Attack’s animation speed.
* '''MotionSpeed_First'''/'''MiddleFrame''' represents when the MotionFirstSpeed and MiddleSpeed params are executed (corresponding with the animation frames).
<syntaxhighlight lang="xml" line="1">
<Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>
<MotionMoveSpeedRatio>0.875f</MotionMoveSpeedRatio>
<MotionMoveSpeedRatio_Y>1.f</MotionMoveSpeedRatio_Y>
<MotionMoveSpeedRatioFrameStart_1>-1</MotionMoveSpeedRatioFrameStart_1>
<MotionMoveSpeedRatioFrame_1>10.f</MotionMoveSpeedRatioFrame_1>
<MotionMoveSpeedRatioFrameY_1>10.f</MotionMoveSpeedRatioFrameY_1>
<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
</Motion>
</syntaxhighlight>

== General: ==
Now we can take a look at more general variables. These are equally important for combat and visual aspects of the Werehog.

* AttackScope sets the degrees of turning while attacking. You have None, Scope90, and Scope360 to use.
* DontCatchTime states how long it takes before the player can use the grab. Set it to 0 for ground moves, 2 for aerial moves.
* DontJump is self-explanatory. You apply it for whatever moves you DON'T want to have an enabled jump afterwards, such as Sho-Hog-Ken (YYA), and disable it for combo that you want to jump with, such as Unleashed Wild Combo (XX-YY-XX-YY).
* OnceSendDamage determines how long a combo can continually send damage. The default value is usually zero, and many moves use this as a way of implementing multiple hits for combos with a single or more number of hitboxes.
* ShakeCameraStartFrame is the start frame for when the Camera Shake can happen for certain moves. Unfortunately, there are no specific variables to affect the number or intensity of shakes.
* GroundHeightRepair determines the floatiness of a move. Lower values mean more floaty and higher values mean less floaty.
* MoveType has two values: Default and IngAutoTarget (the variables below only work when IngAutoTarget is enabled.
* AutoTargetEndFrame can be set to 0 for Default, and any value for IngAutoTarget
* AutoTargetPower can be set to 0 for Default, and any value for IngAutoTarget
<syntaxhighlight lang="xml">
<Motion>
<MotionName>MOVE_A</MotionName>
<FileName>NSA</FileName>
<MotionBlendTimeS>0.02f</MotionBlendTimeS>
<MotionBlendTimeE>0.02f</MotionBlendTimeE>
<MotionBlendTimeEIdle>0.02f</MotionBlendTimeEIdle>
<MotionMoveSpeedRatio>0.875f</MotionMoveSpeedRatio>
<MotionMoveSpeedRatio_Y>1.f</MotionMoveSpeedRatio_Y>
<MotionMoveSpeedRatioFrameStart_1>-1</MotionMoveSpeedRatioFrameStart_1>
<MotionMoveSpeedRatioFrame_1>10.f</MotionMoveSpeedRatioFrame_1>
<MotionMoveSpeedRatioFrameY_1>10.f</MotionMoveSpeedRatioFrameY_1>
<MotionFirstSpeed>1.f</MotionFirstSpeed>
<MiddleSpeed>1.f</MiddleSpeed>
<EndSpeed>1.f</EndSpeed>
<MotionSpeed_FirstFrame>9</MotionSpeed_FirstFrame>
<MotionSpeed_MiddleFrame>16</MotionSpeed_MiddleFrame>
<DontCatchTime>0</DontCatchTime>
<DontJump>false</DontJump>
<OnceSendDamage>0</OnceSendDamage> 
<ShakeCameraStartFrame>-1</ShakeCameraStartFrame>
<GroundHeightRepair>0.1f</GroundHeightRepair>
<MoveType>IngAutoTarget</MoveType>
<AutoTargetEndFrame>9</AutoTargetEndFrame>
<AutoTargetPower>0.2</AutoTargetPower>
</Motion>
</syntaxhighlight>

== Gravity and PadRotation: ==
The following Gravity and PadRotation variables are interpreted and explained by Nec0Arc and myself, so you can understand how to adjust the player’s movement across the X, Y, and Z axis.

* PadRotationIntensity is a general value. It sets the value of your Left Stick’s rotation.
* IsGravity and its subsequent parameters are self-explanatory. Ground moves follow the above setup for its gravity arrays and values.
* Aerial moves follow this particular setup for IsGravity:
* PadRotationIntensity_StartX sets the keyframe for the player’s movement during an attack.
* PadRotationIntensity_PowerX sets the degrees of rotation your player can move.
* PadRotationValidX just sets the value to true or false.

== GameSpeed and Guarding: ==
The following discoveries were made by BaconYum and myself: GameSpeed represents the “Slow Motion” moments that happen with attacks, so let’s look at the variables:

* GameSpeed_StartX refers to the specific frame that starts the GameSpeed variable.
* GameSpeed_PowerX refers to the power of this GameSpeed modifier, which is simple to understand.
** A value of 1 means the game’s speed is normal
** 1 > X > 0 means the game’s speed is slowed. So if you have a value of 0.5, the game’s speed is halved.
** A value above 1 means the game’s speed is multiplied by that amount. A value of 2 means the game’s speed is doubled.
* GameSpeed_CollPowerX does the same thing, except it refers to the player’s collision when doing the attack.
* GuardStart/EndFrame are self-explanatory, and they surprisingly explain the mechanic of Shield Cancelling… neat!

== Sound and Effects: ==
The Sound element is unused in the main game’s Attack XML, mostly used in the TBRES XMLs. The Effect element, however, can be used generally for hand and feet attacks.

* Effect_StartX is the start time value for the effect to take place. L/R is for hands, LF/RF is for feet.
* Effect_EndX is the end time value for the effect to take place.
* Effect_SizeX is self explanatory
* Effect_NameX is also self-explanatory. If you want to look for the effect names for the Werehog, look at EvilSonic’s ar files.

== Collision: ==
The Collision Element deals with the attack’s hitbox, which registers the hits and damage. Both Nec0Arc and NextinFRFX interpreted and discovered the following variables to help you understand what they do:

* Just keep it as true. I don’t know what it does.
* SizeX is the initial or start size of the attack’s hitbox.
* SizeDeltaX is the final or end size of the attack’s hitbox
* RHandStartX is the frame where the collision hitbox starts, applying the SizeX variable. The specific body hitbox can be changed ('''refer to this link''').
* RHandEndX is the frame where the collision hitbox ends, applying the SizeDeltaX variable.

== Camera: ==
This element deals with the player’s camera when doing certain attacks. These values were taken from Sho-Hog-Ken (SHAS).

* StartEaseInFrame/StartEaseOutFrame are used to set the range of when the camera eases in and out.
* EaseIn/EaseOut is the value that the camera pulls in or pulls out.
* Fovy probably means FOV (field of view). The Y could be a type or mean the Y-Axis.
* HopeLength… your guess is as good as mine.
* Height is self-explanatory.

== Vibration: ==
This element deals with the controller’s vibration, usually when a hit is registered.

* Start/EndFrame are self-explanatory
* BigMoter and SmallMoter are the vibration motors of the control, meaning left or right.
* SuccessTimeLength is how long the vibration lasts if you land a hit
* SuccessBig/SmallMoter is the same thing but for the motors specifically.

== Attack: ==
These are the primary Attack values, which we know are connected to the Collision (thanks to Nec0Arc). Let’s take a look at the Attack Variables, which are the final variables you’ll need to complete your Motion:

* Type is one of many different Attack Types that you can use.
* DamagePower is self-explanatory, and its value is multiplied by the Strength Stat
* KnockOutPower_Y determines the vertical knockback distance for enemies
* KnockOutPower_Dir determines the horizontal knockback distance for enemies (I should note, for both, that it weirdly isn’t alterable when doing)
* KnockOutAnglePowerRatio is just a multiplier for both KnockOutPower variables.
* The Attribute variable can be set to Vertical, Side, or FinishAttack.