Fossils File - Revision history

Frank The Farmer: OOpsie daisy formatted this json wrong. I was in the neighborhood

2024-07-16T05:23:36Z

OOpsie daisy formatted this json wrong. I was in the neighborhood

← Older revision		Revision as of 05:23, 16 July 2024
Line 53:		Line 53:
	"cobblemon:rare_candy"		"cobblemon:rare_candy"
	]		]
			}


	{{Addon Creation}}		{{Addon Creation}}

Frank The Farmer: Added folder location and some formatting

2024-05-10T10:22:51Z

Added folder location and some formatting

← Older revision		Revision as of 10:22, 10 May 2024
Line 2:		Line 2:
	== Preface ==		== Preface ==
	The JSONs in the <code>fossils</code> folder control the resulting Pokémon from the <code>fossil machine</code>. These files specify what items are considered a fossil and what Pokémon should be created if these fossils are placed into the machine. They are short files where you simply select any Pokémon and any item in the game.		The JSONs in the <code>fossils</code> folder control the resulting Pokémon from the <code>fossil machine</code>. These files specify what items are considered a fossil and what Pokémon should be created if these fossils are placed into the machine. They are short files where you simply select any Pokémon and any item in the game.

			== File And Folder Format ==
			Below is an example of how you would arrange a <code>fossil.json</code> into a datapack:

			==== Folder Structure ====
			<div class="treeview">
			*''(addon name)''
			** '''pack.mcmeta'''
			**data
			***cobblemon
			****fossils
			*****'''<pokemon>.json'''
			</div></br>

	=== Fossil Breakdown ===		== Fossil Breakdown ==
	The fossil files are able to select any loaded Pokémon [[species]] to come out of the fossil machine. The <code>"result"</code> line functions like the <code>/pokegive</code> or <code>/pokespawn</code> commands, so you can include other data like level or regional forms. You can select up to 3 items you wish to serve as the "fossils."		The fossil files are able to select any loaded Pokémon [[species]] to come out of the fossil machine. The <code>"result"</code> line functions like the <code>/pokegive</code> or <code>/pokespawn</code> commands, so you can include other data like level or regional forms. You can select up to 3 items you wish to serve as the "fossils."

Line 21:		Line 34:
	* The <code>fossils</code> list doesn't support NBT data.		* The <code>fossils</code> list doesn't support NBT data.
	</br>		</br>
	=== Fossil Examples ===		== Fossil Examples ==
	Here are some fossil files you can use as a template to generate your own Pokémon.		Here are some fossil files you can use as a template to generate your own Pokémon.

Frank The Farmer: Your scientists were so preoccupied with whether or not they could, that they didn't stop to think if they should.

2024-03-06T05:30:28Z

Your scientists were so preoccupied with whether or not they could, that they didn't stop to think if they should.

New page

{{TOC|right}}
== Preface ==
The JSONs in the <code>fossils</code> folder control the resulting Pokémon from the <code>fossil machine</code>. These files specify what items are considered a fossil and what Pokémon should be created if these fossils are placed into the machine. They are short files where you simply select any Pokémon and any item in the game.

=== Fossil Breakdown ===
The fossil files are able to select any loaded Pokémon [[species]] to come out of the fossil machine. The <code>"result"</code> line functions like the <code>/pokegive</code> or <code>/pokespawn</code> commands, so you can include other data like level or regional forms. You can select up to 3 items you wish to serve as the "fossils."

</br>Here is a breakdown of the <code>arctozolt</code> fossil file:
{
"<abbr title="Here you will specify what Pokémon will be generated from the machine and any extra data to apply to that Pokémon.">result</abbr>": "<abbr title="In this case, Arctozolt will be created if all the following items are placed into the machine. Because there is no other data specified, it will be a normal level 1 Arctozolt.">arctozolt</abbr>",
"<abbr title="Here you will list items to be used as fossils for the machine.">fossils</abbr>": [
"<abbr title="The item ID for the fossilized dino">cobblemon:fossilized_dino</abbr>",
"<abbr title="The item ID for the fossilized bird">cobblemon:fossilized_bird</abbr>"
]
}

</br> Here is some extra info about fossil files:
* If your <code>result</code> pokemon doesn't exist or includes a typo, then the species will be chose at random from '''all loaded species'''.
* Since the <code>result</code> functions like the commands that generate Pokémon, you can generate them as shiny or with special abilities.
* The <code>fossils</code> don't need to come out of the suspicious sand or gravel blocks. You can use any item from the game.
* The <code>fossils</code> list doesn't support NBT data.
</br>
=== Fossil Examples ===
Here are some fossil files you can use as a template to generate your own Pokémon.

* Cranidos' fossil file:
{
"result": "cranidos",
"fossils": [
"cobblemon:skull_fossil"
]
}
</br>
* A custom Porygon file that will generate as a level 10 shiny:
{
"result": "porygon shiny=yes level=10",
"fossils": [
"cobblemon:upgrade",
"cobblemon:dubious_disc",
"cobblemon:rare_candy"
]

{{Addon Creation}}