Tutorials/Multiple Visual Variants - Revision history

Frank The Farmer: Added Multiple Variants of reference links

2024-02-28T09:30:38Z

Added Multiple Variants of reference links

Blob: added back Category:Tutorial

2023-10-14T11:42:30Z

added back Category:Tutorial

← Older revision		Revision as of 11:42, 14 October 2023
Line 198:		Line 198:

	{{Addon Creation}}		{{Addon Creation}}
			[[Category:Tutorial]]

Blob: navbox

2023-10-14T11:36:43Z

navbox

← Older revision		Revision as of 11:36, 14 October 2023
Line 197:		Line 197:
	You should now have a functional set of variants! If your addon is not working properly at this stage, you can seek help in the Cobblemon Discord.		You should now have a functional set of variants! If your addon is not working properly at this stage, you can seek help in the Cobblemon Discord.

	~~[[Category:Tutorial]]~~		{{Addon Creation}}

Frank The Farmer: /* Step 7: Create the resolver file for your variants */

2023-08-08T11:06:25Z

Step 7: Create the resolver file for your variants

← Older revision		Revision as of 11:06, 8 August 2023
Line 167:		Line 167:
	Due to the many different ways variants can be made, there are many different ways to create the resolver. What you will do for this step is pick a comparable Pokémon feature and use that Pokémon as a template for your resolver file. You will be applying the <code>aspect</code> from your <code>species_feature</code> the same way they do.		Due to the many different ways variants can be made, there are many different ways to create the resolver. What you will do for this step is pick a comparable Pokémon feature and use that Pokémon as a template for your resolver file. You will be applying the <code>aspect</code> from your <code>species_feature</code> the same way they do.
	* Pokémon with variants that change the textures on the base model:		* Pokémon with variants that change the textures on the base model:
	** Tatsugiri		** [https://gitlab.com/cable-mc/cobblemon/-/blob/main/common/src/main/resources/assets/cobblemon/bedrock/pokemon/resolvers/0978_tatsugiri/0_tatsugiri_base.json Tatsugiri]
	** Valencian Butterfree		** [https://gitlab.com/cable-mc/cobblemon/-/blob/main/common/src/main/resources/assets/cobblemon/bedrock/pokemon/resolvers/0012_butterfree/2_butterfree_valencian.json Valencian Butterfree]
	** Valencian Vileplume		** [https://gitlab.com/cable-mc/cobblemon/-/blob/main/common/src/main/resources/assets/cobblemon/bedrock/pokemon/resolvers/0045_vileplume/2_vileplume_valencian.json Valencian Vileplume]
	* Pokemon with multiple variants that change models and the textures:		* Pokemon with multiple variants that change models and the textures:
	** Torterra		** [https://gitlab.com/cable-mc/cobblemon/-/tree/main/common/src/main/resources/assets/cobblemon/bedrock/pokemon/resolvers/0389_torterra Torterra]
	** Alolan Vulpix		** [https://gitlab.com/cable-mc/cobblemon/-/blob/main/common/src/main/resources/assets/cobblemon/bedrock/pokemon/resolvers/0037_vulpix/1_vulpix_alolan.json Alolan Vulpix]
	** Basculin		** [https://gitlab.com/cable-mc/cobblemon/-/blob/main/common/src/main/resources/assets/cobblemon/bedrock/pokemon/resolvers/0550_basculin/0_basculin_base.json Basculin]
	* Pokemon that use a single model, but change textures through <code>layers</code>:		* Pokemon that use a single model, but change textures through <code>layers</code>:
	** Alcremie		** [https://gitlab.com/cable-mc/cobblemon/-/blob/main/common/src/main/resources/assets/cobblemon/bedrock/pokemon/resolvers/0869_alcremie/0_alcremie_base.json Alcremie]
	** Arbok		** [https://gitlab.com/cable-mc/cobblemon/-/blob/main/common/src/main/resources/assets/cobblemon/bedrock/pokemon/resolvers/0024_arbok/0_arbok_base.json Arbok]
	** Spinda		** [https://gitlab.com/cable-mc/cobblemon/-/blob/main/common/src/main/resources/assets/cobblemon/bedrock/pokemon/resolvers/0327_spinda/0_spinda_base.json Spinda]
	</br>		</br>
	# After creating your resolver(s), place them in the <code>resolvers</code> folder for your addon.		# After creating your resolver(s), place them in the <code>resolvers</code> folder for your addon.

	=== Step 8: Test your addon in game ===		=== Step 8: Test your addon in game ===

Blob: added Category:Tutorial, some minor spelling changes

2023-08-07T08:40:47Z

added Category:Tutorial, some minor spelling changes

← Older revision		Revision as of 08:40, 7 August 2023
Line 50:		Line 50:
	It's best that you create all your assets first so you can assign them later. Create any models, textures, or animations that you want in Blockbench. Most visual variants are just a set of extra texture PNGs that are applied to the same model using <code>layers</code>.		It's best that you create all your assets first so you can assign them later. Create any models, textures, or animations that you want in Blockbench. Most visual variants are just a set of extra texture PNGs that are applied to the same model using <code>layers</code>.

	# Create the assets your ~~Pokemon~~ needs in Blockbench		# Create the assets your Pokémon needs in Blockbench
	# Save these assets in their associated folders		# Save these assets in their associated folders

Line 104:		Line 104:

	=== Step 6: Create special spawns for your variants <small>(optional)</small> ===		=== Step 6: Create special spawns for your variants <small>(optional)</small> ===
	This is an optional step to show you how to create unique spawns for each variant choice. If you do not specify any choices in the <code>"pokemon"</code> string, then the <code>"default"</code> choice from your feature will spawn as a result. It's highly recommended that you review the spawn files for ~~pokemon~~ with regional forms, Pumpkaboo, and Arbok. Those spawn files can be found on the [https://gitlab.com/cable-mc/cobblemon/-/tree/main/common/src/main/resources/data/cobblemon/spawn_pool_world Gitlab.]		This is an optional step to show you how to create unique spawns for each variant choice. If you do not specify any choices in the <code>"pokemon"</code> string, then the <code>"default"</code> choice from your feature will spawn as a result. It's highly recommended that you review the spawn files for Pokémon with regional forms, Pumpkaboo, and Arbok. Those spawn files can be found on the [https://gitlab.com/cable-mc/cobblemon/-/tree/main/common/src/main/resources/data/cobblemon/spawn_pool_world Gitlab.]

	You will mostly be using the Arbok file as a template for your Pokémon's spawn files. Even though Arbok's multiple spawns all have the same conditions, they can be changed so the different skins appear in different conditions. You can change the other spawn properties to whatever you like. A list of spawn conditions can be found [https://gitlab.com/cable-mc/cobblemon/-/wikis/Spawner/Spawn-Condition here.] The list of biome tags can be found [https://docs.google.com/document/d/1iB0EJSc2r6mRJXIo1n3XpHbZ5udwJVnrh2pXdhTyH8c/edit here.]		You will mostly be using the Arbok file as a template for your Pokémon's spawn files. Even though Arbok's multiple spawns all have the same conditions, they can be changed so the different skins appear in different conditions. You can change the other spawn properties to whatever you like. A list of spawn conditions can be found [https://gitlab.com/cable-mc/cobblemon/-/wikis/Spawner/Spawn-Condition here.] The list of biome tags can be found [https://docs.google.com/document/d/1iB0EJSc2r6mRJXIo1n3XpHbZ5udwJVnrh2pXdhTyH8c/edit here.]
Line 165:		Line 165:
	If you do not specify a model or poser file for each aspect, then they will use whatever was assigned to the variation with no aspects assigned. This is why some variations do not list every property.		If you do not specify a model or poser file for each aspect, then they will use whatever was assigned to the variation with no aspects assigned. This is why some variations do not list every property.

	Due to the many different ways variants can be made, there are many different ways to create the resolver. What you will do for this step is pick a comparable Pokémon feature and use that ~~pokemon~~ as a template for your resolver file. You will be applying the <code>aspect</code> from your <code>species_feature</code> the same way they do.		Due to the many different ways variants can be made, there are many different ways to create the resolver. What you will do for this step is pick a comparable Pokémon feature and use that Pokémon as a template for your resolver file. You will be applying the <code>aspect</code> from your <code>species_feature</code> the same way they do.
	* ~~Pokemon~~ with variants that change the textures on the base model:		* Pokémon with variants that change the textures on the base model:
	** Tatsugiri		** Tatsugiri
	** Valencian Butterfree		** Valencian Butterfree
Line 196:		Line 196:

	You should now have a functional set of variants! If your addon is not working properly at this stage, you can seek help in the Cobblemon Discord.		You should now have a functional set of variants! If your addon is not working properly at this stage, you can seek help in the Cobblemon Discord.

			[[Category:Tutorial]]

Frank The Farmer at 11:34, 21 July 2023

2023-07-21T11:34:45Z

Blob at 09:05, 21 July 2023

2023-07-21T09:05:21Z

← Older revision		Revision as of 09:05, 21 July 2023
Line 1:		Line 1:
	{{TOC\|right}}		{{TOC\|right}}
	== Preface ==		== Preface ==
	This tutorial will teach you how to create Pokémon that have multiple visual aspects. An example of these would be the Arbok skin patterns, the Pumpkaboo sizes, or the many different variants of Alcremie and Spinda. Due to the variable nature of this system, this guide will only show you how to create and apply extra aspects to a Pokémon. '''Knowledge of creating custom ~~pokemon~~ and [~~https://wiki.cobblemon.com/index.php/~~Tutorials/~~Regional_Forms~~ regional forms] is highly recommended.		This tutorial will teach you how to create Pokémon that have multiple visual aspects. An example of these would be the Arbok skin patterns, the Pumpkaboo sizes, or the many different variants of Alcremie and Spinda. Due to the variable nature of this system, this guide will only show you how to create and apply extra aspects to a Pokémon. '''Knowledge of creating custom Pokémon and [[Tutorials/Regional Forms\|regional forms]] is highly recommended.

	=== Step 1: Decide how your variants will function ===		=== Step 1: Decide how your variants will function ===
	There are a number of factors that can go into ~~Pokemon~~ variants. You can have it be a purely visual thing like Arbok or you can assign stats to each variant with <code>form</code> data like Pumpkaboo or Basculin. You can also take things a step further and create multiple <code>species features</code> for a Pokémon with unique textures that are applied as multiple layers on the model. This is the case for Alcremie and Spinda. They have a small set of texture PNGs that are then mixed and matched in the <code>resolver</code> file to allow for '''''dozens''''' of variants as a result. You can even create unique models and animations for each variant if desired.		There are a number of factors that can go into Pokémon variants. You can have it be a purely visual thing like Arbok or you can assign stats to each variant with <code>form</code> data like Pumpkaboo or Basculin. You can also take things a step further and create multiple <code>species features</code> for a Pokémon with unique textures that are applied as multiple layers on the model. This is the case for Alcremie and Spinda. They have a small set of texture PNGs that are then mixed and matched in the <code>resolver</code> file to allow for '''''dozens''''' of variants as a result. You can even create unique models and animations for each variant if desired.

	Decide how your variant will function first so you know what choices to pick later in this guide. If you'd like some examples, you can reference the <code>species</code> and <code>resolver</code> files of the following Pokémon. Also be sure to check out the <species_features> folder of the mod to see how their feature files look and function. Here are some great examples of the variant system at its best:		Decide how your variant will function first so you know what choices to pick later in this guide. If you'd like some examples, you can reference the <code>species</code> and <code>resolver</code> files of the following Pokémon. Also be sure to check out the <species_features> folder of the mod to see how their feature files look and function. Here are some great examples of the variant system at its best:
Line 55:		Line 55:
	Remember to create a <code>poser</code> file if you made any new animations. Needing new animation and poser files for variants isn’t a common thing. Unless your variant is vastly different, like Alolan Exeggutor, then you most likely don't need to make new animations.		Remember to create a <code>poser</code> file if you made any new animations. Needing new animation and poser files for variants isn’t a common thing. Unless your variant is vastly different, like Alolan Exeggutor, then you most likely don't need to make new animations.

	=== Step 4:Create a “species feature” ===		=== Step 4: Create a “species feature” ===
	You will be creating as many species features as you need to make your variants work. There are 2 types of species features you can make. The <code>flag</code> type feature has a single choice and is used for things like regionals. The <code>choice</code> type feature has a pool of choices and can be either randomized or have one choice set as the default. For the purpose of this guide, '''you will be creating a choice type feature with multiple variants.'''		You will be creating as many species features as you need to make your variants work. There are 2 types of species features you can make. The <code>flag</code> type feature has a single choice and is used for things like regionals. The <code>choice</code> type feature has a pool of choices and can be either randomized or have one choice set as the default. For the purpose of this guide, '''you will be creating a choice type feature with multiple variants.'''

Line 65:		Line 65:
	#* You can create as many choices as you want and name them whatever you want.		#* You can create as many choices as you want and name them whatever you want.
	#* The value for <code>"default"</code> can be set to "random" or any one of the choices you list. You usually want it on random.		#* The value for <code>"default"</code> can be set to "random" or any one of the choices you list. You usually want it on random.
	~~<syntaxhighlight>~~
	{		{
	"type": "choice",		"type": "choice",
	"keys": ["custom_feature"],		"keys": ["custom_feature"],
	"default": "random",		"default": "random",
	"choices": [		"choices": [
	"choice1",		"choice1",
	"choice2",		"choice2",
	"choice3"		"choice3"
	],		],
	"isAspect": true,		"isAspect": true,
	"aspectFormat": "custom-feature-{{choice}}"		"aspectFormat": "custom-feature-<nowiki>{{choice}}</nowiki>"
	}		}
	~~</syntaxhighlight>~~
	# <li value="3"> Save the file		# <li value="3"> Save the file
	# Place this new species feature file into the <code>species_feature</code> folder of your addon		# Place this new species feature file into the <code>species_feature</code> folder of your addon
Line 84:		Line 84:
	Even though the choice is randomized, a Pokémon will maintain its aspects when evolving if the entire evolutionary line is assigned the feature. A "heart" Ekans will always evolve into a "heart" Arbok by default. Aspect choices can also be assigned in the evolution data to change or control the resulting aspect of the next evolution. This is the case with Grotle and Pumpkaboo evolutions.		Even though the choice is randomized, a Pokémon will maintain its aspects when evolving if the entire evolutionary line is assigned the feature. A "heart" Ekans will always evolve into a "heart" Arbok by default. Aspect choices can also be assigned in the evolution data to change or control the resulting aspect of the next evolution. This is the case with Grotle and Pumpkaboo evolutions.

	=== Step 4:Create a “species_feature_assignments” file ===		=== Step 4: Create a “species_feature_assignments” file ===
	The <code>species_feature_assignments</code> file is a very short JSON that has a list of one or more Pokémon which will receive one or more features. If you also want your variants to have different stats like Pumpkaboo, then you'll want to make a <code>species_addition</code> file with form data. Step 4 from the ~~[https://wiki.cobblemon.com/index.php/Tutorials/Regional_Forms~~ regional forms guide.]		The <code>species_feature_assignments</code> file is a very short JSON that has a list of one or more Pokémon which will receive one or more features. If you also want your variants to have different stats like Pumpkaboo, then you'll want to make a <code>species_addition</code> file with form data. [[Tutorials/Regional Forms#Step 4: Create a "species addition" file with "form" data\|Step 4 from the regional forms guide.]]

	# Create a new text file and name it after your idea. Include the extension of <code>.json</code>		# Create a new text file and name it after your idea. Include the extension of <code>.json</code>
Line 103:		Line 103:
	# Place this new file into the <code>species_feature_assignments</code> folder of your addon.		# Place this new file into the <code>species_feature_assignments</code> folder of your addon.

	=== Step 5: Create special spawns for your variants(optional) ===		=== Step 5: Create special spawns for your variants <small>(optional)</small> ===
	This is an optional step to show you how to create unique spawns for each variant choice. If you do not specify any choices in the <code>"pokemon"</code> string, then the <code>"default"</code> choice from your feature will spawn as a result. It's highly recommended that you review the spawn files for pokemon with regional forms, Pumpkaboo, and Arbok. Those spawn files can be found on the [https://gitlab.com/cable-mc/cobblemon/-/tree/main/common/src/main/resources/data/cobblemon/spawn_pool_world Gitlab.]		This is an optional step to show you how to create unique spawns for each variant choice. If you do not specify any choices in the <code>"pokemon"</code> string, then the <code>"default"</code> choice from your feature will spawn as a result. It's highly recommended that you review the spawn files for pokemon with regional forms, Pumpkaboo, and Arbok. Those spawn files can be found on the [https://gitlab.com/cable-mc/cobblemon/-/tree/main/common/src/main/resources/data/cobblemon/spawn_pool_world Gitlab.]

Frank The Farmer: Created page with "{{TOC|right}} == Preface == This tutorial will teach you how to create Pokémon that have multiple visual aspects. An example of these would be the Arbok skin patterns, the Pumpkaboo sizes, or the many different variants of Alcremie and Spinda. Due to the variable nature of this system, this guide will only show you how to create and apply extra aspects to a Pokémon. '''Knowledge of creating custom pokemon and [https://wiki.cobblemon.com/index.php/Tutorials/Regional_For..."

2023-07-21T07:49:13Z

Created page with "{{TOC|right}} == Preface == This tutorial will teach you how to create Pokémon that have multiple visual aspects. An example of these would be the Arbok skin patterns, the Pumpkaboo sizes, or the many different variants of Alcremie and Spinda. Due to the variable nature of this system, this guide will only show you how to create and apply extra aspects to a Pokémon. '''Knowledge of creating custom pokemon and [https://wiki.cobblemon.com/index.php/Tutorials/Regional_For..."

New page

{{TOC|right}}
== Preface ==
This tutorial will teach you how to create Pokémon that have multiple visual aspects. An example of these would be the Arbok skin patterns, the Pumpkaboo sizes, or the many different variants of Alcremie and Spinda. Due to the variable nature of this system, this guide will only show you how to create and apply extra aspects to a Pokémon. '''Knowledge of creating custom pokemon and [https://wiki.cobblemon.com/index.php/Tutorials/Regional_Forms regional forms] is highly recommended.

=== Step 1: Decide how your variants will function ===
There are a number of factors that can go into Pokemon variants. You can have it be a purely visual thing like Arbok or you can assign stats to each variant with <code>form</code> data like Pumpkaboo or Basculin. You can also take things a step further and create multiple <code>species features</code> for a Pokémon with unique textures that are applied as multiple layers on the model. This is the case for Alcremie and Spinda. They have a small set of texture PNGs that are then mixed and matched in the <code>resolver</code> file to allow for '''''dozens''''' of variants as a result. You can even create unique models and animations for each variant if desired.

Decide how your variant will function first so you know what choices to pick later in this guide. If you'd like some examples, you can reference the <code>species</code> and <code>resolver</code> files of the following Pokémon. Also be sure to check out the <species_features> folder of the mod to see how their feature files look and function. Here are some great examples of the variant system at its best:
* '''Grotle & Torterra''': Grotle uses the evolution process to evolve into different variants of Torterra using saplings. Certain saplings will allow it to evolve into a matching Torterra! Each evolution method results in the different Torterra '''models and textures!'''
* '''Milcery & Alcremie''': Milcery also uses the evolution process to apply different aspects in the resulting Alcremie. The difference is that one aspect depends on the Sweet that is held, and the second aspect depends on the time of day that it was evolved. The evolution data that makes this possible for Milcery includes over 1600 lines of data...
* '''Spinda''': Spinda has 5 features, each with their own random pool of choices, that are assigned to it. These features apply some spot textures from a pool of 37 unique textures. This becomes 74 if you include the shiny textures. There are over '''''47,000 unique forms''''' of Spinda as a result.
* '''Arbok''': Arbok has a pool of randomly chosen aspects that affect the pattern on it's snake hood. Although the aspect is chosen at random, each pattern is assigned unique spawn data. You can reference this and create different spawn locations for each variant you make!
* '''Pumpkaboo & Gourgeist''': Pumpkaboo uses <code>form</code> data to apply the different HP stat changes to each of its sizes. Each size form can then be applied with one of the aspect choices so they can have unique models and textures.

=== Step 2: Arrange the folders for this addon ===
Due to some files sharing the same names later in this guide, you will be creating the folder structure and <code>pack.mcmeta</code> now. This is to prevent confusion going forward.

# Create a series of folders arranged like the following example:
==== Folder Structure ====
<div class="treeview">
*''(addon name)''
** '''pack.mcmeta'''
**assets
***cobblemon
****bedrock
*****pokemon
******animations
*******<target pokemon folder>
******models
*******<target pokemon folder>
******posers
******resolvers
*******<target pokemon folder>
****textures
*****pokemon
******<target pokemon folder>
**data
***cobblemon
****spawn_pool_world
****species_feature_assignments
****species_features
</div></br>
# <li value="2">Create your <code>pack.mcmeta</code> file
#* Remember to write the necessary data into this file.
# Place this new file into the first folder of your addon next to <code>assets</code> and <code>data</code>
After this folder tree for your addon is made, you can simply drop the files into the associated folders as you create them.
Remember that the <code>pack.mcmeta</code> is a file, not a folder to add. It must be one folder deep in order for Minecraft to recognize this pack as a resource pack or data pack when in the appropriate game folders.

=== Step 3: Create your assets ===
It's best that you create all your assets first so you can assign them later. Create any models, textures, or animations that you want in Blockbench. Most visual variants are just a set of extra texture PNGs that are applied to the same model using <code>layers</code>.

# Create the assets your Pokemon needs in Blockbench
# Save these assets in their associated folders

Remember to create a <code>poser</code> file if you made any new animations. Needing new animation and poser files for variants isn’t a common thing. Unless your variant is vastly different, like Alolan Exeggutor, then you most likely don't need to make new animations.

=== Step 4:Create a “species feature” ===
You will be creating as many species features as you need to make your variants work. There are 2 types of species features you can make. The <code>flag</code> type feature has a single choice and is used for things like regionals. The <code>choice</code> type feature has a pool of choices and can be either randomized or have one choice set as the default. For the purpose of this guide, '''you will be creating a choice type feature with multiple variants.'''

# Create a new text file and name it after your idea. Include the extension of<code>.json</code>
#* Example: Arbok's species feature is named <code>snake_pattern.json</code>
#* Remember to use lowercase and make sure that the file does not end in any other extension like ".txt"
# Insert the data for a <code>choice</code> species feature into this new species feature JSON:
#* '''Remember to change <code>"custom_feature"</code> to match your file name! It must stay in quotes.'''
#* You can create as many choices as you want and name them whatever you want.
#* The value for <code>"default"</code> can be set to "random" or any one of the choices you list. You usually want it on random.
<syntaxhighlight>
{
"type": "choice",
"keys": ["custom_feature"],
"default": "random",
"choices": [
"choice1",
"choice2",
"choice3"
],
"isAspect": true,
"aspectFormat": "custom-feature-{{choice}}"
}
</syntaxhighlight>
# <li value="3"> Save the file
# Place this new species feature file into the <code>species_feature</code> folder of your addon

Even though the choice is randomized, a Pokémon will maintain its aspects when evolving if the entire evolutionary line is assigned the feature. A "heart" Ekans will always evolve into a "heart" Arbok by default. Aspect choices can also be assigned in the evolution data to change or control the resulting aspect of the next evolution. This is the case with Grotle and Pumpkaboo evolutions.

=== Step 4:Create a “species_feature_assignments” file ===
The <code>species_feature_assignments</code> file is a very short JSON that has a list of one or more Pokémon which will receive one or more features. If you also want your variants to have different stats like Pumpkaboo, then you'll want to make a <code>species_addition</code> file with form data. Step 4 from the [https://wiki.cobblemon.com/index.php/Tutorials/Regional_Forms regional forms guide.]

# Create a new text file and name it after your idea. Include the extension of <code>.json</code>
#* Example: <code>spinda_spots.json</code>
# Insert the following data into this new species_addition JSON:
#* You can list as many Pokémon or features as you need
<syntaxhighlight>
{
"pokemon": ["<target_pokemon_1>", "<target_pokemon_2>"],
"features": ["<feature_1>", "<feature_2>"]
}
</syntaxhighlight>
# <li value="3"> Change <code>"<target_pokemon_#>"</code> to reference the Pokémon you want to add the features to. It must remain in quotes.
#* Example: <code>["bulbasaur", "ivysaur", "venusaur"]</code>
# Change <code>"<feature_#>"</code> to the feature(s) you made earlier. It must remain in quotes.
# <li value="5"> Save the file.
# Place this new file into the <code>species_feature_assignments</code> folder of your addon.

=== Step 5: Create special spawns for your variants(optional) ===
This is an optional step to show you how to create unique spawns for each variant choice. If you do not specify any choices in the <code>"pokemon"</code> string, then the <code>"default"</code> choice from your feature will spawn as a result. It's highly recommended that you review the spawn files for pokemon with regional forms, Pumpkaboo, and Arbok. Those spawn files can be found on the [https://gitlab.com/cable-mc/cobblemon/-/tree/main/common/src/main/resources/data/cobblemon/spawn_pool_world Gitlab.]

You will mostly be using the Arbok file as a template for your Pokémon's spawn files. Even though Arbok's multiple spawns all have the same conditions, they can be changed so the different skins appear in different conditions. You can change the other spawn properties to whatever you like. A list of spawn conditions can be found [https://gitlab.com/cable-mc/cobblemon/-/wikis/Spawner/Spawn-Condition here.] The list of biome tags can be found [https://docs.google.com/document/d/1iB0EJSc2r6mRJXIo1n3XpHbZ5udwJVnrh2pXdhTyH8c/edit here.]

# Obtain Arbok's <code>spawn_pool_world</code> file.
# Rename it after your Pokémon
# Open the file and locate the data under <code>"spawns"</code>
# Change the <code>"id"</code> value to the format of <code><pokemon>-<choice#>-<id #></code>
# Change the <code>"pokemon"</code> value to the format of <code><pokemon> <aspectFormat>=<choice#></code>
#* You'll need to reference your own aspect format you wrote earlier.
# Change the other spawn properties as desired.
# Repeat steps 4-6 to create more spawns for each choice of your species feature.
# Save the file.
# Place this new file into the <code>spawn_pool_world</code> folder of your addon.

Your list of spawns should now look something like Arbok's:
<syntaxhighlight>
"spawns": [
{
"id": "arbok-classic-1",
"pokemon": "arbok snake-pattern=classic",
"presets": [
"natural"
],
"type": "pokemon",
"context": "grounded",
"bucket": "common",
"level": "22-45",
"weight": 0.45,
"condition": {
"canSeeSky": true,
"biomes": [
"#cobblemon:is_arid"
]
}
},
{
"id": "arbok-legacy-1",
"pokemon": "arbok snake-pattern=legacy",
"presets": [
"natural"
],
"type": "pokemon",
"context": "grounded",
"bucket": "common",
"level": "22-45",
"weight": 0.03,
"condition": {
"canSeeSky": true,
"biomes": [
"#cobblemon:is_arid"
]
}
}...
</syntaxhighlight>

=== Step 6: Create the resolver file for your variants ===
Back in step 3, you should have already made the files for <code>models</code>, <code>textures</code>, <code>animations</code>, and <code>posers</code> that you needed. The last thing you need to do is assign them to your variant by creating a new <code>resolver</code> file.

If you do not specify a model or poser file for each aspect, then they will use whatever was assigned to the variation with no aspects assigned. This is why some variations do not list every property.

Due to the many different ways variants can be made, there are many different ways to create the resolver. What you will do for this step is pick a comparable Pokémon feature and use that pokemon as a template for your resolver file. You will be applying the <code>aspect</code> from your <code>species_feature</code> the same way they do.
* Pokemon with variants that change the textures on the base model:
** Tatsugiri
** Valencian Butterfree
** Valencian Vileplume
* Pokemon with multiple variants that change models and the textures:
** Torterra
** Alolan Vulpix
** Basculin
* Pokemon that use a single model, but change textures through <code>layers</code>:
** Alcremie
** Arbok
** Spinda
</br>
# After creating your resolver(s), place them in the <code>resolvers</code> folder for your addon.

=== Step 7: Test your addon in game ===
Load your addon in game to see if your variants looks different from each other. You can have Blockbench open to edit any relevant asset file '''in the resourcepacks folder''' if needed.
# Copy your addon folder and place it in the "resourcepacks" and "datapacks" folder in the Minecraft root directory.
# Start up Minecraft and click on ''Options'', then ''Resource Packs''. Select your pack to load it.
# Load/create a '''Creative''' world save that contains your addon in the "datapack" folder.
# Once in the world, you can run the command <code>/pokespawn <target pokemon> <species feature>=<choice#1></code>.
# Repeat for every variant you created.
# Ensure your new variants are working properly.
# Check if your variants spawn where you assigned them to. You can use <code>/checkspawn <rarity></code> when in the assigned biome. The different aspects are not shown in checkspawn.
#* You can run the command <code>/locate biome <assigned biome></code> to get coordinates to the assigned biome. You can then click on the coordinates it gave you and be teleported instantly.
# Make any desired edits to the asset files and save. Refresh resource packs with F3+T to see the changes you make.
# Make any desired edits to the data files and save. '''You need to quit to main menu, and load the world again if you want to see those changes.'''
#* The command for <code>/reload</code> does not work with Cobblemon addons unfortunately.

You should now have a functional set of variants! If your addon is not working properly at this stage, you can seek help in the Cobblemon Discord.

← Older revision		Revision as of 11:34, 21 July 2023
Line 84:		Line 84:
	Even though the choice is randomized, a Pokémon will maintain its aspects when evolving if the entire evolutionary line is assigned the feature. A "heart" Ekans will always evolve into a "heart" Arbok by default. Aspect choices can also be assigned in the evolution data to change or control the resulting aspect of the next evolution. This is the case with Grotle and Pumpkaboo evolutions.		Even though the choice is randomized, a Pokémon will maintain its aspects when evolving if the entire evolutionary line is assigned the feature. A "heart" Ekans will always evolve into a "heart" Arbok by default. Aspect choices can also be assigned in the evolution data to change or control the resulting aspect of the next evolution. This is the case with Grotle and Pumpkaboo evolutions.

	=== Step 4: Create a “species_feature_assignments” file ===		=== Step 5: Create a “species_feature_assignments” file ===
	The <code>species_feature_assignments</code> file is a very short JSON that has a list of one or more Pokémon which will receive one or more features. If you also want your variants to have different stats like Pumpkaboo, then you'll want to make a <code>species_addition</code> file with form data. [[Tutorials/Regional Forms#Step 4: Create a "species addition" file with "form" data\|Step 4 from the regional forms guide.]]		The <code>species_feature_assignments</code> file is a very short JSON that has a list of one or more Pokémon which will receive one or more features. If you also want your variants to have different stats like Pumpkaboo, then you'll want to make a <code>species_addition</code> file with form data. [[Tutorials/Regional Forms#Step 4: Create a "species addition" file with "form" data\|Step 4 from the regional forms guide.]]

Line 103:		Line 103:
	# Place this new file into the <code>species_feature_assignments</code> folder of your addon.		# Place this new file into the <code>species_feature_assignments</code> folder of your addon.

	=== Step 5: Create special spawns for your variants <small>(optional)</small> ===		=== Step 6: Create special spawns for your variants <small>(optional)</small> ===
	This is an optional step to show you how to create unique spawns for each variant choice. If you do not specify any choices in the <code>"pokemon"</code> string, then the <code>"default"</code> choice from your feature will spawn as a result. It's highly recommended that you review the spawn files for pokemon with regional forms, Pumpkaboo, and Arbok. Those spawn files can be found on the [https://gitlab.com/cable-mc/cobblemon/-/tree/main/common/src/main/resources/data/cobblemon/spawn_pool_world Gitlab.]		This is an optional step to show you how to create unique spawns for each variant choice. If you do not specify any choices in the <code>"pokemon"</code> string, then the <code>"default"</code> choice from your feature will spawn as a result. It's highly recommended that you review the spawn files for pokemon with regional forms, Pumpkaboo, and Arbok. Those spawn files can be found on the [https://gitlab.com/cable-mc/cobblemon/-/tree/main/common/src/main/resources/data/cobblemon/spawn_pool_world Gitlab.]

Line 160:		Line 160:
	</syntaxhighlight>		</syntaxhighlight>

	=== Step 6: Create the resolver file for your variants ===		=== Step 7: Create the resolver file for your variants ===
	Back in step 3, you should have already made the files for <code>models</code>, <code>textures</code>, <code>animations</code>, and <code>posers</code> that you needed. The last thing you need to do is assign them to your variant by creating a new <code>resolver</code> file.		Back in step 3, you should have already made the files for <code>models</code>, <code>textures</code>, <code>animations</code>, and <code>posers</code> that you needed. The last thing you need to do is assign them to your variant by creating a new <code>resolver</code> file.

Line 181:		Line 181:
	# After creating your resolver(s), place them in the <code>resolvers</code> folder for your addon.		# After creating your resolver(s), place them in the <code>resolvers</code> folder for your addon.

	=== Step 7: Test your addon in game ===		=== Step 8: Test your addon in game ===
	Load your addon in game to see if your variants looks different from each other. You can have Blockbench open to edit any relevant asset file '''in the resourcepacks folder''' if needed.		Load your addon in game to see if your variants looks different from each other. You can have Blockbench open to edit any relevant asset file '''in the resourcepacks folder''' if needed.
	# Copy your addon folder and place it in the "resourcepacks" and "datapacks" folder in the Minecraft root directory.		# Copy your addon folder and place it in the "resourcepacks" and "datapacks" folder in the Minecraft root directory.