Creating & Customizing Attack Motions (Unique Inputs) - Revision history

King Galactix at 21:50, 27 April 2026

2026-04-27T21:50:28Z

← Older revision		Revision as of 21:50, 27 April 2026
Line 272:		Line 272:
	* 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''').		* 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.		* 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">		<syntaxhighlight lang="xml">
	<Motion>		<Motion>

King Galactix at 01:37, 20 April 2026

2026-04-20T01:37:42Z

← Older revision		Revision as of 01:37, 20 April 2026
Line 251:		Line 251:
	* Effect_SizeX is self explanatory		* 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.		* 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>
			<!-- Previous variables -->
			<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 ==		== 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 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~~.		* 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.		* SizeX is the initial or start size of the attack’s hitbox.
	* SizeDeltaX is the final or end 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''').		* 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.		* RHandEndX is the frame where the collision hitbox ends, applying the SizeDeltaX variable.
			<syntaxhighlight lang="xml">
			<Motion>
			<!-- Previous variables -->
			<Collision>
			<DebugDraw>true</DebugDraw>
			<Size1>0.75f</Size1>
			<SizeDelta1>0.f</SizeDelta1>
			<RHandStart1>6</RHandStart1>
			<RHandEnd1>16</RHandEnd1>
			</Collision>
			</Motion>
			</syntaxhighlight>

	== Camera ==		== Camera ==
Line 291:		Line 315:
	* SuccessTimeLength is how long the vibration lasts if you land a hit		* SuccessTimeLength is how long the vibration lasts if you land a hit
	* SuccessBig/SmallMoter is the same thing but for the motors specifically.		* SuccessBig/SmallMoter is the same thing but for the motors specifically.
			<syntaxhighlight lang="xml">
			<Motion>
			<!-- Previous variables -->
			<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 ==		== Attack ==
Line 297:		Line 335:
	* Type is one of many different Attack Types that you can use. Refer to the Attack Types documentation		* 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		* 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_Y determines the vertical knockback distance for enemies. It seems to be broken in retail.
	* KnockOutPower_Dir determines the horizontal knockback distance for enemies. ~~Possibly~~ broken.		* 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.		* KnockOutAnglePowerRatio is just a multiplier for both KnockOutPower variables.
	* The Attribute variable can be set to Vertical, Side, or FinishAttack.		* The Attribute variable can be set to Vertical, Side, or FinishAttack.
	<syntaxhighlight lang="xml">		<syntaxhighlight lang="xml">
	<Motion>		<Motion>
	<!-- ~~Insert other~~ variables -->		<!-- Previous variables -->
	<Attack>		<Attack>
	<Type1>NormalHard</Type1>		<Type1>NormalHard</Type1>

King Galactix at 01:31, 20 April 2026

2026-04-20T01:31:33Z

← Older revision		Revision as of 01:31, 20 April 2026
Line 3:		Line 3:
	* EvilAttackMotionFile.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>		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>		<MotionName>MOVE_A</MotionName>
	<FileName>NSA</FileName>		<FileName>NSA</FileName>
Line 165:		Line 165:
	* '''AutoTargetEndFrame''' can be set to 0 for Default, and any value for IngAutoTarget		* '''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		* '''AutoTargetPower''' can be set to 0 for Default, and any value for IngAutoTarget
	<syntaxhighlight lang="xml"><Motion>		<syntaxhighlight lang="xml"> <Motion>
	<MotionName>MOVE_A</MotionName>		<MotionName>MOVE_A</MotionName>
	<FileName>NSA</FileName>		<FileName>NSA</FileName>
Line 200:		Line 200:
	** Launcher 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:		** 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_StartX''' sets the frame that this instance of PadRotationcan start executing.
	* '''PadRotationIntensity_PowerX''' sets the degrees of ~~rotation~~ your player can move.		* '''PadRotationIntensity_PowerX''' sets the degrees of PadRotation that your player can move when executing the combo.
	* '''PadRotationValidX''' ~~just sets~~ the ~~value to~~ true or false.		* '''PadRotationValidX''' enables or disables the PadRotation with true or false.
			<syntaxhighlight lang="xml"> <Motion>
			<!-- Insert previous variables -->
			<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 ==		== GameSpeed and Guarding ==
Line 210:		Line 226:
	* GameSpeed_PowerX refers to the power of this GameSpeed modifier, which is simple to understand.		* 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		** 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.		** 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 ~~multiplied~~ by that amount. A value of 2 means the game’s speed is doubled.		** 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.		* 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!		* 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>
			<!-- Insert previous variables -->
			<GameSpeed_Start1>0</GameSpeed_Start1>
			<GameSpeed_Power1>1</GameSpeed_Power1>
			<GameSpeed_CollPower1>1</GameSpeed_CollPower1>
			<GuardStartFrame>8</GuardStartFrame>
			<GuardEndFrame>27</GuardEndFrame>
			<!--<GameSpeedColl_Start1>-1</GameSpeedColl_Start1>
			<GameSpeedColl_Speed1>-1</GameSpeedColl_Speed1>
			<GameSpeedColl_Timer1>-1</GameSpeedColl_Timer1>
			-->
			</Motion></syntaxhighlight>

	== Sound and Effects ==		== Sound and Effects ==
Line 240:		Line 269:
	* HopeLength… your guess is as good as mine.		* HopeLength… your guess is as good as mine.
	* Height is self-explanatory.		* Height is self-explanatory.
			<syntaxhighlight lang="xml">
			<Motion>
			<!-- Previous variables -->
			<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 ==		== Vibration ==

King Galactix at 05:01, 18 April 2026

2026-04-18T05:01:24Z

Show changes

King Galactix at 15:37, 1 April 2026

2026-04-01T15:37:53Z

← Older revision		Revision as of 15:37, 1 April 2026
Line 3:		Line 3:
	* EvilAttackMotionFile.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>		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>		<MotionName>MOVE_A</MotionName>
	<FileName>NSA</FileName>		<FileName>NSA</FileName>

King Galactix at 15:37, 1 April 2026

2026-04-01T15:37:42Z

← Older revision		Revision as of 15:37, 1 April 2026
Line 1:		Line 1:
	{{Notice\|type=note\|content=You will need the following files from the #Application archive file:		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		* EvilAttackAction1.xml
	* EvilAttackMotionFile.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>

	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>		<MotionName>MOVE_A</MotionName>
	<FileName>NSA</FileName>		<FileName>NSA</FileName>

King Galactix at 14:31, 30 March 2026

2026-03-30T14:31:37Z

← Older revision		Revision as of 14:31, 30 March 2026
Line 133:		Line 133:
	* '''MotionBlendTimeS''', '''MotionBlendTimeE''', and '''MotionBlendTimeEIdle''' blend the animations between a previous and following combo. Keep the values as 0.02f.		* '''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”		* '''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~~.		* '''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.		* '''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).		* '''MotionSpeed_First'''/'''MiddleFrame''' represents when the MotionFirstSpeed and MiddleSpeed params are executed (corresponding with the animation frames).
Line 159:		Line 160:
	Now we can take a look at more general variables. These are equally important for combat and visual aspects of the Werehog.		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.		* '''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.		* '''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).		* '''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).
Line 200:		Line 201:

	* 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.		* 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.		* '''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.
	* Aerial moves follow ~~this particular~~ setup for ~~IsGravity~~:		** 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_StartX sets the keyframe for the player’s movement during an attack.
	* PadRotationIntensity_PowerX sets the degrees of rotation your player can move.		* PadRotationIntensity_PowerX sets the degrees of rotation your player can move.

King Galactix at 17:28, 28 March 2026

2026-03-28T17:28:14Z

King Galactix at 17:26, 28 March 2026

2026-03-28T17:26:52Z

← Older revision		Revision as of 17:26, 28 March 2026
Line 1:		Line 1:
	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>		{{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>		<MotionName>MOVE_A</MotionName>
	<FileName>NSA</FileName>		<FileName>NSA</FileName>
Line 75:		Line 81:
	<Attribute1>VerticalAttack</Attribute1>		<Attribute1>VerticalAttack</Attribute1>
	</Attack>		</Attack>
	</Motion></syntaxhighlight>~~You will need the following files from the #Application archive file:~~		</Motion></syntaxhighlight>

	* EvilAttackAction1.xml
	* EvilAttackMotionFile.xml

	== Names ==		== 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">		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">
Line 195:		Line 197:

	== Gravity and PadRotation ==		== 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 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. It ~~sets~~ the value ~~of your Left Stick’s rotation~~.		* 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.		* 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:		* Aerial moves follow this particular setup for IsGravity:

King Galactix at 01:52, 28 March 2026

2026-03-28T01:52:16Z

← Older revision		Revision as of 01:52, 28 March 2026
Line 80:		Line 80:
	* EvilAttackMotionFile.xml		* EvilAttackMotionFile.xml

	== Names: ==		== 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">		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>		<Motion>
Line 126:		Line 126:
	</syntaxhighlight>		</syntaxhighlight>

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

Line 154:		Line 154:
	</syntaxhighlight>		</syntaxhighlight>

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

Line 194:		Line 194:
	</syntaxhighlight>		</syntaxhighlight>

	== Gravity and PadRotation: ==		== 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 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.

Line 204:		Line 204:
	* PadRotationValidX just sets the value to true or false.		* PadRotationValidX just sets the value to true or false.

	== GameSpeed and Guarding: ==		== 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:		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:

Line 215:		Line 215:
	* GuardStart/EndFrame are self-explanatory, and they surprisingly explain the mechanic of Shield Cancelling… neat!		* GuardStart/EndFrame are self-explanatory, and they surprisingly explain the mechanic of Shield Cancelling… neat!

	== Sound and Effects: ==		== 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.		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.

Line 223:		Line 223:
	* Effect_NameX is also self-explanatory. If you want to look for the effect names for the Werehog, look at EvilSonic’s ar files.		* 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: ==		== 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 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:

Line 232:		Line 232:
	* RHandEndX is the frame where the collision hitbox ends, applying the SizeDeltaX variable.		* RHandEndX is the frame where the collision hitbox ends, applying the SizeDeltaX variable.

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

Line 241:		Line 241:
	* Height is self-explanatory.		* Height is self-explanatory.

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

Line 249:		Line 249:
	* SuccessBig/SmallMoter is the same thing but for the motors specifically.		* SuccessBig/SmallMoter is the same thing but for the motors specifically.

	== Attack: ==		== 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:		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:

← Older revision		Revision as of 17:28, 28 March 2026
Line 5:		Line 5:
	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.		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>		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>		<MotionName>MOVE_A</MotionName>
	<FileName>NSA</FileName>		<FileName>NSA</FileName>
Line 83:		Line 83:
	</Motion></syntaxhighlight>		</Motion></syntaxhighlight>
	== Names ==		== 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">		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>		<Motion>
	<MotionName>MOVE_A</MotionName>		<MotionName>MOVE_A</MotionName>
Line 159:		Line 159:
	Now we can take a look at more general variables. These are equally important for combat and visual aspects of the Werehog.		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.		* '''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.		* '''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).		* '''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.		* '''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.		* '''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.		* '''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.		* '''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		* '''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		* '''AutoTargetPower''' can be set to 0 for Default, and any value for IngAutoTarget
	<syntaxhighlight lang="xml">		<syntaxhighlight lang="xml">
	<Motion>		<Motion>