Old Poser - Revision history

Frank The Farmer: Old Poser update

2024-12-12T05:24:19Z

Old Poser update

← Older revision		Revision as of 05:24, 12 December 2024
Line 1:		Line 1:
	{{TOC\|right}}		{{TOC\|right}}
	== Preface ==		== Preface ==
			This page is for the now outdated poser json format. There is still backwards support for it in the mod, but there is no reason you should still be using it today. Please use the current [[Poser]] wiki page.

	The <code>poser</code> JSON controls all the animations of a Pokémon. It contains information on when the Pokémon will perform certain animations. You can set your Pokémon to only ever perform one animation if you’d like, or you can give it different animations for just about every action it performs! It can even be used to adjust certain properties of an animation so you don't have to edit the animation itself.		The <code>poser</code> JSON controls all the animations of a Pokémon. It contains information on when the Pokémon will perform certain animations. You can set your Pokémon to only ever perform one animation if you’d like, or you can give it different animations for just about every action it performs! It can even be used to adjust certain properties of an animation so you don't have to edit the animation itself.

Frank The Farmer: Frank The Farmer moved page Poser to Old Poser: Outdated json. The new poser page will become the standard going forward and should no longer be called "New_Poser"

2024-12-12T05:20:12Z

Frank The Farmer moved page Poser to Old Poser: Outdated json. The new poser page will become the standard going forward and should no longer be called "New_Poser"

← Older revision	Revision as of 05:20, 12 December 2024
(No difference)

Apion: Remove test

2024-11-13T10:59:54Z

Remove test

← Older revision		Revision as of 10:59, 13 November 2024
Line 403:		Line 403:
	}		}
	}		}

	~~[[File:StatUpAegi.gif]]~~
	{{Addon Creation}}		{{Addon Creation}}

Apion: Test gif support

2024-11-13T10:59:07Z

Test gif support

← Older revision		Revision as of 10:59, 13 November 2024
Line 404:		Line 404:
	}		}

			[[File:StatUpAegi.gif]]
	{{Addon Creation}}		{{Addon Creation}}

Frank The Farmer: /* Poser File Example */

2023-11-07T22:58:30Z

Poser File Example

← Older revision		Revision as of 22:58, 7 November 2023
Line 237:		Line 237:
	{		{
	"name": "blink",		"name": "blink",
	"animations": ["bedrock(~~charizard~~, blink)"]		"animations": ["bedrock(starly, blink)"]
	}		}
	]		]

Blob: navbox

2023-10-14T11:37:28Z

navbox

← Older revision		Revision as of 11:37, 14 October 2023
Line 403:		Line 403:
	}		}
	}		}

			{{Addon Creation}}

Frank The Farmer at 12:18, 11 October 2023

2023-10-11T12:18:35Z

← Older revision		Revision as of 12:18, 11 October 2023
Line 116:		Line 116:

	=== Advanced Poser Functions And When to Use Them ===		=== Advanced Poser Functions And When to Use Them ===
	Posers can do a lot more than just assign an animation to a pose. Certain things can be tweaked in the poser to ~~help~~ make your Pokémon livelier in game. If you enjoy making many different animations for Pokémon, then this section will help you implement them in game. Using these advanced feature can help you make custom Pokémon that are on the same level of quality as the official Pokémon!		Posers can do a lot more than just assign one animation to a pose. Certain things can be tweaked in the poser to make your Pokémon livelier in game. If you enjoy making many different animations for Pokémon, then this section will help you implement them in game. Using these advanced feature can help you make custom Pokémon that are on the same level of quality as the official Pokémon!

			Remember that you can have an unzipped copy of your addon as a resourcepack in the game for easier editing. Since the poser file is a part of the resources of an addon, it can be refreshed in game by pressing <code>F3 + T</code>. This reloads all your resourcepacks and allows you to see the changes you've made to the poser only if the poser you are editing is in the resourcepack folder. '''It is highly recommended to use unzipped folders to test addon stuff when implementing them into the game!''' You can simply make your file edits, save the file, and then refresh your resourcepack in game to see the changes immediately!
			</br>
	==== Layered Animations ====		==== Layered Animations ====
	Layered animations are two or more animations that are listed together in your <code>animations</code> list. The most common example would be adding the <code>look</code> animation on top of your <code>ground_idle</code> animation for your standing pose. You're able to list more than two animations and your main limit would be running out of bones to animate.		Layered animations are two or more animations that are listed together in your <code>animations</code> list. The most common example would be adding the <code>look</code> animation on top of your <code>ground_idle</code> animation for your standing pose. You're able to list more than two animations and your main limit would be running out of bones to animate.
Line 222:		Line 225:
	"profileScale": 1.1,		"profileScale": 1.1,
	"profileTranslation": [ -0.05, 0.15, 0 ],		"profileTranslation": [ -0.05, 0.15, 0 ],
	"faint": "bedrock(starly, faint)",		"faint": "bedrock(starly, faint, true)",
			"cry": "bedrock(starly, cry)",
	"poses": {		"poses": {
			"battle-idle": {
			"poseName": "battle-idle",
			"transformTicks": 10,
			"poseTypes": ["STAND"],
			"isBattle": true,
			"animations": ["bedrock(starly, battle_idle)"],
			"quirks": [
			{
			"name": "blink",
			"animations": ["bedrock(charizard, blink)"]
			}
			]
			},
	"standing": {		"standing": {
	"poseName": "standing",		"poseName": "standing",
Line 233:		Line 250:
	"PROFILE"		"PROFILE"
	],		],
			"isBattle": false,
	"animations": [		"animations": [
	"bedrock(starly, ground_idle)"		"bedrock(starly, ground_idle)"

Frank The Farmer: /* Transformed Parts */

2023-10-11T11:59:54Z

Transformed Parts

← Older revision		Revision as of 11:59, 11 October 2023
Line 170:		Line 170:
	A great use for location and rotation transformation is to adjust shoulder animations. You don't have to account for the model location on the player shoulder when making the animation. If it doesn't line up in the game, you can move the whole model using this function.		A great use for location and rotation transformation is to adjust shoulder animations. You don't have to account for the model location on the player shoulder when making the animation. If it doesn't line up in the game, you can move the whole model using this function.

	The visibility transformation allows you to hide a specific bone in the model when the Pokémon is currently in a pose. This can be used to hide certain bones if needed. This allows you to do things like making Rillaboom use its drum for its battle idle. It also allows Typhlosion to have its flames ignited only during battle. Something to keep in mind is that if you want a bone to be visible only during battle, then you must set this bone as invisible for all other poses. This is why <code>transformedParts</code> is written under every pose in the poser file breakdown.		The visibility transformation allows you to hide a specific bone in the model when the Pokémon is currently in a pose. This can be used to hide certain bones if needed. This allows you to do things like making Rillaboom use its drum for its battle-idle. It also allows Typhlosion to have its flames ignited only during battle. Something to keep in mind is that if you want a bone to be visible only during battle, then you must set this bone as invisible for all other poses. This is why <code>transformedParts</code> is written under every pose in the poser file breakdown.

	Below is an example of all the transformed part properties being used. This is mostly a demonstration of your options when using this function. If this example was applied in game, Charizard's wings would be detached from its body, but only the left wing would be invisible. Realistically, you would never want to do something like that.</br>		Below is an example of all the transformed part properties being used. This is mostly a demonstration of your options when using this function. If this example was applied in game, Charizard's wings would be detached from its body, but only the left wing would be invisible. Realistically, you would never want to do something like that.</br>

	"transformedParts": [		"<abbr title="This property will allow you to manipulate the model parts without having to edit things in blockbench! You can select a bone from the model, and edit this bone specifically for this pose.">transformedParts</abbr>": [
	{		{
	"part": "wing_right",		"<abbr title="Here, we are selecting a bone from the model. In this case, it's charizard's right wing.">part</abbr>": "<abbr title="The bone that will be manipulated. The next 3 lines can change this bone specifically for charizard's pose.">wing_right</abbr>",
	"position": [10, 0, 0],		"<abbr title="This property will change the bone's position. The following set of numbers can change its location on the x, y, and z axis.">position</abbr>": [<abbr title="The xyz axis values that will be applied to the bone. In this case, the bone will move 10 units on the x axis. This would be 10 units to the right if you were looking at charizard.">10, 0, 0</abbr>],
	"rotation": [0, 0, 0],		"<abbr title="This property will change the bone's rotation. The following set of numbers can change its rotation in degrees on the x, y, and z axis. You will likely never have to rotate a bone for a pose, so these values will be left blank. This part of the example is merely to show you your options.">rotation</abbr>": [<abbr title="We don't actually want to rotate charizard's wings, so these values will be left at zero. If you don't want to use this rotation property at all, you can simply remove this one line!">0, 0, 0</abbr>],
	"isVisible": true		"<abbr title="This property controls whether or not the selected bone will be visible for this pose. Note that if you want a bone to be visible just for 1 pose, then it must be set as invisible for all other poses.">isVisible</abbr>": <abbr title="Here, we are setting charizard's right wing to be visible.">true</abbr>
	},		},
	{		{
	"part": "wing_left",		"<abbr title="Here, we are selecting a second bone from the model. In this case, it's charizard's left wing.">part</abbr>": "<abbr title="The bone that will be manipulated. The next 3 lines can change this bone specifically for charizard's pose.">wing_left</abbr>",
	"position": [-10, 0, 0],		"<abbr title="This property will change the bone's position. The following set of numbers can change its location on the x, y, and z axis.">position</abbr>": [<abbr title="The xyz axis values that will be applied to the bone. In this case, the bone will move -10 units on the x axis. This would be 10 units to the left if you were looking at charizard.">-10, 0, 0</abbr>],
	"rotation": [0, 0, 0],		"<abbr title="This property will change the bone's rotation. The following set of numbers can change its rotation in degrees on the x, y, and z axis. You will likely never have to rotate a bone for a pose, so these values will be left blank. This part of the example is merely to show you your options.">rotation</abbr>rotation</abbr>": [<abbr title="We don't actually want to rotate charizard's wings, so these values will be left at zero. If you don't want to use this rotation property at all, you can simply remove this one line!">0, 0, 0</abbr>],
	"isVisible": false		"<abbr title="This property controls whether or not the selected bone will be visible for this pose. Note that if you want a bone to be visible just for 1 pose, then it must be set as invisible for all other poses.">isVisible</abbr>": <abbr title="Here, we are setting charizard's left wing to be invisible.">false</abbr>
	}		}
	]		]

Frank The Farmer: /* Quirks */

2023-10-11T11:50:26Z

Quirks

← Older revision		Revision as of 11:50, 11 October 2023
Line 141:		Line 141:

	==== Quirks ====		==== Quirks ====
	Quirk animations are extra animations that you can have play over the main animation list. What makes them different from the previous animation overwrite function is that these quirks can have extra properties applied to them. You can make them loop a certain number of times and include timers for these quirks. The most common example of a quirk animation would be the blink animations.		Quirk animations are extra animations that you can have play over the main animation list. What makes them different from the previous animation overwrite function is that these quirks can have extra properties applied to them. You can make them loop a certain number of times and include timers for these quirks. The most common example of a quirk animation would be the blink animations. By default, a quirk animation should play once every 8-20 seconds!

	Making a quirk in your poser file would largely depend on an animator making these quirky little animations to play in game. You can do more than just blinking animations. You can make a Pokémon roar, sneeze, or dance and have it play as a quirk for its standing pose or any other pose. A timer can then be applied to these quirk animations so you could end up with something like charizard doing a roar every 30-60 seconds when its idle. It's a very flexible sub system for animations that is only limited by your creativity.		Making a quirk in your poser file would largely depend on an animator making these quirky little animations to play in game. You can do more than just blinking animations. You can make a Pokémon roar, sneeze, or dance and have it play as a quirk for its standing pose or any other pose. A timer can then be applied to these quirk animations so you could end up with something like charizard doing a roar every 30-60 seconds when its idle. It's a very flexible sub system for animations that is only limited by your creativity.

			Here is a list of properties that can affect quirks:
			"loopTimes": Int = 1 // The number of times the animation should play for the quirk
			"minSecondsBetweenOccurrences": Float = 8 // The decimal-friendly number of seconds that is the
			minimum between the quirk playing once and it playing a second time
			"maxSecondsBetweenOccurrences": Float = 30 // What do you think
			"animations": List<Animation> = [] // The list of animations to play (together) when this quirk runs
			"name": String // The name of the quirk
			</br>
	Below is an example of a modified quirk animation. What this will do is eventually make charizard play the blink animation 5 times in a row. Then after the animation plays, an 8-20 second timer begins to play this quirk again. The quirk timer starts after the quirk animations end.</br>		Below is an example of a modified quirk animation. What this will do is eventually make charizard play the blink animation 5 times in a row. Then after the animation plays, an 8-20 second timer begins to play this quirk again. The quirk timer starts after the quirk animations end.</br>

	"quirks": [		"<abbr title="This property allows you to play other animations over the main list of animations for this pose. The most common type of quirk animations are blinks, but you can apply any animation you wish as a quirk.">quirks</abbr>": [
	{		{
	"name": "blink",		"<abbr title="Here we are defining the name of this quirk">name</abbr>": "<abbr title="The name of this quirk will simply be called 'blink'.">blink</abbr>",
	"loopTimes": 5,		"<abbr title="The number of times the animation should play for the quirk. By default, this value is 1.">loopTimes</abbr>": <abbr title="For this example, we will let the blink animation play 5 times. After the blink plays 5 times, it will then start a timer before it can play again.">5</abbr>,
	"minSecondsBetweenOccurrences": 8,		"<abbr title="The decimal-friendly number of seconds that is the minimum between the quirk playing once and it playing a second time. Default value is 8.">minSecondsBetweenOccurrences</abbr>": <abbr title="After 8 seconds, there is a chance that this quirk animation will play.">8</abbr>,
	"maxSecondsBetweenOccurrences": 20,		"<abbr title="The decimal-friendly number of seconds that is the maximum between the quirk playing once and it playing a second time. Default value is 30.">maxSecondsBetweenOccurrences</abbr>": <abbr title="It will take 20 seconds at most for the quirk animation to play again.">20</abbr>,
	"animations": ["bedrock(charizard, blink)"]		"<abbr title="Here, you are going to list the animation that you want to play as a quirk. Given the data of the previous lines, this animation will play 5 times every 8-20 seconds.">animations</abbr>": ["<abbr title="This points towards charizard's blink animation">bedrock(charizard, blink)</abbr>"]
	},		}
	</br>		</br>

Frank The Farmer: /* Animation Overwrites */

2023-10-11T11:41:03Z

Animation Overwrites

← Older revision		Revision as of 11:41, 11 October 2023
Line 132:		Line 132:

	==== Animation Overwrites ====		==== Animation Overwrites ====
	This function is mostly used for cases where you want an animation to be played exclusively for certain situations. You simply write <code>, true</code> after your animation type in your animations list. The most common ~~case~~ for this function would be writing it into your faint so the faint animation should always be playing when a Pokémon faints. Sometimes animations don't change properly and this can fix it most of the time.		This function is mostly used for cases where you want an animation to be played exclusively for certain situations. You simply write <code>, true</code> after your animation type in your animations list. The most common use for this function would be writing it into your faint so the faint animation should always be playing when a Pokémon faints. Sometimes animations don't change properly and this can fix it most of the time.

	Below is an example of the faint using this overwrite function. What's going to happen in game is that when charizard faints, it will always play the faint animation over other animations it was already doing. This is fine because the faint animation animates the whole model. The cry animation does not contain this function because we want the cry to play over the idle animation, but not completely overwrite everything! If it did, then charizard would t-pose whenever it tried to do it's cry animation because it only animates the head bone.</br>		Below is an example of the faint using this overwrite function. What's going to happen in game is that when charizard faints, it will always play the faint animation over other animations it was already doing. This is fine because the faint animation animates the whole model. The cry animation does not contain this function because we want the cry to play over the idle animation, but not completely overwrite everything! If it did, then charizard would t-pose whenever it tried to do it's cry animation because it only animates the head bone.</br>

	"faint": "bedrock(charizard, faint, true)",		"<abbr title="This points to the faint animation for this Pokémon. If you have no faint animation, you can delete this line.">faint</abbr>": "<abbr title="This points to charizard's faint animation">bedrock(charizard, faint</abbr>, <abbr title="Adding 'true' like this will force this faint animation to play over all other animations whenever charizard faints.">true</abbr>)",
	"cry": "bedrock(charizard, cry)",		"<abbr title="This points to the cry animation for this Pokémon. Cries play whenever the Pokémon is called out of the pokeball. This occurs in and out of battle.">cry</abbr>": "<abbr title="This points to charizard's cry animation. Since it does not contain 'true' written after it, then this cry animation will not completely overwrite other animations when it plays. It should simply animate the bones it's supposed to while the rest of the bones can be controlled by another animation.">bedrock(charizard, cry)</abbr>",
	</br>		</br>