Poser - Revision history

Frank The Farmer: Added primary quirks to the poser page

2025-03-06T12:43:50Z

Added primary quirks to the poser page

@@ Line 277: / Line 277: @@
 === Quirks ===
-Quirk animations are stateful animations (for now) that you can have play over the main animation for a pose. The new poser format introduced a shorthand method to writing in your quirk animations in the <code>q.bedrock_quirk()</code> format. The [[Poser#Quirks | old Poser method for quirks]] can be condensed into one line using this function. When using this function, all the properties must be listed in specific order, placed inside of single quotes (the apostrophe key) unless its a number, and separated by commas.
+Quirk animations are typically stateful animations that you can have play over the main animation for a pose. The new poser format introduced primary quirk animations and a shorthand method to writing in your quirk animations in the <code>q.bedrock_quirk()</code> format. The [[Poser#Quirks | old Poser method for quirks]] can be condensed into one line using this function. When using this function, all the properties must be listed in specific order, placed inside of single quotes (the apostrophe key) unless its a number, and separated by commas.
 </br>
 The properties of <code>q.bedrock_quirk</code> must be in the following order:
@@ Line 298: / Line 303: @@
+       ]
 </br>
-==== q.array ====
+===== q.array =====
 You can replace your animation name with the <code>q.array()</code> function to have the quirk pick from a list of animations to play. This can be helpful if you have a lot of quirks that you want to play under one pose. You simply need to put the list of animations inside of the parenthesis, include each animation name inside of single quotes, and separate them with a comma.
 * Example: <code>q.array('quirk_battle_idle', 'quirk_battle_idle2')</code>
@@ Line 307: / Line 312: @@
          "q.bedrock_quirk('blastoise', q.array('quirk_battle_idle', 'quirk_battle_idle2'), 30, 60, 1)"
+       ]
 </br>

Frank The Farmer: Slight formatting again

2025-03-06T12:16:08Z

Slight formatting again

← Older revision		Revision as of 12:16, 6 March 2025
Line 125:		Line 125:

	</br>		</br>
	====== q.array, q.random, and math.random ======		===== q.array, q.random, and math.random =====
	Whenever one of the previously mentioned functions calls the parameter for the animation type, such as <code>'faint'</code>, in the function, you can substitute the value with another function that can call one of multiple animations instead. These 3 functions can help create the illusion of randomized animations if you have enough animations to support the pose, named animation, or quirk.		Whenever one of the previously mentioned functions calls the parameter for the animation type, such as <code>'faint'</code>, in the function, you can substitute the value with another function that can call one of multiple animations instead. These 3 functions can help create the illusion of randomized animations if you have enough animations to support the pose, named animation, or quirk.

Frank The Farmer: Included some new functions for calling animations

2025-03-06T12:14:35Z

Included some new functions for calling animations

@@ Line 125: / Line 125: @@
 </br>
 === Conditions ===
 You can expand the amount of animations a Pokémon can have and when they should be played by using <code>conditions</code>. Conditions are what allow for battle animations despite the <code>standing</code> and <code>battle-idle</code> poses both using the <code>"STAND"</code> pose type. Typically, if you want different animations using the same pose types, then you must set one pose's condition to true, and the other pose's matching condition to false. You can mix and match these conditions to make something like an animation that only plays in battle, if it is raining while the sun is setting.

Frank The Farmer: Slight formatting

2025-03-06T11:16:47Z

Slight formatting

← Older revision		Revision as of 11:16, 6 March 2025
Line 124:		Line 124:
	"physical": "q.bedrock_primary('blastoise', 'physical', q.curve('symmetrical_wide'))",		"physical": "q.bedrock_primary('blastoise', 'physical', q.curve('symmetrical_wide'))",

			</br>
	=== Conditions ===		=== Conditions ===
	You can expand the amount of animations a Pokémon can have and when they should be played by using <code>conditions</code>. Conditions are what allow for battle animations despite the <code>standing</code> and <code>battle-idle</code> poses both using the <code>"STAND"</code> pose type. Typically, if you want different animations using the same pose types, then you must set one pose's condition to true, and the other pose's matching condition to false. You can mix and match these conditions to make something like an animation that only plays in battle, if it is raining while the sun is setting.		You can expand the amount of animations a Pokémon can have and when they should be played by using <code>conditions</code>. Conditions are what allow for battle animations despite the <code>standing</code> and <code>battle-idle</code> poses both using the <code>"STAND"</code> pose type. Typically, if you want different animations using the same pose types, then you must set one pose's condition to true, and the other pose's matching condition to false. You can mix and match these conditions to make something like an animation that only plays in battle, if it is raining while the sun is setting.

Frank The Farmer: Slight introduction to molang conditions in the conditions section

2025-03-06T11:15:11Z

Slight introduction to molang conditions in the conditions section

@@ Line 125: / Line 125: @@
 === Conditions ===
-You can expand the amount of animations a Pokémon can have and when they should be played by using <code>conditions</code>. Conditions are what allow for battle animations despite the <code>standing</code> and <code>battle-idle</code> poses both using the <code>"STAND"</code> pose type. Typically, if you want different animations using the same pose types, then you must set one pose's condition to true, and the other pose's matching condition to false. You can mix and match these conditions to make something like an animation that only plays in battle, if it is raining while the sun is setting. </br>
+You can expand the amount of animations a Pokémon can have and when they should be played by using <code>conditions</code>. Conditions are what allow for battle animations despite the <code>standing</code> and <code>battle-idle</code> poses both using the <code>"STAND"</code> pose type. Typically, if you want different animations using the same pose types, then you must set one pose's condition to true, and the other pose's matching condition to false. You can mix and match these conditions to make something like an animation that only plays in battle, if it is raining while the sun is setting.
-List of Currently Implemented Conditions:
+</br>
 * <code>"isBattle"</code>: The Pokémon must be in a battle.
 * <code>"isTouchingWater"</code>: The Pokémon must be touching water. Not necessarily underwater.
@@ Line 156: / Line 183: @@
 </br>
 === Transformed Parts ===
 This function allows you to transform parts of the model when the Pokémon is in a certain pose. You can change the location, rotation, and visibility of bones for each pose. This allows you to make some slight adjustments to an in-game animation without having to edit the animation itself. While there aren't many examples of this function, it's most common use is to hide model parts when a Pokémon is not in its battle idle. This is the case with Rillaboom and its drum.

Frank The Farmer: Updated placeholder animation section and included examples. Curse you Paul!

2025-03-06T10:25:16Z

Updated placeholder animation section and included examples. Curse you Paul!

← Older revision		Revision as of 10:25, 6 March 2025
Line 262:		Line 262:

	=== Placeholder Animations ===		=== Placeholder Animations ===
	The new poser allows creators to use the placeholder animations which the JSON poser could not access before. These placeholder animations are based on the body type or limb features of the Pokémon. Each placeholder features a very simple animation that swings a limb back and forth. ~~For now, you'll have to figure out how to configure these yourself lol</br>~~		The new poser allows creators to use the placeholder animations which the JSON poser could not access before. These placeholder animations are based on the body type or limb features of the Pokémon. Each placeholder features a very simple animation that swings a limb back and forth.

	~~Here~~ is a list of ~~all the Placeholder~~ animations:		</br>
	* ~~<code>[https://gitlab.com/cable-mc/cobblemon/-/blob/main/common/src/main/kotlin/com/cobblemon/mod/common/client/render/models/blockbench/PoseableEntityModel.kt#L172 "~~q.quadruped_walk~~()"]</code>~~ - A basic walk animation for Pokémon with 4 legs		Below is a list of current placeholder animations, their default values, and an example you can copy into your animations list directly:
	* <code>~~[https://gitlab.com/cable-mc/cobblemon/-/blob/main/common/src/main/kotlin/com/cobblemon/mod/common/client/render/models/blockbench/PoseableEntityModel.kt#L192~~ "q.~~biped_walk~~()"]</code> - A basic walking animation for Pokémon who stand on 2 legs.		* '''q.quadruped_walk''' - A basic walk animation for Pokémon with 4 legs.</br>
	* <code>~~[https://gitlab.com/cable-mc/cobblemon/-/blob/main/common/src/main/kotlin/com/cobblemon/mod/common/client/render/models/blockbench/PoseableEntityModel.kt#L208~~ "q.~~bimanual_swing~~()"]</code> - A basic arm swinging animation for Pokémon with 2 arms that usually stand on 2 legs.		<code>"q.quadruped_walk(0.66, 1.4, 'leg_front_left', 'leg_front_right', 'leg_back_left', 'leg_back_right')"</code>
	* <code>~~[https://gitlab.com/cable-mc/cobblemon/-/blob/main/common/src/main/kotlin/com/cobblemon/mod/common/client/render/models/blockbench/PoseableEntityModel.kt#L224~~ "q.~~sine_wing_flap~~()"]</code> - A basic wing flap animation for a pair of wings on a Pokémon.
			</br>
			* '''q.biped_walk''' - A basic walking animation for Pokémon who stand on 2 legs.</br>
			<code>"q.biped_walk(0.66, 1.4, 'leg_left', 'leg_right')"</code>

			</br>
			* '''q.bimanual_swing''' - A basic arm swinging animation for Pokémon with 2 arms that usually stand on 2 legs.
			<code>"q.bimanual_swing(0.66, 1.4, 'arm_left', 'arm_right')"</code>

			</br>
			* '''q.sine_wing_flap''' - A basic wing flap animation for a pair of wings on a Pokémon. This animation allows you to control a few more aspects of the specified bones. It's important to note what axis these "wings" should be rotating in to give the illusion of flapping. So be sure to reference your model.
			<code>"q.sine_wing_flap(<abbr title="Multiplier for the amplitude value. How far the wings will flap">0.9</abbr>, <abbr title="Multiplier for the period value. How fast the wings will flap">0.9</abbr>, <abbr title="Vertical shift value. Radian value that the wing pair will be offset by.">25</abbr>, <abbr title="The x, y, or z axis of the bone that shall be rotated by this animation.">'z'</abbr>, <abbr title="The left wing to be animated">'wing_left'</abbr>, <abbr title="The right wing to be animated">'wing_right'</abbr>)"</code>

			</br>
			With the exception of the wing flap placeholder, the first value mentioned in these functions controls how fast the limbs will swing, also called the period value. The second value is the amplitude, or how far a limb will swing. These are both multiplier values to a cosine wave that the author of this post can't seem to find at this moment. Be sure to tune these values if the limbs don't work with the defaults.

	</br>		</br>

Frank The Farmer: Data update for example poser

2025-03-06T06:17:41Z

Data update for example poser

← Older revision		Revision as of 06:17, 6 March 2025
Line 283:		Line 283:
	* Blink animations are not applied to the sleep pose. This is because you don't blink when you sleep!		* Blink animations are not applied to the sleep pose. This is because you don't blink when you sleep!
	{		{
	"portraitScale": ~~2.3~~,		"portraitScale": 1,
	"portraitTranslation": [-0.1, 0~~.58~~, 0],		"portraitTranslation": [0, 0, 0],
	"profileScale": ~~0.75~~,		"profileScale": 1,
	"profileTranslation": [0, 0~~.68~~, 0],		"profileTranslation": [0, 0, 0],
	"animations": {		"animations": {
	"faint": "q.bedrock_primary('riolu', 'faint', q.curve('one'))",		"faint": "q.bedrock_primary('riolu', 'faint', q.curve('one'))",

Blob: Blob moved page New Poser to Poser without leaving a redirect

2024-12-12T11:59:02Z

Blob moved page New Poser to Poser without leaving a redirect

← Older revision	Revision as of 11:59, 12 December 2024
(No difference)

Frank The Farmer: Expanded on bedrock_primary function information

2024-12-12T10:48:50Z

Expanded on bedrock_primary function information

← Older revision		Revision as of 10:48, 12 December 2024
Line 92:		Line 92:
	===== q.bedrock_primary =====		===== q.bedrock_primary =====
	The function <code>q.bedrock_primary()</code> allows you to assign a primary animation to an animation type. <code>Primary animations</code> are meant to take control of the entire model to play its animation and will clear any previous animations it was doing. An example would be a Pokémon's physical attack animation. When a Pokémon uses a physical move, it should clear the battle idle animation and play its physical animation instead. These animations often move the whole body and many of its limbs. When the physical animation is done, it returns control of the model to the battle idle after the physical animation has finished and should play a short transition animation in between.		The function <code>q.bedrock_primary()</code> allows you to assign a primary animation to an animation type. <code>Primary animations</code> are meant to take control of the entire model to play its animation and will clear any previous animations it was doing. An example would be a Pokémon's physical attack animation. When a Pokémon uses a physical move, it should clear the battle idle animation and play its physical animation instead. These animations often move the whole body and many of its limbs. When the physical animation is done, it returns control of the model to the battle idle after the physical animation has finished and should play a short transition animation in between.

	</br>		</br>
			<code>q.bedrock_primary</code> comes with a couple of extra properties and they should be written in the following order:
			# group: <code>'blastoise'</code> - The animation JSON that the game will search for the following animation. This should always be the name of a Pokémon.
			# animation: <code>'status'</code> - The animation the game will call from the previously mentioned animation JSON. Primary animations are usually your attack animations or faints, but you can assign it to other named animations if desired.
			# (optional) excluded labels: <code>'look'</code> - Exclusive labeled animations that wont get overwritten by this primary animation. The only reasonable use of excluded labels is to exclude the look animation from being overwritten. This is so they can keep looking at a target when using an animation.
			# curve: <code>'q.curve('symmetrical_wide')'</code> - The interpolation curve that this primary animation will use to transition to and from the pose it is written under.

	Since Primary animations behave in a similar way to swapping poses, they can use special transition animation types via the <code>q.curve</code> property written within its sub properties. These provide different types of smoothness to the interpolation and will be explained in the next section.
	</br>		</br>
			Since Primary animations behave in a similar way to swapping poses, they can use special interpolation curve types via the <code>q.curve</code> property written within its sub properties. These provide different types of smoothness to the interpolation and will be explained in the next section.

	Below is an example of the 4 primary ~~animation~~ in the poser:		</br>
			Below is an example of the 4 common primary animations in the poser:
	"faint": "q.bedrock_primary('blastoise', 'faint', q.curve('one'))",		"faint": "q.bedrock_primary('blastoise', 'faint', q.curve('one'))",
	"physical": "q.bedrock_primary('blastoise', 'physical', q.curve('symmetrical_wide'))",		"physical": "q.bedrock_primary('blastoise', 'physical', q.curve('symmetrical_wide'))",
	"special": "q.bedrock_primary('blastoise', 'special', q.curve('symmetrical_wide'))",		"special": "q.bedrock_primary('blastoise', 'special', q.curve('symmetrical_wide'))",
	"status": "q.bedrock_primary('blastoise', 'status', q.curve('symmetrical_wide'))"		"status": "q.bedrock_primary('blastoise', 'status', 'look', q.curve('symmetrical_wide'))"

	</br>		</br>
Line 116:		Line 123:
	"faint": "q.bedrock_primary('blastoise', 'faint', q.curve('one'))",		"faint": "q.bedrock_primary('blastoise', 'faint', q.curve('one'))",
	"physical": "q.bedrock_primary('blastoise', 'physical', q.curve('symmetrical_wide'))",		"physical": "q.bedrock_primary('blastoise', 'physical', q.curve('symmetrical_wide'))",



	=== Conditions ===		=== Conditions ===

Frank The Farmer: Expanded information on some existing properties. Updated conditions

2024-12-12T07:00:28Z

Expanded information on some existing properties. Updated conditions

← Older revision		Revision as of 07:00, 12 December 2024
Line 1:		Line 1:
	~~Under construction. Dont look or else!~~

	{{TOC\|right}}		{{TOC\|right}}
	== Preface ==		== Preface ==
	The ~~new~~ <code>poser</code> JSON controls all the animations of a Pokémon just as the old [[Poser]] did. It contains the same information for when the Pokémon will perform certain animations, but has received many requested upgrades. Some of these upgrades include multi-bone look animations, support for move animations, and even selecting from a pool of animations for quirks. Functionality of the new Poser will always be maintained and should let addon creators have the same options as the [https://gitlab.com/cable-mc/cobblemon/-/blob/main/common/src/main/kotlin/com/cobblemon/mod/common/client/render/models/blockbench/pokemon/gen1/SquirtleModel.kt hard-coded Kotlin Posers.]		The <code>poser</code> JSON controls all the animations of a Pokémon just as the old [[Poser]] did. It contains the same information for when the Pokémon will perform certain animations, but has received many requested upgrades. Some of these upgrades include multi-bone look animations, support for move animations, and even selecting from a pool of animations for quirks. Functionality of the new Poser will always be maintained and should let addon creators have the same options as the [https://gitlab.com/cable-mc/cobblemon/-/blob/main/common/src/main/kotlin/com/cobblemon/mod/common/client/render/models/blockbench/pokemon/gen1/SquirtleModel.kt hard-coded Kotlin Posers.]

	</br>		</br>
	== Poser Properties ==		== Poser Properties ==
	Before breaking down each section of the ~~new~~ Poser file, let's take a look at all its different properties and how to use them. This section includes all of the different functions of the poser, any configurable options for said function, and how to write each function. You will notice that the poser now includes something in the format of <code>q.<function></code>. These are molang functions which allow you to do many new things. The q stands for query and its just part of the standard format for these new functions. Some functions can even go inside of other functions. It's not terribly complicated once you read what each one does. They allow addon creators to do many things they couldn't before!		Before breaking down each section of the Poser file, let's take a look at all its different properties and how to use them. This section includes all of the different functions of the poser, any configurable options for said function, and how to write each function. You will notice that the poser now includes something in the format of <code>q.<function></code>. These are molang functions which allow you to do many new things. The q stands for query and its just part of the standard format for these new functions. Some functions can even go inside of other functions. It's not terribly complicated once you read what each one does. They allow addon creators to do many things they couldn't before!

	</br>		</br>
Line 37:		Line 35:
	</br>		</br>
	=== Poses & Animations ===		=== Poses & Animations ===
	There's a handful of Pose types and Animation types that you can make animations for. <code>Poses</code> are the states a Pokémon is in, like idle or moving. Poses are for assigning animations like your ground idles, ground walks, water idles, etc. The <code>animation types</code> are the different events in battles that you can assign animations to for each Pokémon. ~~Animation types would include your~~ faints, cries, and attack animations. Below is a list of currently available Animation types and Poses to choose from. </br>		There's a handful of Pose types and Animation types that you can make animations for. <code>Poses</code> are the states a Pokémon is in, like idle or moving. Poses are for assigning animations like your ground idles, ground walks, water idles, etc. The <code>animation types</code> are the different events in battles that you can assign animations to for each Pokémon.

			For the sake of clarity, you should always refer to animations like faints, cries, or physicals as '''Named Animations'''. This is to help everyone distinguish them from the animations that are applied to poses. This distinction is important because you can assign both <code>animations</code> and <code>namedAnimations</code> to a pose. This is to allow you to assign different cries, faints, or attack animations to different poses like your floating or flying poses. This allows for water attack animations if you make the animation to support it. This process will be detailed later. Below is a list of currently available Named Animation types and Poses to choose from. </br>


	==== Animations ====		==== Animations & Named Animations ====
	* '''faint''': <code>animation.<pokemon>.faint</code> - The animation that plays when a Pokémon faints.		* '''faint''': <code>animation.<pokemon>.faint</code> - The animation that plays when a Pokémon faints.
	* '''cry''': <code>animation.<pokemon>.cry</code> - The animation that plays when a Pokémon is called out or when it starts battle.		* '''cry''': <code>animation.<pokemon>.cry</code> - The animation that plays when a Pokémon is called out or when it starts battle.
Line 66:		Line 66:

	</br>		</br>
	==== q.bedrock ====		==== Basic Animation Calling Functions ====
			Below are the 3 methods to call a <code>Pose</code> or <code>namedAnimation</code> animation. Each of them serve a purpose in layering animations on the Pokémon. <code>Pose</code> animations must always use <code>q.bedrock()</code> to serve as the base animation that can be overwritten by other animations when called. <code>NamedAnimations</code> can either use <code>q.bedrock_stateful()</code> to layer over the base animation or use <code>q.bedrock_primary()</code> to overwrite the base animation while it is playing. The default function used in each named animation type can be changed if your animation supports it. If you want the cry to overwrite rather than layer, then just be sure to animate it properly.

			</br>
			===== q.bedrock =====
	The <code>q.bedrock()</code> function is the familiar animation calling format from the [[Old_Poser \| old poser]] which got converted into a molang function. It's the same thing as before, just in a new look. You are still just listing your Pokémon and then the animation in the parenthesis. This function is mainly used to assign poses their animations. These animations are meant to be overwritten by Primary or Stateful animations whenever convenient.</br>		The <code>q.bedrock()</code> function is the familiar animation calling format from the [[Old_Poser \| old poser]] which got converted into a molang function. It's the same thing as before, just in a new look. You are still just listing your Pokémon and then the animation in the parenthesis. This function is mainly used to assign poses their animations. These animations are meant to be overwritten by Primary or Stateful animations whenever convenient.</br>
	Below is an example of the <code>q.bedrock</code> function assigning a walk animation to the <code>"WALK"</code> pose type:		Below is an example of the <code>q.bedrock</code> function assigning a walk animation to the <code>"WALK"</code> pose type:
Line 77:		Line 81:

	</br>		</br>
	==== q.bedrock_stateful ====		===== q.bedrock_stateful =====
	The function <code>q.bedrock_stateful()</code> allows you to assign a stateful animation to an animation type. <code>Stateful animations</code> are meant to animate just a few bones of the Pokémon and get overlaid on the current pose. An example would be cries only animating the mouth or head of the Pokémon. A stateful animation won't take control of the whole model to play its animation.		The function <code>q.bedrock_stateful()</code> allows you to assign a stateful animation to an animation type. <code>Stateful animations</code> are meant to animate just a few bones of the Pokémon and get overlaid on the current pose. An example would be cries only animating the mouth or head of the Pokémon. A stateful animation won't take control of the whole model to play its animation.
	</br>		</br>
Line 86:		Line 90:

	</br>		</br>
	==== q.bedrock_primary ====		===== q.bedrock_primary =====
	The function <code>q.bedrock_primary()</code> allows you to assign a primary animation to an animation type. <code>Primary animations</code> are meant to take control of the entire model to play its animation and will clear any previous animations it was doing. An example would be a Pokémon's physical attack animation. When a Pokémon uses a physical move, it should clear the battle idle animation and play its physical animation instead. These animations often move the whole body and many of its limbs. When the physical animation is done, it returns control of the model to the battle idle after the physical animation has finished and should play a short transition animation in between.		The function <code>q.bedrock_primary()</code> allows you to assign a primary animation to an animation type. <code>Primary animations</code> are meant to take control of the entire model to play its animation and will clear any previous animations it was doing. An example would be a Pokémon's physical attack animation. When a Pokémon uses a physical move, it should clear the battle idle animation and play its physical animation instead. These animations often move the whole body and many of its limbs. When the physical animation is done, it returns control of the model to the battle idle after the physical animation has finished and should play a short transition animation in between.
	</br>		</br>
Line 100:		Line 104:

	</br>		</br>
	==== q.curve ====		====== q.curve ======
	The function <code>q.curve()</code> is a sub function for <code>q.bedrock_primary()</code> which allows the animation to interpolate back into the main pose. This allows the transition between animations to behave similarly to linear keyframes and smooth keyframes when animating.		The function <code>q.curve()</code> is a sub function for <code>q.bedrock_primary()</code> which allows the animation to interpolate back into the main pose. This allows the transition between animations to behave similarly to linear keyframes and smooth keyframes when animating.
	</br>		</br>
Line 122:		Line 126:
	* <code>"isBattle"</code>: The Pokémon must be in a battle.		* <code>"isBattle"</code>: The Pokémon must be in a battle.
	* <code>"isTouchingWater"</code>: The Pokémon must be touching water. Not necessarily underwater.		* <code>"isTouchingWater"</code>: The Pokémon must be touching water. Not necessarily underwater.
	* <code>"~~isTouchingWaterOrRain~~"</code>: The Pokémon must be touching water or rain. Again, not necessarily underwater.		* <code>"isInWaterOrRain"</code>: The Pokémon must be touching water or in rain. Again, not necessarily underwater.
	* <code>"~~isSubmergedInWater~~"</code>: The Pokémon must be underwater. The red line on the hitbox must be below the surface.		* <code>"isUnderWater"</code>: The Pokémon must be underwater. The red line on the hitbox must be below the surface.
	* <code>"isStandingOnRedSand"</code>: The Pokémon must be standing on red sand.		* <code>"isStandingOnRedSand"</code>: The Pokémon must be standing on red sand.
	* <code>"isStandingOnSand"</code>: The Pokémon must be standing on sand		* <code>"isStandingOnSand"</code>: The Pokémon must be standing on sand