Species Additions - Revision history

Frank The Farmer: Info update for species addiitons

2025-03-06T05:32:44Z

Info update for species addiitons

← Older revision		Revision as of 05:32, 6 March 2025
Line 82:		Line 82:
	</br>		</br>
	==== Datapack Folder Location ====		==== Datapack Folder Location ====
	These files belong in a folder you might have never seen before. You can place the JSONs in the species additions folder itself, or even create sub folders for your JSONs. Here is how you should arrange your <code>species addition</code> files and folder:		These files belong in a folder you might have never seen before. You can place the JSONs in the species additions folder itself, or even create sub folders for your JSONs. '''Remember that datapack rules will apply if you use the cobblemon namespace and use the Pokémon's name to name the JSON. Consider using your own namespace and using unique file names to avoid conflicts with other addons that want to make changes to the same Pokémon.''' Here is how you should arrange your <code>species addition</code> files and folder:
	<div class="treeview">		<div class="treeview">
	*''(addon name)''		*''(addon name)''
Line 93:		Line 93:
	</div></br>		</div></br>

	You can also merge the species additions folder into an existing addon pack.		You can also merge the species additions folder into an existing addon pack.

	=== Species Addition Examples ===		=== Species Addition Examples ===

Frank The Farmer: Made some additions 😏

2024-03-04T11:48:49Z

Made some additions 😏

@@ Line 1: / Line 1: @@
 {{TOC|right}}
 == Preface ==
-You can create a <code>species_addition</code> JSON to replace or add some new data to an existing <code>species</code> file. Species additions can be a helpful way to add your own regional variants to existing Pokémon. They can also be helpful if you want to rewrite a Pokémon's stats for an addon. This system was created to improve the compatibility between multiple datapacks by allowing datapack developers to target specific species and append or replace depending on the field type without overwriting the base species file.
+You can create a <code>species_addition</code> JSON to replace or add some new data to an existing <code>[[Species|species]]</code> file. Species additions can be a helpful way to add your own [[Tutorials/Regional_Forms|regional variants]] to existing Pokémon. They can also be helpful if you want to rewrite a Pokémon's stats for an addon. This system was created to improve the compatibility between multiple datapacks by allowing datapack developers to target specific species and append or replace depending on the field type without overwriting the base species file.
 === Species Addition Breakdown ===
@@ Line 8: / Line 8: @@
 Here is a breakdown of an example <code>species addition</code>. Hover over the underlined text to see more information.
+  {
-    "<abbr title="Here you specify what Pokémon will receive species data changes">target</abbr>": "<abbr title="Bulbasaur is the pokemon that will receive changes">cobblemon:bulbasaur</abbr>",
+  "<abbr title="Here you will specify which Pokémon will receive the data in this file.">target</abbr>": "<abbr title="In this case, Bulbasaur will get all of this data written into its species file.">cobblemon:bulbasaur</abbr>",
-    "<abbr title="A Pokémon's primary type">primaryType</abbr>": "<abbr title="Bulbasaur's primary type will be changed to Fire">fire</abbr>",
+  "<abbr title="This will let you change the primary type of the target">primaryType</abbr>": "fire",
-     "<abbr title="A Pokemon's secondary type">secondaryType</abbr>": "<abbr title="Bulbasaur's secondary type will be changed to Water">water</abbr>"
+  "<abbr title="This will let you change the secondary type of the target">secondaryType</abbr>": "water",
+  }
-Loading this file would result in Bulbasaur becoming a Fire/Water type.
+Loading this file would have the following effects on Bulbasaur:
-Here is a list of tips about species additions:
+</br>Here is a list of tips about species additions:
 * Species additions will rewrite any data if it is already written in the target species file.
 ** Example: If you wanted to add a new move to the <code>moves</code> list, you'd have to rewrite the entire move list. If you only write the one new move, it will be the only move that Pokémon can learn.
@@ Line 26: / Line 80: @@
 * Using species additions to add special Pokémon forms is the most addon friendly process!
 ** If two creators both wanted to add a regional form to Mudkip, and they both used species additions to add the form data, then people can use both addons together without issues!
+</br>
 ==== Datapack Folder Location ====
 These files belong in a folder you might have never seen before. You can place the JSONs in the species additions folder itself, or even create sub folders for your JSONs. Here is how you should arrange your <code>species addition</code> files and folder:
@@ Line 43: / Line 97: @@
 === Species Addition Examples ===
 One of the most common uses of species additions by the community is adding extra <code>evolution</code> data to official Pokémon. It is also used often to change the <code>baseScale</code> and <code>hitbox</code> sizes of a Pokémon for use with unofficial models.
 * In this example, Eevee will now evolve into Charizard at level 36 and it will maintain all its other eeveelutions!

Blob: navbox

2023-10-14T11:39:59Z

navbox

← Older revision		Revision as of 11:39, 14 October 2023
Line 158:		Line 158:

	[[File:New_Eeveelutions.png\|thumb\|center\|900px\|caption\|The resulting eeveelutions with both addons enabled.]]		[[File:New_Eeveelutions.png\|thumb\|center\|900px\|caption\|The resulting eeveelutions with both addons enabled.]]

			{{Addon Creation}}

Blob at 12:11, 26 July 2023

2023-07-26T12:11:45Z

← Older revision		Revision as of 12:11, 26 July 2023
Line 9:		Line 9:
	{		{
	"<abbr title="Here you specify what Pokémon will receive species data changes">target</abbr>": "<abbr title="Bulbasaur is the pokemon that will receive changes">cobblemon:bulbasaur</abbr>",		"<abbr title="Here you specify what Pokémon will receive species data changes">target</abbr>": "<abbr title="Bulbasaur is the pokemon that will receive changes">cobblemon:bulbasaur</abbr>",
	"<abbr title="A Pokémon's primary type">primaryType</abbr>": "<abbr title="Bulbasaur's primary type will be changed to ~~fire~~">fire</abbr>",		"<abbr title="A Pokémon's primary type">primaryType</abbr>": "<abbr title="Bulbasaur's primary type will be changed to Fire">fire</abbr>",
	"<abbr title="A Pokemon's secondary type">secondaryType</abbr>": "<abbr title="Bulbasaur's secondary type will be changed to ~~water~~">water</abbr>"		"<abbr title="A Pokemon's secondary type">secondaryType</abbr>": "<abbr title="Bulbasaur's secondary type will be changed to Water">water</abbr>"
	}		}

	~~The result of loading~~ this file would be Bulbasaur becoming a ~~fire~~/~~water~~ type.		Loading this file would result in Bulbasaur becoming a Fire/Water type.

	Here is a list of tips about species additions:		Here is a list of tips about species additions:
Line 42:		Line 42:

	=== Species Addition Examples ===		=== Species Addition Examples ===
	One of the most common uses of species additions by the community is adding extra <code>evolution</code> data to official Pokémon. It is also used often to change the <code>baseScale</code> and <code>hitbox</code> sizes of a ~~pokemon~~ for use with unofficial models.		One of the most common uses of species additions by the community is adding extra <code>evolution</code> data to official Pokémon. It is also used often to change the <code>baseScale</code> and <code>hitbox</code> sizes of a Pokémon for use with unofficial models.

	* In this example, Eevee will now evolve into Charizard at level 36 and it will maintain all its other eeveelutions!		* In this example, Eevee will now evolve into Charizard at level 36 and it will maintain all its other eeveelutions!
Line 66:		Line 66:

	The following is an example of two addons that want to change <code>evolution</code> and <code>form</code> data for an existing Pokémon. In this case, they both want to create a new eeveelution and a new regional form of Eevee that has its own evolution as well. Thanks to <code>species_additions</code> and its special rules, anybody can use both of these hypothetical addons and get the effects of both without issues!		The following is an example of two addons that want to change <code>evolution</code> and <code>form</code> data for an existing Pokémon. In this case, they both want to create a new eeveelution and a new regional form of Eevee that has its own evolution as well. Thanks to <code>species_additions</code> and its special rules, anybody can use both of these hypothetical addons and get the effects of both without issues!
	* A ~~normal~~ Eevee could then evolve into Charizard or Blastoise at level 36.		* A regular Eevee could then evolve into Charizard or Blastoise at level 36.
	* An Alolan Eevee would become an ~~ice~~ type and evolve into Squirtle with a ~~water stone~~.		* An Alolan Eevee would become an Ice type and evolve into Squirtle with a [[Water Stone]].
	* A Hisuian Eevee would become a ~~fire~~ type and evolve into Bulbasaur with a ~~leaf stone~~.		* A Hisuian Eevee would become a Fire type and evolve into Bulbasaur with a [[Leaf Stone]].

	Addon #1's species addition:		Addon #1's species addition:

Frank The Farmer: /* Species Addition Examples */

2023-07-26T09:05:31Z

Species Addition Examples

← Older revision		Revision as of 09:05, 26 July 2023
Line 156:		Line 156:
	]		]
	}		}

			[[File:New_Eeveelutions.png\|thumb\|center\|900px\|caption\|The resulting eeveelutions with both addons enabled.]]

Frank The Farmer: Created page with "{{TOC|right}} == Preface == You can create a `species_addition` JSON to replace or add some new data to an existing `species` file. Species additions can be a helpful way to add your own regional variants to existing Pokémon. They can also be helpful if you want to rewrite a Pokémon's stats for an addon. This system was created to improve the compatibility between multiple datapacks by allowing datapack developers to target specific species and ap..."

2023-07-26T07:31:04Z

Created page with "{{TOC|right}} == Preface == You can create a <code>species_addition</code> JSON to replace or add some new data to an existing <code>species</code> file. Species additions can be a helpful way to add your own regional variants to existing Pokémon. They can also be helpful if you want to rewrite a Pokémon's stats for an addon. This system was created to improve the compatibility between multiple datapacks by allowing datapack developers to target specific species and ap..."

New page

{{TOC|right}}
== Preface ==
You can create a <code>species_addition</code> JSON to replace or add some new data to an existing <code>species</code> file. Species additions can be a helpful way to add your own regional variants to existing Pokémon. They can also be helpful if you want to rewrite a Pokémon's stats for an addon. This system was created to improve the compatibility between multiple datapacks by allowing datapack developers to target specific species and append or replace depending on the field type without overwriting the base species file.

=== Species Addition Breakdown ===
Creating a <code>species addition</code> JSON is very simple. You simply list your target Pokémon, and then list '''''any data''''' that you wish to rewrite or add to the <code>species</code> file of that Pokémon. <code>Forms</code> and <code>evolution</code> data are exceptions to the rewriting. They will always be added instead.

Here is a breakdown of an example <code>species addition</code>. Hover over the underlined text to see more information.
{
"<abbr title="Here you specify what Pokémon will receive species data changes">target</abbr>": "<abbr title="Bulbasaur is the pokemon that will receive changes">cobblemon:bulbasaur</abbr>",
"<abbr title="A Pokémon's primary type">primaryType</abbr>": "<abbr title="Bulbasaur's primary type will be changed to fire">fire</abbr>",
"<abbr title="A Pokemon's secondary type">secondaryType</abbr>": "<abbr title="Bulbasaur's secondary type will be changed to water">water</abbr>"
}

The result of loading this file would be Bulbasaur becoming a fire/water type.

Here is a list of tips about species additions:
* Species additions will rewrite any data if it is already written in the target species file.
** Example: If you wanted to add a new move to the <code>moves</code> list, you'd have to rewrite the entire move list. If you only write the one new move, it will be the only move that Pokémon can learn.
* Species additions will also add your written data if it doesn't exist in the target species file yet.
** You can create a file to add <code>drops</code> for Pokémon that don't drop anything yet.
* This system was created to help addon creators keep their datapacks compatible with others! Always use them if you wish to edit something about existing Pokémon you didn't create.
** It will prevent 2 datapacks fighting over who will get to replace the main species file.
** It can prevent your addon from causing irreparable damage to player save data in certain scenarios!
* If 2 additions want to rewrite the same thing, like item drops, then only the first file in the load order will have its changes implemented.
* Using species additions to add special Pokémon forms is the most addon friendly process!
** If two creators both wanted to add a regional form to Mudkip, and they both used species additions to add the form data, then people can use both addons together without issues!

==== Datapack Folder Location ====
These files belong in a folder you might have never seen before. You can place the JSONs in the species additions folder itself, or even create sub folders for your JSONs. Here is how you should arrange your <code>species addition</code> files and folder:
<div class="treeview">
*''(addon name)''
**data
***''(addon name)''
****species_additions
*****'''<target_pokemon>.json'''
*****''(optional target pokemon/generation folders)''
******'''<optional target_pokemon>.json'''
</div></br>

You can also merge the species additions folder into an existing addon pack.

=== Species Addition Examples ===
One of the most common uses of species additions by the community is adding extra <code>evolution</code> data to official Pokémon. It is also used often to change the <code>baseScale</code> and <code>hitbox</code> sizes of a pokemon for use with unofficial models.

* In this example, Eevee will now evolve into Charizard at level 36 and it will maintain all its other eeveelutions!
{
"target": "cobblemon:eevee",
"evolutions": [
{
"id": "eevee_charizard",
"variant": "level_up",
"result": "charizard",
"consumeHeldItem": false,
"learnableMoves": [],
"requirements": [
{
"variant": "level",
"minLevel": 36
}
]
}
]
}

The following is an example of two addons that want to change <code>evolution</code> and <code>form</code> data for an existing Pokémon. In this case, they both want to create a new eeveelution and a new regional form of Eevee that has its own evolution as well. Thanks to <code>species_additions</code> and its special rules, anybody can use both of these hypothetical addons and get the effects of both without issues!
* A normal Eevee could then evolve into Charizard or Blastoise at level 36.
* An Alolan Eevee would become an ice type and evolve into Squirtle with a water stone.
* A Hisuian Eevee would become a fire type and evolve into Bulbasaur with a leaf stone.

Addon #1's species addition:
{
"target": "cobblemon:eevee",
"features": ["alolan"],
"forms": [
{
"name": "Alola",
"primaryType": "ice",
"abilities": [
"snowcloak",
"h:snowwarning"
],
"aspects": ["alolan"],
"evolutions": [
{
"id": "eevee_squirtle",
"variant": "item_interact",
"result": "squirtle",
"consumeHeldItem": false,
"learnableMoves": [],
"requirements": [],
"requiredContext": "cobblemon:water_stone"
}
]
}
],
"evolutions": [
{
"id": "eevee_blastoise",
"variant": "level_up",
"result": "blastoise",
"consumeHeldItem": false,
"learnableMoves": [],
"requirements": [
{
"variant": "level",
"minLevel": 36
}
]
}
]
}

Addon #2's species addition:
{
"target": "cobblemon:eevee",
"features": ["hisuian"],
"forms": [
{
"name": "Hisui",
"primaryType": "fire",
"abilities": [
"flamebody",
"h:drought"
],
"aspects": ["hisuian"],
"evolutions": [
{
"id": "eevee_bulbasaur",
"variant": "item_interact",
"result": "bulbasaur",
"consumeHeldItem": false,
"learnableMoves": [],
"requirements": [],
"requiredContext": "cobblemon:leaf_stone"
}
]
}
],
"evolutions": [
{
"id": "eevee_charizard",
"variant": "level_up",
"result": "charizard",
"consumeHeldItem": false,
"learnableMoves": [],
"requirements": [
{
"variant": "level",
"minLevel": 36
}
]
}
]
}