Creating & Customizing Attack Actions (Combo Routes) - Revision history

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

2026-07-31T02:00:05Z

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

← Older revision		Revision as of 02:00, 31 July 2026
Line 166:		Line 166:
	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:		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__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 next input, unless WaitEndMotionEndFrame is set to a value higher than 0.		* 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.		* 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">		<syntaxhighlight lang="xml">

King Galactix: Updated the ButtonIng Input registration section

2026-07-31T01:58:07Z

Updated the ButtonIng Input registration section

← Older revision		Revision as of 01:58, 31 July 2026
Line 180:		Line 180:
	* KEY__IngStartFrame is the start value of holding the button input.		* 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__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)~~.		* 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">		<syntaxhighlight lang="xml">
	<Action>		<Action>

King Galactix: Included a disclaimer toward KEY__IngFrameTime

2026-07-31T01:54:25Z

Included a disclaimer toward KEY__IngFrameTime

← Older revision		Revision as of 01:54, 31 July 2026
Line 176:		Line 176:
	<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>		<WaitEndMotionEndFrame>22</WaitEndMotionEndFrame>
	</Action>		</Action>
	</syntaxhighlight>The three parameters below allow you to register the input while holding down on a button.		</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__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__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~~		* 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">		<syntaxhighlight lang="xml">
	<Action>		<Action>

King Galactix at 23:43, 29 July 2026

2026-07-29T23:43:39Z

← Older revision		Revision as of 23:43, 29 July 2026
Line 74:		Line 74:
	* ValidLevel_Max determines what level a combo is disabled/locked		* 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.		* 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">		** 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>
	<Action>
	<ActionName>NSD_2</ActionName>		<ActionName>NSD_2</ActionName>
	<MotionName>NSD_2</MotionName>		<MotionName>NSD_2</MotionName>
	<ValidLevel_Min>1</ValidLevel_Min> <!-- The combo is active at Combat Level 1 -->		<ValidLevel_Min>1</ValidLevel_Min> <!-- The combo is active at Combat Level 1 -->
	<ValidLevel_Max>15</ValidLevel_Max> <!-- The combo is inactive at Combat Level 15 -->		<ValidLevel_Max>15</ValidLevel_Max> <!-- The combo is inactive at Combat Level 15 -->
			</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> <!-- The combo is active at Combat Level 16 -->
			<ValidLevel_Max>99</ValidLevel_Max> <!-- The combo is active at Combat Level 99 -->
			</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">
			<!-- Pre-Upgrade -->
			<Action>
			<ActionName>NSC</ActionName>
			<MotionName>NSC</MotionName>
			<ValidLevel_Min>1</ValidLevel_Min>
			<ValidLevel_Max>15</ValidLevel_Max>
	<ValidCommon>true</ValidCommon>		<ValidCommon>true</ValidCommon>
	<ValidBerserker>true</ValidBerserker>		<ValidBerserker>true</ValidBerserker>
	<KEY__YDown></KEY__YDown>		<KEY__YDown>NSD_2</KEY__YDown>
	<~~KEY__XDown></KEY__XDown>~~		<!-- following variables -->
	~~<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>		</Action>
	<~~/syntaxhighlight>~~		<!-- Post-Upgrade -->
	** … 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>		<Action>
	<ActionName>~~NSD~~</ActionName>		<ActionName>NSC</ActionName>
	<MotionName>~~NSD~~</MotionName>		<MotionName>NSC</MotionName>
	<ValidLevel_Min>16</ValidLevel_Min>		<ValidLevel_Min>16</ValidLevel_Min>
	<ValidLevel_Max>99</ValidLevel_Max>		<ValidLevel_Max>99</ValidLevel_Max>
	<ValidCommon>true</ValidCommon>		<ValidCommon>true</ValidCommon>
	<ValidBerserker>true</ValidBerserker>		<ValidBerserker>true</ValidBerserker>
	<KEY__YDown>~~NSE~~</KEY__YDown>		<KEY__YDown>NSD</KEY__YDown>
	<~~KEY__XDown>JH1S</KEY__XDown>~~		<!-- following variables -->
	~~<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>		</Action>
	</syntaxhighlight>		</syntaxhighlight>

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

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

King Galactix at 23:27, 29 July 2026

2026-07-29T23:27:53Z

← Older revision		Revision as of 23:27, 29 July 2026
Line 209:		Line 209:
	* WaitEndMotionSpeed (WEMS) is the speed of WEMEF, which works inversely proportionately.		* WaitEndMotionSpeed (WEMS) is the speed of WEMEF, which works inversely proportionately.
	* EndMotionSpeed is just the general speed of the whole action.		* EndMotionSpeed is just the general speed of the whole action.
	* LandStartFrame is self-explanatory, ~~so most moves have a ‘-1’ value… with exception~~.		* LandStartFrame is self-explanatory, which is the frame when the player starts landing.
	* 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.		* 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>
			<!-- previous variables -->
			<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:		Aerial Attacks follow the same principle but with two new variables:

	* AirCatchStartFrame is the frame where the player can use the Aerial Piledriver.		* 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.		* AddVelocityY increases or decreases the player's upward velocity, depending on whether the value is positive or negative.<syntaxhighlight lang="xml"><Action>
			<!-- previous variables -->
			<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.		Special Moves and Attack Finishers have empty Start/End frames, and any variables below have a value of -1.

King Galactix at 23:22, 29 July 2026

2026-07-29T23:22:35Z

← Older revision		Revision as of 23:22, 29 July 2026
Line 7:		Line 7:
	NSA > NSB > SC > SC2 > SD (YY-XXX) = Donkey 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>		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>		<ActionName>MOVE_A</ActionName>
	<MotionName>MOVE_A</MotionName>		<MotionName>MOVE_A</MotionName>
Line 14:		Line 14:
	<ValidCommon>true</ValidCommon>		<ValidCommon>true</ValidCommon>
	<ValidBerserker>true</ValidBerserker>		<ValidBerserker>true</ValidBerserker>
	<KEY__YDown>~~NSB~~</KEY__YDown>		<KEY__YDown>MOVE_B</KEY__YDown>
	<KEY__XDown>JF</KEY__XDown>		<KEY__XDown>MOVE_C</KEY__XDown>
	<KEY__ADown></KEY__ADown>		<KEY__ADown></KEY__ADown>
	<KEY__Land></KEY__Land>		<KEY__Land></KEY__Land>
Line 99:		Line 99:
	</Action>		</Action>
	</syntaxhighlight>		</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!		** … 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>
	~~Let’s look at some other variables, then. These are fairly important~~.		<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>

	* ValidCommon determines if a move works in Normal Mode		Let’s look at some other variables. These are fairly important.
	* 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~~.		* 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 ~~them for ground moves,~~ and ~~disable them~~ for ~~Aerial moves~~.		* 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">		<syntaxhighlight lang="xml">
	<Action>		<Action>
Line 133:		Line 155:
	* '''KEY__AirCombo''' activates when the player is in the air and when the player makes contact with the enemy hitbox.		* '''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.		* '''KEY__End''' activates a move when inputs are no longer received, meaning that you stop pressing ANYTHING.
			<syntaxhighlight lang="xml">
			<Action>
			<!-- Previous variables -->
			<KEY__YDown>MOVE_B</KEY__YDown> <!-- Press the Button -->
			<KEY__YUp></KEY__YUp> <!-- Release the Button -->
			<KEY__YIng></KEY__YIng> <!-- Hold the Button -->
			<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>
			<!-- Following variables -->
			</Action>
			</syntaxhighlight>

	== Input Registration: ==		== Input Registration: ==
Line 140:		Line 183:
	* 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.		* 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.		* 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">
	The three parameters below allow you to register the input while holding down on a button.		<Action>
			<!-- Previous variables -->
			<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__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__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.		* KEY__IngFrameTIme is how long you hold the button for. The button
			<syntaxhighlight lang="xml">
	The following variables assist with attack speed and more:		<Action>
			<!-- Previous variables -->
			<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.		* WaitEndMotionSpeed (WEMS) is the speed of WEMEF, which works inversely proportionately.

King Galactix at 23:11, 29 July 2026

2026-07-29T23:11:29Z

@@ Line 74: / Line 74: @@
 * 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…
+** 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">
 ** … 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!

King Galactix at 23:08, 29 July 2026

2026-07-29T23:08:28Z

← Older revision		Revision as of 23:08, 29 July 2026
Line 34:		Line 34:
	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.		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>		* 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>		<ActionName>MOVE_A</ActionName>
	<MotionName>MOVE_A</MotionName>		<MotionName>MOVE_A</MotionName>
	</Action></syntaxhighlight>		</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>		* 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>		<ActionName>MOVE_A2</ActionName>
	<MotionName>MOVE_A</MotionName>		<MotionName>MOVE_A</MotionName>
Line 48:		Line 48:
	</Action></syntaxhighlight>		</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.		* 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">		Ground, Straight<syntaxhighlight lang="xml" start="9524"><Action>
	<Action>
	<ActionName>Start_YButtonUP</ActionName>		<ActionName>Start_YButtonUP</ActionName>
	<MotionName>NSA</MotionName>		<MotionName>NSA</MotionName>
Line 55:		Line 54:
	<ValidLevel_Max>99</ValidLevel_Max>		<ValidLevel_Max>99</ValidLevel_Max>
	<!-- Following Variables -->		<!-- Following Variables -->
	</Action>		</Action></syntaxhighlight>Aerial, Hook<syntaxhighlight lang="xml" start="9524"><Action>
	</syntaxhighlight>Aerial, Hook<syntaxhighlight lang="xml" start="9524">
	<Action>
	<ActionName>Start_Air_XButtonDown</ActionName>		<ActionName>Start_Air_XButtonDown</ActionName>
	<MotionName>JCA2</MotionName>		<MotionName>JCA2</MotionName>
Line 63:		Line 60:
	<ValidLevel_Max>99</ValidLevel_Max>		<ValidLevel_Max>99</ValidLevel_Max>
	<!-- Following Variables -->		<!-- Following Variables -->
	</Action>		</Action></syntaxhighlight>Special Attacks<syntaxhighlight lang="xml" line="1"><Action>
	</syntaxhighlight>Special Attacks<syntaxhighlight lang="xml" line="1"> <Action>		<ActionName>Start_Dash_Air_YButtonDown</ActionName>
	<ActionName>Start_Dash_Air_YButtonDown</ActionName>		<MotionName>DC</MotionName>
	<MotionName>DC</MotionName>		<ValidLevel_Min>12</ValidLevel_Min>
	<ValidLevel_Min>12</ValidLevel_Min>		<ValidLevel_Max>99</ValidLevel_Max>
	<ValidLevel_Max>99</ValidLevel_Max>		<!-- Following Variables -->
	<!-- Following Variables -->		</Action></syntaxhighlight>
	</Action></syntaxhighlight>

	== Common Values: ==		== Common Values: ==
Line 78:		Line 74:
	* ValidLevel_Max determines what level a combo is disabled/locked		* 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.		* 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…
	* 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!
	* … 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.		Let’s look at some other variables, then. These are fairly important.

King Galactix at 04:08, 26 July 2026

2026-07-26T04:08:47Z

← Older revision		Revision as of 04:08, 26 July 2026
Line 7:		Line 7:
	NSA > NSB > SC > SC2 > SD (YY-XXX) = Donkey 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>		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>		<ActionName>MOVE_A</ActionName>
	<MotionName>MOVE_A</MotionName>		<MotionName>MOVE_A</MotionName>
Line 34:		Line 34:
	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.		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">		* 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>
	<Action>
	<ActionName>MOVE_A</ActionName>		<ActionName>MOVE_A</ActionName>
	<MotionName>MOVE_A</MotionName>		<MotionName>MOVE_A</MotionName>
	</Action>		</Action></syntaxhighlight>
	</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">		* 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>
	<Action>
	<ActionName>MOVE_A2</ActionName>		<ActionName>MOVE_A2</ActionName>
	<MotionName>MOVE_A</MotionName>		<MotionName>MOVE_A</MotionName>
	</Action>		</Action></syntaxhighlight>
	</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>
	* 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>		<ActionName>MOVE_A</ActionName>
	<MotionName>MOVE_A3</MotionName>		<MotionName>MOVE_A3</MotionName>
	</Action>		</Action></syntaxhighlight>
	</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.		* 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">		Ground, Straight<syntaxhighlight lang="xml" start="9524">
	<Action>		<Action>
	<ActionName>Start_YButtonUP</ActionName>		<ActionName>Start_YButtonUP</ActionName>
Line 62:		Line 56:
	<!-- Following Variables -->		<!-- Following Variables -->
	</Action>		</Action>
	</syntaxhighlight>Aerial, Hook<syntaxhighlight lang="xml~~" line="1~~" start="9524">		</syntaxhighlight>Aerial, Hook<syntaxhighlight lang="xml" start="9524">
	<Action>		<Action>
	<ActionName>Start_Air_XButtonDown</ActionName>		<ActionName>Start_Air_XButtonDown</ActionName>
Line 70:		Line 64:
	<!-- Following Variables -->		<!-- Following Variables -->
	</Action>		</Action>
	</syntaxhighlight>Special Attacks<syntaxhighlight lang="xml"><Action>		</syntaxhighlight>Special Attacks<syntaxhighlight lang="xml" line="1"> <Action>
	<ActionName>Start_Dash_Air_YButtonDown</ActionName>		<ActionName>Start_Dash_Air_YButtonDown</ActionName>
	<MotionName>DC</MotionName>		<MotionName>DC</MotionName>
Line 96:		Line 90:

	* Guard and Avoid (meaning Dodge) are self-explanatory. Enable them for ground moves, and disable them for Aerial moves.		* 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>
			<!-- Variables here -->
			<Guard>true</Guard>
			<Avoid>true</Avoid>
			<!-- Variables there -->
			</Action>
			</syntaxhighlight>

	== Creating Combo Routes: ==		== Creating Combo Routes: ==

King Galactix at 17:09, 23 July 2026

2026-07-23T17:09:30Z

@@ Line 7: / Line 7: @@
 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">
+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>
@@ Line 30: / Line 29: @@
        <LandStartFrame>-1</LandStartFrame>
        <ActionValidHeightMin>-1</ActionValidHeightMin>
-     </Action>
+     </Action></syntaxhighlight>
 == Names: ==
@@ Line 62: / Line 60: @@
        <ValidLevel_Min>1</ValidLevel_Min>
        <ValidLevel_Max>99</ValidLevel_Max>
-       <ValidCommon>true</ValidCommon>
+       <!-- Following Variables -->
      </Action>
 </syntaxhighlight>Aerial, Hook<syntaxhighlight lang="xml" line="1" start="9524">
@@ Line 86: / Line 68: @@
        <ValidLevel_Min>1</ValidLevel_Min>
        <ValidLevel_Max>99</ValidLevel_Max>
-       <ValidCommon>true</ValidCommon>
+       <!-- Following Variables -->
      </Action>
-</syntaxhighlight>Special Attacks
+</syntaxhighlight>Special Attacks<syntaxhighlight lang="xml"><Action>
 == Common Values: ==