Cobblemon Wiki - User contributions [en]

Dialogues

2026-01-23T03:04:58Z

Hiroku: mandatory dialogue field mention

Dialogues are a feature that can be used from API or from datapacks to play conversations in a GUI. They display entities, view pages of text, and handle various types of input.

A dialogue that has been registered through a datapack can be opened using the /opendialogue command.

Every case of a MoLang expression can be either a single text property or can be an array of text to support running multiple expressions to produce a result.

[[File:Dialogue_Intro.png|400px|center]]

=Dialogue=

A Dialogue JSON file consists of the following main elements:

- <code>escapeAction</code>: A string or array that defines the action to be taken when the dialogue is escaped. This can be a MoLang expression or a sequence of MoLang expressions.

- <code>speakers</code>: An object that defines the speakers in the dialogue. Each speaker is represented by a key-value pair, where the key is the speaker's identifier and the value is an object that describes what the speaker looks like and their name.

- <code>pages</code>: An array of objects, each representing a page in the dialogue.

==Speakers==

Each speaker is represented by an object with the following properties:

- <code>name</code>: A string or object that defines the speaker's name. This is usually just text. If it's an object, it must have a <code>type</code> property set to <code>"expression"</code> and an <code>expression</code> property that contains a MoLang expression. You would use an expression if you wanted the name to be dynamic.

- <code>face</code>: An object or MoLang expression that defines the speaker's face. This will be rendered in a frame of the GUI. For objects, it must have a <code>type</code> property set to the type of face. The only object type support currently is "standard". The others are done using MoLang expressions rather than an object.

- <code>gibber</code>: An object defining the gibber behaviour. This can be defined as simply <code>{}</code> to use the default settings, or as a full object with any of the properties that you want to set. See the section on <code>gibber</code> further below to see the properties that are available.

===Faces===
The speaker faces can be defined in multiple ways. If it is an object it is going to be a "standard" face type.

===="standard"====
The standard face type is for when the face displayed is not connected to a specific entity in the world but does follow Cobblemon's format of identifier and aspect list. The object must have the following properties:

- <code>modelType</code>: One of 'pokemon', 'npc'

- <code>identifier</code>: The identifier of the Pokémon or NPC, such as <code>cobblemon:bulbasaur</code>.

- <code>aspects</code>: An array of aspects that will be applied to the model.

For example:

"face": {
"type": "artificial",
"modelType": "pokemon",
"identifier": "cobblemon:pikachu",
"aspects": [
"shiny"
]
}

====player====
By using <code>q.player.face()</code> you can make the player's model render for this face.

For example:

"face": "q.player.face();"

====npc====
By using <code>q.npc.face()</code> you can show a direct reference to the NPC you're having the dialogue with, if this was dialogue started with an NPC entity.

For example:

"face": "q.npc.face();"

===Gibber===
An additional feature of dialogues is having the text appear gradually and with a simplistic set of tones that mimic speech, referred to here as gibbering. Gibbering has many options and all have sensible defaults. The properties available are as follows:

- <code>graduallyShowText</code>: A boolean which, when true, will cause the text in the GUI to gradually be typed out. When false, gibbering sound effects will play but all of the text will be visible from the beginning. Defaults to true.

- <code>allowSkip</code>: Whether or not clicking in the dialogue box will skip the gibbering and display all of the text at once. If false, the player must wait until the entirety of the gibbering has occurred before they can continue to the next page.

<code>step</code>: The number of characters between each gibber. A gibber will play for the current character index and then, after some time interval, this step will be used to move to a later character in the text to play the next gibber. When gradually revealing text is on, a larger step will mean that text will appear in larger chunks. Defaults to 4 characters.

<code>interval</code>: The time (in seconds) between each gibber sound. A smaller value will make the sounds come more rapidly, and the text will appear more quickly if gradually showing text. Defaults to 0.1 seconds.

<code>minPitch</code>: The minimum pitch multiplier that could be used when randomly selecting a tone. Defaults to 0.8.

<code>maxPitch</code>: The maximum pitch multiplier that could be used when randomly selecting a tone. Defaults to 1.2.

<code>minVolume</code>: The minimum volume multiplier that could be used when randomly selecting a tone. Defaults to 0.75.

<code>maxVolume</code>: The maximum volume multiplier that could be used when randomly selecting a tone. Defaults to 1.1.

<code>sounds</code>: A list of resource locations indicating which sound events should be chosen from when playing a gibber. It can be any number of sounds. Defaults to three sounds: <code>"cobblemon:entity.villager.npc1"</code>, <code>"cobblemon:entity.villager.npc2"</code>, and <code>"cobblemon:entity.villager.npc1"</code>.

==Pages==

Each page is represented by an object with the following properties:

- <code>id</code>: A string that uniquely identifies the page. This is needed for instances where you might want to jump to a specific page. Page numbers could be used, but you should use page IDs.

- <code>speaker</code>: A string that specifies the speaker's identifier. This depends upon the speaker by this identifier existing in the speakers list.

- <code>lines</code>: An array of strings or objects, each representing a line of text. If it's an object, it must have a <code>type</code> property set to <code>"expression"</code> and an <code>expression</code> property that contains a MoLang expression that evaluates to a string. You would use an expression if you want to include variables to make dynamic text.

- <code>input</code>: An object or string that defines the input prompt. If it's an object, it must have a <code>type</code> property set to <code>"option"</code>, <code>"text"</code>, <code>"auto-continue"</code>, or <code>"none"</code>, and other properties depending on the type. By default, the input value will be <code>none</code>.

- <code>gibber</code>: A page-specific gibber configuration. See above for more information about gibber objects. By default this is null, and will therefore fallback to the gibber that is on the <code>speaker</code> for this page, if any is.

- <code>clientActions</code>: A list of MoLang expressions that will run on the client after the first frame of the page has been rendered on the client. This can be used to play sounds with <code>"q.sound(...)"</code>, or even play animations on the face being rendered (if it is a Bedrock animated entity) by doing, for example, <code>"q.face.play_animation('win');"</code>.

- <code>escapeAction</code>: A string or array that defines the action to be taken when the page is escaped. This can be a MoLang expression or a sequence of MoLang expressions.

- <code>background</code>: A resource location to use as the background texture for the dialogue box. By default this is null, which will result in Cobblemon's internal texture to be used.

==Input Types==

The <code>input</code> property in a page object can have different structures depending on the <code>type</code>.

For all inputs that specify an <code>action</code> property which is set to a MoLang expression, you can access the time it took for them to make that input using <code>v.seconds_taken_to_input</code>.

==="option"===
The input is a set of options. The object must have an <code>options</code> property that is an array of objects, each representing an option. It can also specify whether the options should be displayed vertically or horizontally by whether or not the <code>vertical</code> property is true or false.

Each option object can have the following properties:

- <code>value</code>: The unique value of the dialogue option. This is not displayed to the player and is instead used to reference this option from scripts. This property is mandatory.

- <code>text</code>The display text for the option. This can be a simple string or can be an object. This property is mandatory.

- <code>action</code>: The MoLang expression to run when the user chooses the option.

- <code>isVisible</code>: A MoLang expression which must return either true or false. If false, the option will not be visible for the player. Defaults to true.

- <code>isSelectable</code>: A MoLang expression which must return either true or false. If false, the option will be greyed out (but only if it is visible). Defaults to true.

[[File:Dialogue_Options.png|600px|center]]

==="text"===
The input is a text field. The <code>action</code> property is a MoLang expression that will run when the player hits enter with text typed in. As specified earlier, you can check the text that they input using <code>v.selected_option</code> inside of the MoLang expression.

[[File:Dialogue_Input.png|600px|center]]

==="auto-continue"===
The dialogue will automatically progress after some period of time. There are several optional properties for this.

- <code>delay</code>: The delay in seconds until it progresses. By default this is 5 seconds.

- <code>allowSkip</code>: Whether the user is able to skip the delay by clicking. By default this is true. If false, the player will be forced to wait for the delay.

- <code>showTimer</code>: Whether a bar will be displayed to indicate how much more time the player has until it auto-continues. Defaults to false.

- <code>action</code>: A MoLang expression that runs when either the player clicks (only when <code>allowSkip</code> is true) or the delay finishes. By default this moves to the next page.

==="none"===
There is no input except that it waits until the user clicks to continue. The object can have an <code>action</code> property that defines the MoLang expression to run when the player clicks. By default, it moves to the next page.

===Timeouts===
All input types except for <code>"none"</code> and <code>"autocontinue"</code> can have a 'timeout' object which allows you to apply time constraints to the player viewing the page.

The timeout object can have 3 properties:

- <code>duration</code>: The time, in seconds, that the player will have to complete the input. By default this is 10 seconds.

- <code>showTimer</code>: Whether or not a bar will be shown to show the player how much time they have left. By default this is true.

- <code>action</code>: A MoLang expression to run if they do not enter the input in time. By default this will close the dialogue.

[[File:Dialogue_Timer.png|600px|center]]

=Example=
The following example is built-in to the mod, labelled "example".

{
"escapeAction": "q.dialogue.set_page('quitter')",
"speakers": {
"pikachu": {
"name": "The Voice of Hiro",
"face": {
"type": "artificial",
"modelType": "pokemon",
"identifier": "cobblemon:pikachu",
"aspects": [
"shiny"
]
},
"gibber": {
"step": 2,
"interval": 0.07,
"allowSkip": false
}
},
"player": {
"face": "q.player.face();",
"name": {
"type": "expression",
"expression": "q.player.username"
}
}
},
"pages": [
{
"id": "player-chat",
"speaker": "player",
"lines": [
{
"type": "expression",
"expression": "'Hello, I\\'m ' + q.player.username + '!'"
}
]
},
{
"speaker": "pikachu",
"lines": [
{
"type": "expression",
"expression": "'Nice to meet you, ' + q.player.username + '! Welcome to the world of dialogues!'"
}
]
},
{
"id": "intro",
"speaker": "pikachu",
"lines": [ "Do you want to learn more?"],
"input": {
"type": "option",
"vertical": false,
"options": [
{
"text": "Yes",
"value": "yes",
"action": [
"v.player_response = 'That sounds great!';",
"v.next_page = 'page1';",
"q.dialogue.set_page('player-surrogate');"
]
},
{
"text": "No",
"value": "no",
"action": [
"v.player_response = 'No, I really don\\'t care.';",
"v.next_page = 'quitter';",
"q.dialogue.set_page('player-surrogate');"
]
},
{
"text": "Sword!",
"value": "sword",
"isVisible": "q.player.main_held_item.is_of('minecraft:iron_sword')",
"isSelectable": "q.player.data.scared_npc != true;",
"action": [
"v.player_response = 'How about you die! Muahahaha!';",
"v.next_page = 'sword';",
"q.dialogue.set_page('player-surrogate');"
]
},
{
"text": "Sword again!",
"value": "sword2",
"isVisible": "q.player.main_held_item.is_of('minecraft:iron_sword')",
"isSelectable": "q.player.data.scared_npc == true;",
"action": [
"v.player_response = 'How about you die... again! Muahahaha!';",
"v.next_page = 'sword-again';",
"q.dialogue.set_page('player-surrogate');"
]
}
]
}
},
{
"id": "player-surrogate",
"speaker": "player",
"gibber": {},
"lines": [
{
"type": "expression",
"expression": "v.player_response;"
}
],
"input": "q.dialogue.set_page(v.next_page);"
},
{
"id": "page1",
"speaker": "pikachu",
"lines": [
"Well you see, this is a dialogue.",
"You can have multiple pages, and each page can have multiple lines."
]
},
{
"id": "page2",
"speaker": "pikachu",
"lines": ["On an unrelated note, did you know that I'm deeply afraid of iron swords? Anyway, cya!"],
"input": {
"type": "auto-continue",
"delay": 5,
"allowSkip": true,
"action": "q.dialogue.close();"
}
},
{
"id": "quitter",
"speaker": "pikachu",
"lines": ["Fine. Be that way."],
"input": "q.dialogue.close();",
"escapeAction": "q.dialogue.close();"
},
{
"id": "sword",
"speaker": "pikachu",
"lines": ["Oh god no, please don't hurt me!"],
"escapeAction": "q.dialogue.input('');",
"input": [
"t.data = q.player.data();",
"t.data.scared_npc = true;",
"q.player.save_data();",
"q.dialogue.close();"
]
},
{
"id": "sword-again",
"speaker": "pikachu",
"lines": ["I'm ready for you this time. YOU will die today!"],
"escapeAction": "0",
"input": {
"type": "option",
"vertical": true,
"timeout": {
"delay": 6,
"action": "q.dialogue.input('stand');"
},
"options": [
{
"text": "Parry his attack.",
"value": "parry",
"action": [
"v.reaction = 'parry';",
"q.dialogue.set_page('sword-again-decided');"
]
},
{
"text": "Stand perfectly still.",
"value": "stand",
"action": [
"v.reaction = 'stand still';",
"q.dialogue.set_page('sword-again-decided');"
]
},
{
"text": "Drop your sword.",
"value": "drop",
"action": [
"v.reaction = 'drop your sword';",
"q.dialogue.set_page('sword-again-decided');"
]
}
]
}
},
{
"id": "sword-again-decided",
"lines": [
{
"type": "expression",
"expression": "v.reaction == 'parry' ? 'You parry his attack and kill him.' : (v.reaction == 'stand still' ? 'He kills you.' : 'You drop your sword and he kills you.')"
}
],
"input": {
"type": "auto-continue",
"delay": 3,
"allowSkip": false,
"showTimer": false,
"action": "q.dialogue.set_page('sword-again-reaction');"
}
},
{
"id": "sword-again-reaction",
"speaker": "pikachu",
"lines": [
{
"type": "expression",
"expression": "'Nah, I\\'m just kidding. Interesting that you chose to ' + v.reaction + ' though.'"
}
]
},
{
"id": "name-question",
"speaker": "pikachu",
"lines": [ "Here's a puzzle though... What is my name? Lowercase only."],
"input": {
"type": "text",
"timeout": {
"delay": 10,
"action": "q.dialogue.set_page('too-slow');"
},
"action": [
"q.dialogue.set_page('name-speak');",
"t.data = q.player.data();"
]
}
},
{
"id": "name-speak",
"speaker": "player",
"lines": [
{
"type": "expression",
"expression": "'Your name is ' + v.selected_option + ', right?'"
}
],
"input": "q.dialogue.set_page('name-guess');"
},
{
"id": "name-guess",
"speaker": "pikachu",
"lines": [
{
"type": "expression",
"expression": "v.selected_option == 'hiroku' ? 'Correct! You know things that you shouldn\\'t...' : ('Wrong! I\\'m not \"' + v.selected_option + '\". Whoever that is.')"
}
],
"input": {
"type": "auto-continue",
"delay": 5,
"allowSkip": true,
"action": "q.dialogue.set_page('farewell');"
}
},
{
"id": "farewell",
"speaker": "pikachu",
"lines": ["Anyway, I'm done with this dialogue. Bye!"],
"input": "q.dialogue.close();"
},
{
"id": "too-slow",
"speaker": "pikachu",
"lines": ["Don't know? Sad. Well I don't know your name either, so I guess we're even."],
"input": "q.dialogue.close()"
}
]
}

1.7.1

2025-12-01T02:13:10Z

Hiroku: Date fix

{{InfoboxVersion
| title = 1.7.1
| image =
| release = November 29th, 2025
| fabric = [https://modrinth.com/mod/cobblemon/version/s64m1opn Modrinth] [https://www.curseforge.com/minecraft/mc-mods/cobblemon/files/6125079 CurseForge]
| neoforge = TBD
| previous = [[1.7.0]]
| next = TBD
}}
'''1.7.1''' is a minor update to Cobblemon that was released on November 29th, 2025.<ref>https://cobblemon.com/changelog#1-7-1</ref> It adds new trades and recipes, a few changes and various bug fixes.

==Additions==
* Added trades for [[Saccharine Sapling|Saccharine Saplings]], [[Hearty Grains]], [[Chipped Pot]], and [[Masterpiece Teacup]] to the Wandering Trader.
* Added brewing recipe for [[Throat Spray]].
* Added vanilla sprinting's field of view change to Pokémon land mounts.
* Added a customizable keybind for the riding freelook button.
* Added double tap to sprint on land mounts.

==Changes==
* Made Jet pitch turning 1.5x faster across all Pokémon.
* Party Pokémon now attack only mobs that are attacking their owner, instead of randomly targeting unrelated mobs and getting themselves hurt.
* Reduced the cost of the Vivichoke Seed trade with the Wandering Trader.
===Model updates for the following Pokémon===
* Tinkatink
* Tinkatuff
* Tinkaton

==Fixes==
* Fixed incorrect camera pivot on Bird, Jet, and Dolphin mounts, leading to some disorienting riding.
* Fixed players suffocating while on vanilla mounts.
* Fixed a graphics crash that could occur on some machines when campfire pots were nearby.
* Fixed ride controls overlay being displayed to passengers. The passengers probably don't need to know about those.
* Fixed mount jumping so that it doesn't switch back to ground animations.
* Fixed ridden Pokémon land collision and some issues around stepping up blocks. Land mounts are smoother overall now.
* Fixed Furfrou's pink and magenta trims being swapped. Only a man could make that mistake.
* Fixed friendship being reset to the default value when evolving a Pokémon.
* Fixed Combees not depositing honey upon leaving a hive if they entered it with nectar.
* Fixed pastured Combees not moving during the night or in rain.
* Fixed a case in which a Combee might try to path to a flower that no longer exists.
* Fixed Combees attempting to enter a full hive.
* Fixed a crash involving Combees and hives. 500 bee bugs. Bugged bees? We can be bees. Mark, this is good news.
* Fixed a crash related to NPC navigation.
* Fixed a crash when opening a PC box with certain wallpapers while using VulkanMod.
* Fixed a crash when you place a block in the way of hearty grains 2nd block.
* Fixed passengers hearing the shiny noise of a ridden shiny Pokémon.
Ponigiri can no longer be eaten at full hunger.
* Fixed Poké Snack spawning sounds not coming from the block.
* Medicinal Brew's Campfire Pot recipe now correctly displays that it can be made using an empty glass bottle or a filled bottle.
* Fixed glass bottle not being returned when slathering honey on a saccharine leaf block.
* Fixed saccharine hanging signs sometimes dropping their oak wood counterpart when being broken.
* Fixed a bunch of incompatibilities with NeoForge mods.
* Fixed a bug where wind charges hitting pasture blocks would recall all Pokémon in it.
* Fixed the Home on the Range advancement triggering when opening the Pokémon interaction wheel.
* Fixed recipes that use concrete not working on NeoForge.
* Fixed Boltund's model.
* Fixed Cyclizar's textures.

==References==
{{reflist}}

Molang Types

2025-11-08T01:43:25Z

Hiroku: ObjectValue clarification

This is a table of types used in Cobblemon as documented, and the classes they extend from.

{| class="wikitable fixed-header sortable"
!Name!!Type!!Description
|-
|<code>MoValue</code>
|Class
|This is the parent class of all values. Does nothing on it's own, can be treated like <code>Any</code> in Kotlin.
|-
|<code>DoubleValue</code>
|Subclass of MoValue
|Doubles are also used as Integers and Booleans.
|-
|<code>StringValue</code>
|Subclass of MoValue
|Represents a String.
|-
|<code>MoStruct</code>
|Subclass of MoValue
|Used like a map, can get or set using a string key.
|-
|<code>VariableStruct</code>
|Subclass of MoStruct
|A struct that can get and set values.
|-
|<code>ArrayStruct</code>
|Subclass of VariableStruct
|A struct that uses integers as keys. NOTE: For the purpose of documentation, ArrayStruct is notated as <code>ArrayStruct<Type></code> when only one type is expected. All <code>ArrayStruct</code>s have no required types and can be mixed.
|-
|<code>QueryStruct</code>
|Subclass of MoStruct
|A struct that contains functions that can be executed using get. Does not support setting values.
|-
|<code>ObjectValue</code>
|Subclass of QueryStruct
|Cobblemon class used to implement many types. Can get the value of the type, get a double value using <code>asDouble()</code>, and get a string value using <code>asString()</code>. This is used for Players, Pokémon, Battles, and the rest of our implemented Minecraft and Cobblemon types. These may have special functions depending on what's being represented by it.
|}

Molang

2025-11-08T01:42:29Z

Hiroku: We have a specific fork on the gitlab now

Cobblemon uses a [https://gitlab.com/cable-mc/molang modified] version of [https://github.com/bedrockk/MoLang Bedrockk MoLang] to parse and execute MoLang. Updated as of 1.6.1.

==Types==

* [[Molang Types|Types]]

==Functions==

* [[Molang General Functions|General (Standard) Functions]]
* [[Molang Registry Functions|Registry Functions (World, Block, Dimension, Biome)]]
* [[Molang Player Functions|Player Functions]]
* [[Molang Entity Functions|Entity Functions]]
* [[Molang NPC Functions|NPC Functions]]
* [[Molang Battle Functions|Battle Functions]]
* [[Molang BattleActor Functions|BattleActor Functions]]
* [[Molang Pokémon Functions|Pokémon Functions]]
* [[Molang PokémonEntity Functions|PokémonEntity Functions]]
* [[Molang PokémonStore Functions|PokémonStore Functions]]
* [[Molang Party Functions|Party Functions]]
* [[Molang PC Functions|PC Functions]]
* [[Molang SpawningContext Functions|SpawningContext Functions]]
* [[Molang Server Functions|Server Functions]]
* [[Molang Pokédex Functions|Pokédex Functions]]
* [[Molang Species Functions|Species Functions]]

==== Client Only ====

* [[Molang Client General Functions|General Functions]]
* [[Molang Animation Functions|Animation Functions]]

Dialogues

2025-11-01T10:04:06Z

Hiroku: line breaks would help here

Dialogues are a feature that can be used from API or from datapacks to play conversations in a GUI. They display entities, view pages of text, and handle various types of input.

A dialogue that has been registered through a datapack can be opened using the /opendialogue command.

Every case of a MoLang expression can be either a single text property or can be an array of text to support running multiple expressions to produce a result.

[[File:Dialogue_Intro.png|400px|center]]

=Dialogue=

A Dialogue JSON file consists of the following main elements:

- <code>escapeAction</code>: A string or array that defines the action to be taken when the dialogue is escaped. This can be a MoLang expression or a sequence of MoLang expressions.

- <code>speakers</code>: An object that defines the speakers in the dialogue. Each speaker is represented by a key-value pair, where the key is the speaker's identifier and the value is an object that describes what the speaker looks like and their name.

- <code>pages</code>: An array of objects, each representing a page in the dialogue.

==Speakers==

Each speaker is represented by an object with the following properties:

- <code>name</code>: A string or object that defines the speaker's name. This is usually just text. If it's an object, it must have a <code>type</code> property set to <code>"expression"</code> and an <code>expression</code> property that contains a MoLang expression. You would use an expression if you wanted the name to be dynamic.

- <code>face</code>: An object or MoLang expression that defines the speaker's face. This will be rendered in a frame of the GUI. For objects, it must have a <code>type</code> property set to the type of face. The only object type support currently is "standard". The others are done using MoLang expressions rather than an object.

- <code>gibber</code>: An object defining the gibber behaviour. This can be defined as simply <code>{}</code> to use the default settings, or as a full object with any of the properties that you want to set. See the section on <code>gibber</code> further below to see the properties that are available.

===Faces===
The speaker faces can be defined in multiple ways. If it is an object it is going to be a "standard" face type.

===="standard"====
The standard face type is for when the face displayed is not connected to a specific entity in the world but does follow Cobblemon's format of identifier and aspect list. The object must have the following properties:

- <code>modelType</code>: One of 'pokemon', 'npc'

- <code>identifier</code>: The identifier of the Pokémon or NPC, such as <code>cobblemon:bulbasaur</code>.

- <code>aspects</code>: An array of aspects that will be applied to the model.

For example:

"face": {
"type": "artificial",
"modelType": "pokemon",
"identifier": "cobblemon:pikachu",
"aspects": [
"shiny"
]
}

====player====
By using <code>q.player.face()</code> you can make the player's model render for this face.

For example:

"face": "q.player.face();"

====npc====
By using <code>q.npc.face()</code> you can show a direct reference to the NPC you're having the dialogue with, if this was dialogue started with an NPC entity.

For example:

"face": "q.npc.face();"

===Gibber===
An additional feature of dialogues is having the text appear gradually and with a simplistic set of tones that mimic speech, referred to here as gibbering. Gibbering has many options and all have sensible defaults. The properties available are as follows:

- <code>graduallyShowText</code>: A boolean which, when true, will cause the text in the GUI to gradually be typed out. When false, gibbering sound effects will play but all of the text will be visible from the beginning. Defaults to true.

- <code>allowSkip</code>: Whether or not clicking in the dialogue box will skip the gibbering and display all of the text at once. If false, the player must wait until the entirety of the gibbering has occurred before they can continue to the next page.

<code>step</code>: The number of characters between each gibber. A gibber will play for the current character index and then, after some time interval, this step will be used to move to a later character in the text to play the next gibber. When gradually revealing text is on, a larger step will mean that text will appear in larger chunks. Defaults to 4 characters.

<code>interval</code>: The time (in seconds) between each gibber sound. A smaller value will make the sounds come more rapidly, and the text will appear more quickly if gradually showing text. Defaults to 0.1 seconds.

<code>minPitch</code>: The minimum pitch multiplier that could be used when randomly selecting a tone. Defaults to 0.8.

<code>maxPitch</code>: The maximum pitch multiplier that could be used when randomly selecting a tone. Defaults to 1.2.

<code>minVolume</code>: The minimum volume multiplier that could be used when randomly selecting a tone. Defaults to 0.75.

<code>maxVolume</code>: The maximum volume multiplier that could be used when randomly selecting a tone. Defaults to 1.1.

<code>sounds</code>: A list of resource locations indicating which sound events should be chosen from when playing a gibber. It can be any number of sounds. Defaults to three sounds: <code>"cobblemon:entity.villager.npc1"</code>, <code>"cobblemon:entity.villager.npc2"</code>, and <code>"cobblemon:entity.villager.npc1"</code>.

==Pages==

Each page is represented by an object with the following properties:

- <code>id</code>: A string that uniquely identifies the page. This is needed for instances where you might want to jump to a specific page. Page numbers could be used, but you should use page IDs.

- <code>speaker</code>: A string that specifies the speaker's identifier. This depends upon the speaker by this identifier existing in the speakers list.

- <code>lines</code>: An array of strings or objects, each representing a line of text. If it's an object, it must have a <code>type</code> property set to <code>"expression"</code> and an <code>expression</code> property that contains a MoLang expression that evaluates to a string. You would use an expression if you want to include variables to make dynamic text.

- <code>input</code>: An object or string that defines the input prompt. If it's an object, it must have a <code>type</code> property set to <code>"option"</code>, <code>"text"</code>, <code>"auto-continue"</code>, or <code>"none"</code>, and other properties depending on the type. By default, the input value will be <code>none</code>.

- <code>gibber</code>: A page-specific gibber configuration. See above for more information about gibber objects. By default this is null, and will therefore fallback to the gibber that is on the <code>speaker</code> for this page, if any is.

- <code>clientActions</code>: A list of MoLang expressions that will run on the client after the first frame of the page has been rendered on the client. This can be used to play sounds with <code>"q.sound(...)"</code>, or even play animations on the face being rendered (if it is a Bedrock animated entity) by doing, for example, <code>"q.face.play_animation('win');"</code>.

- <code>escapeAction</code>: A string or array that defines the action to be taken when the page is escaped. This can be a MoLang expression or a sequence of MoLang expressions.

- <code>background</code>: A resource location to use as the background texture for the dialogue box. By default this is null, which will result in Cobblemon's internal texture to be used.

==Input Types==

The <code>input</code> property in a page object can have different structures depending on the <code>type</code>.

For all inputs that specify an <code>action</code> property which is set to a MoLang expression, you can access the time it took for them to make that input using <code>v.seconds_taken_to_input</code>.

==="option"===
The input is a set of options. The object must have an <code>options</code> property that is an array of objects, each representing an option. It can also specify whether the options should be displayed vertically or horizontally by whether or not the <code>vertical</code> property is true or false.

Each option object can have the following properties:

- <code>value</code>: The unique value of the dialogue option. This is not displayed to the player and is instead used to reference this option from scripts.

- <code>text</code>The display text for the option. This can be a simple string or can be an object

- <code>action</code>: The MoLang expression to run when the user chooses the option.

- <code>isVisible</code>: A MoLang expression which must return either true or false. If false, the option will not be visible for the player. Defaults to true.

- <code>isSelectable</code>: A MoLang expression which must return either true or false. If false, the option will be greyed out (but only if it is visible). Defaults to true.

[[File:Dialogue_Options.png|600px|center]]

==="text"===
The input is a text field. The <code>action</code> property is a MoLang expression that will run when the player hits enter with text typed in. As specified earlier, you can check the text that they input using <code>v.selected_option</code> inside of the MoLang expression.

[[File:Dialogue_Input.png|600px|center]]

==="auto-continue"===
The dialogue will automatically progress after some period of time. There are several optional properties for this.

- <code>delay</code>: The delay in seconds until it progresses. By default this is 5 seconds.

- <code>allowSkip</code>: Whether the user is able to skip the delay by clicking. By default this is true. If false, the player will be forced to wait for the delay.

- <code>showTimer</code>: Whether a bar will be displayed to indicate how much more time the player has until it auto-continues. Defaults to false.

- <code>action</code>: A MoLang expression that runs when either the player clicks (only when <code>allowSkip</code> is true) or the delay finishes. By default this moves to the next page.

==="none"===
There is no input except that it waits until the user clicks to continue. The object can have an <code>action</code> property that defines the MoLang expression to run when the player clicks. By default, it moves to the next page.

===Timeouts===
All input types except for <code>"none"</code> and <code>"autocontinue"</code> can have a 'timeout' object which allows you to apply time constraints to the player viewing the page.

The timeout object can have 3 properties:

- <code>duration</code>: The time, in seconds, that the player will have to complete the input. By default this is 10 seconds.

- <code>showTimer</code>: Whether or not a bar will be shown to show the player how much time they have left. By default this is true.

- <code>action</code>: A MoLang expression to run if they do not enter the input in time. By default this will close the dialogue.

[[File:Dialogue_Timer.png|600px|center]]

=Example=
The following example is built-in to the mod, labelled "example".

{
"escapeAction": "q.dialogue.set_page('quitter')",
"speakers": {
"pikachu": {
"name": "The Voice of Hiro",
"face": {
"type": "artificial",
"modelType": "pokemon",
"identifier": "cobblemon:pikachu",
"aspects": [
"shiny"
]
},
"gibber": {
"step": 2,
"interval": 0.07,
"allowSkip": false
}
},
"player": {
"face": "q.player.face();",
"name": {
"type": "expression",
"expression": "q.player.username"
}
}
},
"pages": [
{
"id": "player-chat",
"speaker": "player",
"lines": [
{
"type": "expression",
"expression": "'Hello, I\\'m ' + q.player.username + '!'"
}
]
},
{
"speaker": "pikachu",
"lines": [
{
"type": "expression",
"expression": "'Nice to meet you, ' + q.player.username + '! Welcome to the world of dialogues!'"
}
]
},
{
"id": "intro",
"speaker": "pikachu",
"lines": [ "Do you want to learn more?"],
"input": {
"type": "option",
"vertical": false,
"options": [
{
"text": "Yes",
"value": "yes",
"action": [
"v.player_response = 'That sounds great!';",
"v.next_page = 'page1';",
"q.dialogue.set_page('player-surrogate');"
]
},
{
"text": "No",
"value": "no",
"action": [
"v.player_response = 'No, I really don\\'t care.';",
"v.next_page = 'quitter';",
"q.dialogue.set_page('player-surrogate');"
]
},
{
"text": "Sword!",
"value": "sword",
"isVisible": "q.player.main_held_item.is_of('minecraft:iron_sword')",
"isSelectable": "q.player.data.scared_npc != true;",
"action": [
"v.player_response = 'How about you die! Muahahaha!';",
"v.next_page = 'sword';",
"q.dialogue.set_page('player-surrogate');"
]
},
{
"text": "Sword again!",
"value": "sword2",
"isVisible": "q.player.main_held_item.is_of('minecraft:iron_sword')",
"isSelectable": "q.player.data.scared_npc == true;",
"action": [
"v.player_response = 'How about you die... again! Muahahaha!';",
"v.next_page = 'sword-again';",
"q.dialogue.set_page('player-surrogate');"
]
}
]
}
},
{
"id": "player-surrogate",
"speaker": "player",
"gibber": {},
"lines": [
{
"type": "expression",
"expression": "v.player_response;"
}
],
"input": "q.dialogue.set_page(v.next_page);"
},
{
"id": "page1",
"speaker": "pikachu",
"lines": [
"Well you see, this is a dialogue.",
"You can have multiple pages, and each page can have multiple lines."
]
},
{
"id": "page2",
"speaker": "pikachu",
"lines": ["On an unrelated note, did you know that I'm deeply afraid of iron swords? Anyway, cya!"],
"input": {
"type": "auto-continue",
"delay": 5,
"allowSkip": true,
"action": "q.dialogue.close();"
}
},
{
"id": "quitter",
"speaker": "pikachu",
"lines": ["Fine. Be that way."],
"input": "q.dialogue.close();",
"escapeAction": "q.dialogue.close();"
},
{
"id": "sword",
"speaker": "pikachu",
"lines": ["Oh god no, please don't hurt me!"],
"escapeAction": "q.dialogue.input('');",
"input": [
"t.data = q.player.data();",
"t.data.scared_npc = true;",
"q.player.save_data();",
"q.dialogue.close();"
]
},
{
"id": "sword-again",
"speaker": "pikachu",
"lines": ["I'm ready for you this time. YOU will die today!"],
"escapeAction": "0",
"input": {
"type": "option",
"vertical": true,
"timeout": {
"delay": 6,
"action": "q.dialogue.input('stand');"
},
"options": [
{
"text": "Parry his attack.",
"value": "parry",
"action": [
"v.reaction = 'parry';",
"q.dialogue.set_page('sword-again-decided');"
]
},
{
"text": "Stand perfectly still.",
"value": "stand",
"action": [
"v.reaction = 'stand still';",
"q.dialogue.set_page('sword-again-decided');"
]
},
{
"text": "Drop your sword.",
"value": "drop",
"action": [
"v.reaction = 'drop your sword';",
"q.dialogue.set_page('sword-again-decided');"
]
}
]
}
},
{
"id": "sword-again-decided",
"lines": [
{
"type": "expression",
"expression": "v.reaction == 'parry' ? 'You parry his attack and kill him.' : (v.reaction == 'stand still' ? 'He kills you.' : 'You drop your sword and he kills you.')"
}
],
"input": {
"type": "auto-continue",
"delay": 3,
"allowSkip": false,
"showTimer": false,
"action": "q.dialogue.set_page('sword-again-reaction');"
}
},
{
"id": "sword-again-reaction",
"speaker": "pikachu",
"lines": [
{
"type": "expression",
"expression": "'Nah, I\\'m just kidding. Interesting that you chose to ' + v.reaction + ' though.'"
}
]
},
{
"id": "name-question",
"speaker": "pikachu",
"lines": [ "Here's a puzzle though... What is my name? Lowercase only."],
"input": {
"type": "text",
"timeout": {
"delay": 10,
"action": "q.dialogue.set_page('too-slow');"
},
"action": [
"q.dialogue.set_page('name-speak');",
"t.data = q.player.data();"
]
}
},
{
"id": "name-speak",
"speaker": "player",
"lines": [
{
"type": "expression",
"expression": "'Your name is ' + v.selected_option + ', right?'"
}
],
"input": "q.dialogue.set_page('name-guess');"
},
{
"id": "name-guess",
"speaker": "pikachu",
"lines": [
{
"type": "expression",
"expression": "v.selected_option == 'hiroku' ? 'Correct! You know things that you shouldn\\'t...' : ('Wrong! I\\'m not \"' + v.selected_option + '\". Whoever that is.')"
}
],
"input": {
"type": "auto-continue",
"delay": 5,
"allowSkip": true,
"action": "q.dialogue.set_page('farewell');"
}
},
{
"id": "farewell",
"speaker": "pikachu",
"lines": ["Anyway, I'm done with this dialogue. Bye!"],
"input": "q.dialogue.close();"
},
{
"id": "too-slow",
"speaker": "pikachu",
"lines": ["Don't know? Sad. Well I don't know your name either, so I guess we're even."],
"input": "q.dialogue.close()"
}
]
}

Dialogues

2025-04-19T05:14:07Z

Hiroku: Added gibber, clientActions, and background information

Dialogues are a feature that can be used from API or from datapacks to play conversations in a GUI. They display entities, view pages of text, and handle various types of input.

A dialogue that has been registered through a datapack can be opened using the /opendialogue command.

Every case of a MoLang expression can be either a single text property or can be an array of text to support running multiple expressions to produce a result.

[[File:Dialogue_Intro.png|400px|center]]

=Dialogue=

A Dialogue JSON file consists of the following main elements:

- <code>escapeAction</code>: A string or array that defines the action to be taken when the dialogue is escaped. This can be a MoLang expression or a sequence of MoLang expressions.

- <code>speakers</code>: An object that defines the speakers in the dialogue. Each speaker is represented by a key-value pair, where the key is the speaker's identifier and the value is an object that describes what the speaker looks like and their name.

- <code>pages</code>: An array of objects, each representing a page in the dialogue.

==Speakers==

Each speaker is represented by an object with the following properties:

- <code>name</code>: A string or object that defines the speaker's name. This is usually just text. If it's an object, it must have a <code>type</code> property set to <code>"expression"</code> and an <code>expression</code> property that contains a MoLang expression. You would use an expression if you wanted the name to be dynamic.

- <code>face</code>: An object or MoLang expression that defines the speaker's face. This will be rendered in a frame of the GUI. For objects, it must have a <code>type</code> property set to the type of face. The only object type support currently is "standard". The others are done using MoLang expressions rather than an object.

- <code>gibber</code>: An object defining the gibber behaviour. This can be defined as simply <code>{}</code> to use the default settings, or as a full object with any of the properties that you want to set. See the section on <code>gibber</code> further below to see the properties that are available.

===Faces===
The speaker faces can be defined in multiple ways. If it is an object it is going to be a "standard" face type.

===="standard"====
The standard face type is for when the face displayed is not connected to a specific entity in the world but does follow Cobblemon's format of identifier and aspect list. The object must have the following properties:

- <code>modelType</code>: One of 'pokemon', 'npc'

- <code>identifier</code>: The identifier of the Pokémon or NPC, such as <code>cobblemon:bulbasaur</code>.

- <code>aspects</code>: An array of aspects that will be applied to the model.

For example:

"face": {
"type": "artificial",
"modelType": "pokemon",
"identifier": "cobblemon:pikachu",
"aspects": [
"shiny"
]
}

====player====
By using <code>q.player.face()</code> you can make the player's model render for this face.

For example:

"face": "q.player.face();"

====npc====
By using <code>q.npc.face()</code> you can show a direct reference to the NPC you're having the dialogue with, if this was dialogue started with an NPC entity.

For example:

"face": "q.npc.face();"

===Gibber===
An additional feature of dialogues is having the text appear gradually and with a simplistic set of tones that mimic speech, referred to here as gibbering. Gibbering has many options and all have sensible defaults. The properties available are as follows:

- <code>graduallyShowText</code>: A boolean which, when true, will cause the text in the GUI to gradually be typed out. When false, gibbering sound effects will play but all of the text will be visible from the beginning. Defaults to true.

- <code>allowSkip</code>: Whether or not clicking in the dialogue box will skip the gibbering and display all of the text at once. If false, the player must wait until the entirety of the gibbering has occurred before they can continue to the next page.

<code>step</code>: The number of characters between each gibber. A gibber will play for the current character index and then, after some time interval, this step will be used to move to a later character in the text to play the next gibber. When gradually revealing text is on, a larger step will mean that text will appear in larger chunks. Defaults to 4 characters.

<code>interval</code>: The time (in seconds) between each gibber sound. A smaller value will make the sounds come more rapidly, and the text will appear more quickly if gradually showing text. Defaults to 0.1 seconds.

<code>minPitch</code>: The minimum pitch multiplier that could be used when randomly selecting a tone. Defaults to 0.8.

<code>maxPitch</code>: The maximum pitch multiplier that could be used when randomly selecting a tone. Defaults to 1.2.

<code>minVolume</code>: The minimum volume multiplier that could be used when randomly selecting a tone. Defaults to 0.75.

<code>maxVolume</code>: The maximum volume multiplier that could be used when randomly selecting a tone. Defaults to 1.1.

<code>sounds</code>: A list of resource locations indicating which sound events should be chosen from when playing a gibber. It can be any number of sounds. Defaults to three sounds: <code>"cobblemon:entity.villager.npc1"</code>, <code>"cobblemon:entity.villager.npc2"</code>, and <code>"cobblemon:entity.villager.npc1"</code>.

==Pages==

Each page is represented by an object with the following properties:

- <code>id</code>: A string that uniquely identifies the page. This is needed for instances where you might want to jump to a specific page. Page numbers could be used, but you should use page IDs.

- <code>speaker</code>: A string that specifies the speaker's identifier. This depends upon the speaker by this identifier existing in the speakers list.

- <code>lines</code>: An array of strings or objects, each representing a line of text. If it's an object, it must have a <code>type</code> property set to <code>"expression"</code> and an <code>expression</code> property that contains a MoLang expression that evaluates to a string. You would use an expression if you want to include variables to make dynamic text.

- <code>input</code>: An object or string that defines the input prompt. If it's an object, it must have a <code>type</code> property set to <code>"option"</code>, <code>"text"</code>, <code>"auto-continue"</code>, or <code>"none"</code>, and other properties depending on the type. By default, the input value will be <code>none</code>.

- <code>gibber</code>: A page-specific gibber configuration. See above for more information about gibber objects. By default this is null, and will therefore fallback to the gibber that is on the <code>speaker</code> for this page, if any is.

- <code>clientActions</code>: A list of MoLang expressions that will run on the client after the first frame of the page has been rendered on the client. This can be used to play sounds with <code>"q.sound(...)"</code>, or even play animations on the face being rendered (if it is a Bedrock animated entity) by doing, for example, <code>"q.face.play_animation('win');"</code>.

- <code>escapeAction</code>: A string or array that defines the action to be taken when the page is escaped. This can be a MoLang expression or a sequence of MoLang expressions.

- <code>background</code>: A resource location to use as the background texture for the dialogue box. By default this is null, which will result in Cobblemon's internal texture to be used.

==Input Types==

The <code>input</code> property in a page object can have different structures depending on the <code>type</code>.

For all inputs that specify an <code>action</code> property which is set to a MoLang expression, you can access the time it took for them to make that input using <code>v.seconds_taken_to_input</code>.

==="option"===
The input is a set of options. The object must have an <code>options</code> property that is an array of objects, each representing an option. It can also specify whether the options should be displayed vertically or horizontally by whether or not the <code>vertical</code> property is true or false.

Each option object can have the following properties:

- <code>value</code>: The unique value of the dialogue option. This is not displayed to the player and is instead used to reference this option from scripts.
- <code>text</code>The display text for the option. This can be a simple string or can be an object
- <code>action</code>: The MoLang expression to run when the user chooses the option.
- <code>isVisible</code>: A MoLang expression which must return either true or false. If false, the option will not be visible for the player. Defaults to true.
- <code>isSelectable</code>: A MoLang expression which must return either true or false. If false, the option will be greyed out (but only if it is visible). Defaults to true.

[[File:Dialogue_Options.png|600px|center]]

==="text"===
The input is a text field. The <code>action</code> property is a MoLang expression that will run when the player hits enter with text typed in. As specified earlier, you can check the text that they input using <code>v.selected_option</code> inside of the MoLang expression.

[[File:Dialogue_Input.png|600px|center]]

==="auto-continue"===
The dialogue will automatically progress after some period of time. There are several optional properties for this.

- <code>delay</code>: The delay in seconds until it progresses. By default this is 5 seconds.

- <code>allowSkip</code>: Whether the user is able to skip the delay by clicking. By default this is true. If false, the player will be forced to wait for the delay.

- <code>showTimer</code>: Whether a bar will be displayed to indicate how much more time the player has until it auto-continues. Defaults to false.

- <code>action</code>: A MoLang expression that runs when either the player clicks (only when <code>allowSkip</code> is true) or the delay finishes. By default this moves to the next page.

==="none"===
There is no input except that it waits until the user clicks to continue. The object can have an <code>action</code> property that defines the MoLang expression to run when the player clicks. By default, it moves to the next page.

===Timeouts===
All input types except for <code>"none"</code> and <code>"autocontinue"</code> can have a 'timeout' object which allows you to apply time constraints to the player viewing the page.

The timeout object can have 3 properties:

- <code>duration</code>: The time, in seconds, that the player will have to complete the input. By default this is 10 seconds.

- <code>showTimer</code>: Whether or not a bar will be shown to show the player how much time they have left. By default this is true.

- <code>action</code>: A MoLang expression to run if they do not enter the input in time. By default this will close the dialogue.

[[File:Dialogue_Timer.png|600px|center]]

=Example=
The following example is built-in to the mod, labelled "example".

{
"escapeAction": "q.dialogue.set_page('quitter')",
"speakers": {
"pikachu": {
"name": "The Voice of Hiro",
"face": {
"type": "artificial",
"modelType": "pokemon",
"identifier": "cobblemon:pikachu",
"aspects": [
"shiny"
]
},
"gibber": {
"step": 2,
"interval": 0.07,
"allowSkip": false
}
},
"player": {
"face": "q.player.face();",
"name": {
"type": "expression",
"expression": "q.player.username"
}
}
},
"pages": [
{
"id": "player-chat",
"speaker": "player",
"lines": [
{
"type": "expression",
"expression": "'Hello, I\\'m ' + q.player.username + '!'"
}
]
},
{
"speaker": "pikachu",
"lines": [
{
"type": "expression",
"expression": "'Nice to meet you, ' + q.player.username + '! Welcome to the world of dialogues!'"
}
]
},
{
"id": "intro",
"speaker": "pikachu",
"lines": [ "Do you want to learn more?"],
"input": {
"type": "option",
"vertical": false,
"options": [
{
"text": "Yes",
"value": "yes",
"action": [
"v.player_response = 'That sounds great!';",
"v.next_page = 'page1';",
"q.dialogue.set_page('player-surrogate');"
]
},
{
"text": "No",
"value": "no",
"action": [
"v.player_response = 'No, I really don\\'t care.';",
"v.next_page = 'quitter';",
"q.dialogue.set_page('player-surrogate');"
]
},
{
"text": "Sword!",
"value": "sword",
"isVisible": "q.player.main_held_item.is_of('minecraft:iron_sword')",
"isSelectable": "q.player.data.scared_npc != true;",
"action": [
"v.player_response = 'How about you die! Muahahaha!';",
"v.next_page = 'sword';",
"q.dialogue.set_page('player-surrogate');"
]
},
{
"text": "Sword again!",
"value": "sword2",
"isVisible": "q.player.main_held_item.is_of('minecraft:iron_sword')",
"isSelectable": "q.player.data.scared_npc == true;",
"action": [
"v.player_response = 'How about you die... again! Muahahaha!';",
"v.next_page = 'sword-again';",
"q.dialogue.set_page('player-surrogate');"
]
}
]
}
},
{
"id": "player-surrogate",
"speaker": "player",
"gibber": {},
"lines": [
{
"type": "expression",
"expression": "v.player_response;"
}
],
"input": "q.dialogue.set_page(v.next_page);"
},
{
"id": "page1",
"speaker": "pikachu",
"lines": [
"Well you see, this is a dialogue.",
"You can have multiple pages, and each page can have multiple lines."
]
},
{
"id": "page2",
"speaker": "pikachu",
"lines": ["On an unrelated note, did you know that I'm deeply afraid of iron swords? Anyway, cya!"],
"input": {
"type": "auto-continue",
"delay": 5,
"allowSkip": true,
"action": "q.dialogue.close();"
}
},
{
"id": "quitter",
"speaker": "pikachu",
"lines": ["Fine. Be that way."],
"input": "q.dialogue.close();",
"escapeAction": "q.dialogue.close();"
},
{
"id": "sword",
"speaker": "pikachu",
"lines": ["Oh god no, please don't hurt me!"],
"escapeAction": "q.dialogue.input('');",
"input": [
"t.data = q.player.data();",
"t.data.scared_npc = true;",
"q.player.save_data();",
"q.dialogue.close();"
]
},
{
"id": "sword-again",
"speaker": "pikachu",
"lines": ["I'm ready for you this time. YOU will die today!"],
"escapeAction": "0",
"input": {
"type": "option",
"vertical": true,
"timeout": {
"delay": 6,
"action": "q.dialogue.input('stand');"
},
"options": [
{
"text": "Parry his attack.",
"value": "parry",
"action": [
"v.reaction = 'parry';",
"q.dialogue.set_page('sword-again-decided');"
]
},
{
"text": "Stand perfectly still.",
"value": "stand",
"action": [
"v.reaction = 'stand still';",
"q.dialogue.set_page('sword-again-decided');"
]
},
{
"text": "Drop your sword.",
"value": "drop",
"action": [
"v.reaction = 'drop your sword';",
"q.dialogue.set_page('sword-again-decided');"
]
}
]
}
},
{
"id": "sword-again-decided",
"lines": [
{
"type": "expression",
"expression": "v.reaction == 'parry' ? 'You parry his attack and kill him.' : (v.reaction == 'stand still' ? 'He kills you.' : 'You drop your sword and he kills you.')"
}
],
"input": {
"type": "auto-continue",
"delay": 3,
"allowSkip": false,
"showTimer": false,
"action": "q.dialogue.set_page('sword-again-reaction');"
}
},
{
"id": "sword-again-reaction",
"speaker": "pikachu",
"lines": [
{
"type": "expression",
"expression": "'Nah, I\\'m just kidding. Interesting that you chose to ' + v.reaction + ' though.'"
}
]
},
{
"id": "name-question",
"speaker": "pikachu",
"lines": [ "Here's a puzzle though... What is my name? Lowercase only."],
"input": {
"type": "text",
"timeout": {
"delay": 10,
"action": "q.dialogue.set_page('too-slow');"
},
"action": [
"q.dialogue.set_page('name-speak');",
"t.data = q.player.data();"
]
}
},
{
"id": "name-speak",
"speaker": "player",
"lines": [
{
"type": "expression",
"expression": "'Your name is ' + v.selected_option + ', right?'"
}
],
"input": "q.dialogue.set_page('name-guess');"
},
{
"id": "name-guess",
"speaker": "pikachu",
"lines": [
{
"type": "expression",
"expression": "v.selected_option == 'hiroku' ? 'Correct! You know things that you shouldn\\'t...' : ('Wrong! I\\'m not \"' + v.selected_option + '\". Whoever that is.')"
}
],
"input": {
"type": "auto-continue",
"delay": 5,
"allowSkip": true,
"action": "q.dialogue.set_page('farewell');"
}
},
{
"id": "farewell",
"speaker": "pikachu",
"lines": ["Anyway, I'm done with this dialogue. Bye!"],
"input": "q.dialogue.close();"
},
{
"id": "too-slow",
"speaker": "pikachu",
"lines": ["Don't know? Sad. Well I don't know your name either, so I guess we're even."],
"input": "q.dialogue.close()"
}
]
}

Tutorials/Creating A Custom Pokemon

2024-11-09T23:22:12Z

Hiroku: Fakemon generator update

{{TOC|right}}
== Preface ==
This beginner friendly step-by-step guide will walk you through adding custom Pokémon through resource and data packs. Cobblemon addons have certain requirements in order to work in Minecraft. There are several mistakes you can make along the way that can cause the game to crash. This tutorial was created in collaboration with Cobblemon community members who have made these mistakes.

Knowledge of coding and resource packs is not necessary! In this tutorial, you will mostly be replacing data in existing file templates and building a custom Pokémon out of cubes. Experience with Blockbench is recommended, but never required! If at any point your addon is not working, you can look for help in the Cobblemon discord server.

== Overview ==
This guide will teach you:
* How to format your models and animations
* Where to place your files
* How to configure stats for your Pokémon
* How to configure evolutions for your Pokémon
* How to configure spawning for your Pokémon

What you will be creating are two things together; a resource pack and a data pack.
Resource packs primarily operate within the assets folder, while data packs operate within the data folder.

The reason we need to make two different things is that the data pack handles all the information (stuff a server needs), and the resource pack handles all the assets like models, textures, and more (stuff the client needs).

In this guide we will be creating both as a single pack.

As a brief summary:
* <code>Data packs</code> as a stand-alone are useful for servers, as servers have no need for assets
* <code>Resource packs</code> are useful for players playing on servers that already have the data
* A single pack with data pack and resource pack files together are useful to players who are playing single player, and need both the data and the assets. These combined data and resource files are often called <code>Addons</code>.

== Recommended Tools ==
While creating an addon can be done with a browser and some default PC tools, it's highly recommended that you download some of the following software. They can be very helpful if you want to make more than one custom Pokémon.
* '''Blockbench Desktop App''' - It will make accessing assets easier
* '''A Text Editor''' - They can be helpful for editing multiple files at once
** Recommendations:
**# Visual Studio Code
**# Notepad++
* '''Zip File Software''' - They can help you zip up your addon to be shared
** Recommendations:
**# 7zip


Cobblemon addons use a lot of <code>json</code> files. These are human-readable sets of data for Minecraft to read. Here are some JSON terms to help you understand these files.

'''JSON terminology'''
* <code>"key": "value"</code> - Property, aka "key-value pair". <code>key</code> must have quotes around it in JSON. <code>value</code> can be any of the following:
* <code>{}</code> - Object. contains properties, as above.
* <code>[]</code> - Array. Is an ordered list of "entries" of any of the other data types.
* <code>"abc"</code> - String. Quotes around any set of characters. Cannot have line returns in the middle of them.
* <code>1</code> - Number. Doesn't have quotes. Some values can be decimal friendly.
* <code>true/false</code> - Boolean. Doesn't have quotes. One of possibly either `true` or `false`

'''JSON quirks'''
* Must have commas between properties.
* Cannot have commas after properties if there's not another property.
** You can't have any commas before any sort of closing bracket.

== Creating a Custom Pokémon ==
=== Part 1: 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 new text file and name it <code>pack.mcmeta</code>
#* Ensure that it doesn't end in other file extensions like .txt. You may need to search "how to show file extensions" for whatever operating system you have.
#* This file tells Minecraft "this is a resourcepack/datapack"
# Open the file and insert the following data:
#* Hover over the underlined text to see more information.
{
"<abbr title="This lets Minecraft know that it is a datapack">pack</abbr>": {
"<abbr title="Here you will list the pack format number for a specific version of Minecraft">pack_format</abbr>": <abbr title="As of 1.20.1, the current resourcepack format number is 15. But it will still load if this number isn't correct!">15</abbr>,
"<abbr title="Here you will write a short description of your datapack">description</abbr>": "<abbr title="Your short datapack description">Example description</abbr>"
}
}
# <li value=3> Save the file and put it aside for now.
# Create a series of folders arranged like the following example:
==== Folder Structure ====
<div class="treeview">
*''(addon name)''
** '''pack.mcmeta'''
**assets
***cobblemon
****bedrock
*****pokemon
******animations
*******<folder named after your pokemon>
******models
*******<folder named after your pokemon>
******posers
******resolvers
*******<folder named after your pokemon>
****lang
****textures
*****pokemon
******<folder named after your pokemon>
**data
***cobblemon
****spawn_pool_world
****species
*****custom
</div>
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.

=== Part 2: Create your Pokémon's assets in Blockbench ===
'''This is not a guide to Blockbench.''' This '''extensive''' part of the tutorial will guide you in the creation of a compatible Cobblemon model. Cobblemon models have certain requirements in order to work in Minecraft. There are several mistakes you might make when creating a model which may result in you having to start all over.

This part of the guide is a slightly watered down version of the [[Tutorials/Creating A Model|model creation tutorial]] to keep things more beginner friendly.

==== Step 1: Get access to Blockbench ====
Blockbench is a free 3D Modeling program capable of doing everything you need to make a Cobblemon model. You can create a model, paint it, and animate it all at the same time using Blockbench. Watching some Blockbench tutorials before getting started is recommended.

# Open your browser and go to https://www.blockbench.net
# <code>DOWNLOAD</code> the app '''or''' click on <code>OPEN WEB APP</code>

Blockbench can also be used on mobile devices!

'''Disclaimer''': This guide is tailored towards the Blockbench app on PC.

==== Step 2: Create the model file ====
You will be creating the project file in Blockbench. Although this step seems simple, if you choose the wrong model type or UV mode then it will not work with Cobblemon's custom Pokémon system.

# Open up Blockbench
# Click on File > New > Bedrock Entity
# '''In lowercase only''', type the name of your custom Pokémon in both <code>File Name</code> and <code>Model Identifier</code>
# Make sure Default UV Mode is set to <code>Box UV</code>
# Leave <code>Texture Size</code> alone
# Click <code>Confirm</code>

You have created the foundation of your model file!

Despite being for the Java version of Minecraft, Cobblemon uses Bedrock entities to allow for flexible animations.

==== Step 3: Creating cubes the right way ====
There are many ways to create a Pokémon model. There is no “right way” to make a cube to build your design; however, '''there are several things that can break your model involving these cubes.'''

Before you get started, you should know that there are several things you should '''never''' do when creating cubes. As you create your model, keep the following tips in mind:
* '''Don't''' use capital letters when naming your cubes or groups. Minecraft might crash trying to read them.
** '''Always stick with lowercase letters when naming things!'''
* '''Don't''' use decimals in <code>Size</code> values! Minecraft can't handle "2.5" pixels properly.
** These decimal values will get rounded up or down in game and break the geometry.
** <code>Position</code>, <code>Inflate</code>, <code>Pivot Point</code>, and <code>Rotation</code> values can use decimals without issues.
* '''Don't''' change the UV Mode of the cube. They should all be “Box UV” by default.
** If just one cube is changed to Per-face UV, the whole resource pack will refuse to load.
* '''Don't''' forget to save! It can take hours or days to make your model. Save often!
* Make sure your model is facing <code>North</code>! '''It should be facing towards the N on the floor.'''
** It may walk backwards or sideways in game if not facing North.
* Your model does not always need to be on a 1 to 1 scale. It can be sized down in game to affect texture details.

With that in mind, you can start creating cubes in Blockbench!
# Create a cube by clicking the <code>Add Cube</code> button under "Outliner" or press Ctrl + N
# Change the elements of this cube as needed
# Repeat these steps when more cubes are needed to build your model

'''Tip''': You can change one of the size values to 0 to create a 2D plane. These are usually called <code>panes</code> and can be used to create flat textures for certain situations. Remember to paint the back side of these panes!

==== Step 4: Arrange your cubes into "bones" ====
As you create the cubes for your model, you will want group them into folders. These groups of cubes are called <code>bones</code>. Only bones can be selected in the <code>Animate</code> tab. Bones can even go inside of other bones. You are essentially building a skeleton. Sort these bones out to make animating the model easier later on.
[[File:Example_of_Arm.png|thumb|350px|caption|Sceptile's arm bone structure.]]
# Decide which cubes should be grouped together as a <code>bone</code>.example: grouping several cubes together to make a "foot" bone. Then grouping other cubes to make a "leg" bone.
# Create a group by clicking the <code>Add Group</code> button under "Outliner" or press Ctrl + G
# Name this new bone. It is recommended to use names of body parts like arm, arm 2, hand, etc.
# Click and drag associated cubes into this new bone folder.
# Assign an appropriate pivot point to this new bone. This controls the location it will rotate from.
# Repeat these steps when more bones are needed for animation

Bones can use the same properties under the "Element" section. How you use these properties with bones is up to you. You can reference official models that have a similar body type to your custom Pokémon.

==== Step 5: Arranging your bones the right way ====
There are many ways to create a Pokémon model. Unfortunately, there is a "right way" to arrange your bones so it won't break something in game; however, '''this will never restrict your creative freedom!''' There are only 2 "bones" required to make your model functional with Cobblemon and it shouldn't interfere with your design.

'''You may want to come back to these steps after creating all of the cubes necessary to make your model complete'''
[[File:CharmanderAndItsBones.png|thumb|350px|caption|Charmander with its "root folder" and "head" bone.]]
# Create a new bone group and name this folder after your custom Pokémon
# Drag all bones and cubes into this new folder until it holds everything.
#*This folder that holds everything is known as the <code>root folder</code>
# Ensure the XYZ Pivot Point values of the root folder are all at 0.
#* This stops the model from sinking into the ground in game.
# Create or pick the <code>head</code> bone for your Pokémon.
#*This will be the bone that rotates when it uses the "look" animation.
#* Sometimes a Pokémon wont have a traditional head like Spheal for example. You'll have to get creative with which bone shall be the head bone.
# Ensure this head bone is named <code>head</code>.
#* You mostly name it "head" for simplicity with the <code>poser file</code>.
#* If your Pokémon is shaped differently, then just remember to use the name of the bone that works best in its poser file.

The root folder is crucial for making the in-game model's position look exactly the way it does in Blockbench. If the Pivot values are not 0, then it will shift in some direction.

Having a head bone allows the Pokémon to use the look animation without issues. In the past, many creators have unknowingly assigned the head bone as "head" in their poser files despite not having an actual bone with that name in their model. '''If the model did not have this matching <code>head</code> bone, the game would crash!'''

==== Step 6: Create your textures ====
This step will only help you with the creation of the files. Any artistic help will have to be sourced from somewhere else. It is recommended to watch some tutorials or ask for help in the Cobblemon discord server.
[[File:PaintingACharmander.png|thumb|450px|caption|Charmander getting painted in Blockbench.]]
# Click on "Create Texture" or press Ctrl+Shift+T.
# Name the texture after your Pokémon.
# Ensure Pixel Density is set to <code>16x</code>
#* Other densities may break textures.
#* The model can later be sized up or down to affect details.
# Click confirm. The default settings are usually fine.
# Navigate to the <code>Paint</code> tab in the top-right corner of Blockbench
# Paint the model until satisfied.
# Click the Save icon on your texture, or press Ctrl+S
# Make sure the PNG is called <code><pokemon>.png</code>
# Place this PNG in your Pokémon's <code>texture</code> folder of your addon.
#* The folder path for this PNG should be like so: <code> <your_addon>/assets/cobblemon/textures/pokemon/<your_pokemon>/<pokemon>.png </code>
# Repeat these steps for the shiny texture. (optional)

==== Step 7: Animate your Pokémon ====
Again, this step will only help you with the creation of the files. Animations are not required to make your Pokémon work in game. This step may be skipped.

'''Remember that animations can only select bones. And if you change the bone names during or after this process, then you need to update your animations!'''
# Navigate to the <code>Animate</code> tab in the top-right corner of Blockbench
# Under the "ANIMATIONS" section, click the <code>Add Animation</code> button.
# Name your animation <code>animation.<pokemon>.<animation type></code>
#* There is a list of animation type examples below
#* A full list of animation types that the developers make can be found [[Tutorials/Creating_A_Model#Step_7:_Animate_your_Pokémon| here.]]
# Select a desired loop mode. This can be changed later.
# Click <code>Confirm</code>
# Animate your Pokémon until satisfied.
# Repeat the previous steps to create new animations.
# Save your animations as a group. Click on the top-most save icon.
# Name this animation JSON <code><pokemon>.animation.json</code>
# Place this animation JSON in your Pokémon's <code>animation</code> folder of your addon.
#* The folder path for this JSON should be like so: <code><your_addon>/assets/cobblemon/bedrock/pokemon/animations/<your_pokemon>/<pokemon>.animation.json</code>

Cobblemon has a limited selection of Pose types that animations can use in game. You should at least create some core animations like idles, walks, and faints. You can name your animations using the following naming scheme.

Beginner list of Poses and animations you should make for your Pokemon:
* "STAND" - <code>animation.<pokemon>.ground_idle</code>
* "WALK" - <code>animation.<pokemon>.ground_walk</code>
* "faint" - <code>animation.<pokemon>.faint</code>

The full list of usable pose types and the animations that work with them can be found on the full version of the [[Tutorials/Creating_A_Model#Step_7:_Animate_your_Pokémon| model guide.]]

==== Step 8: Export Bedrock Geometry ====
By now, you should already have your textures and animations saved somewhere. All that's left is to export your model file. Afterwards, everything you have made should be ready to use in resource packs!

# Click on File > Export > Export Bedrock Geometry
# Name this file <code><pokemon>.geo.json</code>
# Place this model JSON in your Pokémon's <code>model</code> folder of your addon.
#* The folder path for this JSON should be like so: <code><your_addon>/assets/cobblemon/bedrock/pokemon/models/<your_pokemon>/<pokemon>.geo.json </code>

This step is done last in case any edits needed to be made to the model.

Congratulations! You should now have a model, textures, and animations, which is most of the work for creating a custom Pokémon. Provided you followed this guide, your model should not be causing any issues when put in game.

=== Part 3: Create your Pokémon's Poser file ===
<code>Posers</code> are JSON files that create a set of animations for a Pokémon to use. The poser file 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!

You will be creating a poser file for the idle, walk, and faint animation you should have created if following this guide. '''Later in this guide''', you will have to come back and edit some of the <code>portrait</code> and <code>profile</code> values in the file so they look nice in the menus!

# Create a new text file and name it after your Pokémon. Include the file extension of <code>.json</code>
#* Example: <code>bulbasaur.json</code>
#* Make sure this new file name ends in .json and not any other file extension like .txt. You may need to search "how to show file extensions" for whatever operating system you have.
# Open this new JSON in your preferred text editor
# Copy and paste this entire poser example into the JSON
#* Hover over the underlined text to see more information.
{
"<abbr title="Tells the game which bone is the head. In this case, the head bone is simply named head.">head</abbr>": "<abbr title="The bone from your model that will act as the head for the look animation that plays when a Pokémon wants to look in certain directions. Can be any other appropriate bone and not all Pokémon need to do this!">head</abbr>",
"<abbr title="These refer to the portraits on the party menu on the left side of the screen. This will require some trial and error. I advise coming back to this after you’ve implemented your Pokémon. (Tip: you can refresh your resource pack with F3 + T for quick edits.)">portraitScale": 1</abbr>,
"<abbr title="These refer to the portraits on the party menu on the left side of the screen. This will require some trial and error. I advise coming back to this after you’ve implemented your Pokémon. (Tip: you can refresh your resource pack with F3 + T for quick edits.)">portraitTranslation": [ 0, 0.5, 0 ]</abbr>,
"<abbr title="These refer to the full body view of the Pokémon often seen in GUI, but most notably the summary UI. Like the previous code block, this section will require some trial and error, and you should come back to edit this later. (Tip: you can refresh your resource pack with F3 + T for quick edits.)">profileScale": 1</abbr>,
"<abbr title="These refer to the full body view of the Pokémon often seen in GUI, but most notably the summary UI. Like the previous code block, this section will require some trial and error, and you should come back to edit this later. (Tip: you can refresh your resource pack with F3 + T for quick edits.)">profileTranslation": [ 0, 0.4, 0 ]</abbr>,
"<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="The animation you are telling it to use when your Pokémon faints. If you have correctly named all your files and animations, this should be as simple as changing 'pokemon' to be your Pokémon’s name.">bedrock(pokemon, faint)</abbr>",
"<abbr title="Here we are defining a list of our poses.">poses</abbr>": {
"<abbr title="Here we are defining the name of the pose.">standing</abbr>": {
"<abbr title="Here we are again defining the name of the pose.">poseName</abbr>": "<abbr title="The name of your pose. In this case, its called standing">standing</abbr>",
"<abbr title="This is transition time between animations. You probably won't need to mess with this.>transformTicks": 10</abbr>,
"<abbr title="Here, we are telling the game when this animation will take place.">poseTypes</abbr>": [
"<abbr title="One of the pose types that will use the following animation. STAND - when stationary on the ground">STAND</abbr>",
"<abbr title="One of the pose types that will use the following animation. NONE - when not doing anything at all">NONE</abbr>",
"<abbr title="One of the pose types that will use the following animation. PORTRAIT - when in a portrait like on your party UI">PORTRAIT</abbr>",
"<abbr title="One of the pose types that will use the following animation. PROFILE - when in summary screens">PROFILE</abbr>"
],
"<abbr title="Here you will list which animations will play during these poses.">animations</abbr>": [
"<abbr title="Allows the Pokémon to move its head around to observe its surroundings. You can delete this if your Pokémon doesn't have a head bone, or you just don't want them looking around.">look</abbr>",
"<abbr title="The animation you are telling it to use when your Pokémon is standing, doing nothing, or in the mod's UI. If you have correctly named all your files and animations, this should be as simple as changing 'pokemon' to be your Pokémon’s name.">bedrock(pokemon, ground_idle)</abbr>"
]
},
"<abbr title="Here we are defining the name of the pose.">walking</abbr>": {
"<abbr title="Here we are again defining the name of the pose.">poseName</abbr>": "<abbr title="The name of your pose. In this case, its called walking">walking</abbr>",
"<abbr title="This is transition time between animations. You probably won't need to mess with this.>transformTicks": 10</abbr>,
"<abbr title="Here, we are telling the game when this animation will take place.">poseTypes</abbr>": [ "<abbr title="One of the pose types that will use the following animation. WALK - when traveling on the ground">WALK</abbr>" ],
"<abbr title="Here you will list which animations will play during these poses.">animations</abbr>": [ "<abbr title="The animation you are telling it to use when your Pokémon is walking on land. If you have correctly named all your files and animations, this should be as simple as changing 'pokemon' to be your Pokémon’s name.">bedrock(pokemon, ground_walk)</abbr>" ]
}
}
}
# <li value=4> In the section for <code>"faint"</code>, change "pokemon" in <code>"bedrock(pokemon, faint)"</code> to be your Pokémon's name.
#* Don't put the name in quotes.
# In the section for <code>"standing"</code>, change "pokemon" in <code>"bedrock(pokemon, ground_idle)"</code> to be your Pokémon's name.
#* Don't put the name in quotes.
# In the section for <code>"walking"</code>, change "pokemon" in <code>"bedrock(pokemon, ground_walk)"</code> to be your Pokémon's name.
#* Don't put the name in quotes.
# Save the file
# Place this new poser JSON into the <code>posers</code> folder of your addon.

You just created the poser file! When it's time to test your addon in game, it should use the animations you created earlier.

=== Part 4: Create your Pokémon's Resolver file ===
<code>Resolvers</code> are JSON files that assign a Pokémon its <code>model</code>, <code>textures</code>, and <code>animations</code>. The resolver files control all the things that allow a Pokémon to function visually!

You will be creating the resolver file for your Pokémon. At this part of the guide, you should already have files for model, texture, animation, and poser. Now they just need to be linked to your Pokémon using the resolver file.

# Create a new text file and name it <code>"0_<pokemon>_base.json"</code>
#* Example: <code>0_treecko_base.json</code>
#* Make sure this new file name ends in .json and not any other file extension like .txt. You may need to search "how to show file extensions" for whatever operating system you have.
# Open this new JSON in your preferred text editor
# Copy and paste this entire resolver example into the JSON
#*Hover over the underlined text to see more information.
{
"<abbr title="Here you are saying what Pokémon species will get the following assets">species</abbr>": "<abbr title="In this example, Treecko will get the following assets. You will want to change 'treecko' to be your Pokémon's name">cobblemon:treecko</abbr>",
"<abbr title="This is the load order of the forms in this file. Since this file contains the default variants for this Pokémon, load order should be 0. Addons may create more forms later, and they will use a higher number. This is what '0_' and '_base' in the file name represent. '0_' represents the load order, and '_base' represents that these are the default forms.">order": 0</abbr>,
"<abbr title="Here you will list all of your Pokémon's visual variations. This is how the shiny version uses the same model but with a different texture.">variations</abbr>": [
{
"<abbr title="'Aspects' are traits a Pokémon has. In this section, we are determining what the Pokémon will look like if it has no aspects. This can be considered the 'default' assets.">aspects": []</abbr>,
"<abbr title="Here you are telling the Pokémon what poser file to use.">poser</abbr>": "<abbr title="In this example, it will use the treecko poser. You will want to change 'treecko' to be your Pokémon's name">cobblemon:treecko</abbr>",
"<abbr title="Here you are telling the Pokémon what model file to use.">model</abbr>": "<abbr title="In this example, it will use the treecko model. You will want to change 'treecko' to be your Pokémon's name">cobblemon:treecko.geo</abbr>",
"<abbr title="Here you are telling the Pokémon what texture PNG to use.">texture</abbr>": "<abbr title="In this example, it will use 'treecko.png' from the 'treecko' folder. You will want to change both instances of 'treecko' to be your Pokémon's name">cobblemon:textures/pokemon/treecko/treecko.png</abbr>",
"<abbr title="This can be used to add additional textures on top of the main texture like with emissive textures or Arbok's chest patterns. This is unfortunately not covered in this guide.">layers": []</abbr>
},
{
"<abbr title="In this section, we are determining what the Pokémon will look like if it is 'shiny'.">aspects</abbr>": [
"<abbr title="Here you are specifying that any shiny Treecko will use the following texture. If you don't list a model or poser like this example, then it will use the 'default' ones that you created above.">shiny</abbr>"
],
"<abbr title="Here you are telling the shiny Pokémon what texture PNG to use. The texture will be applied to the default model in this example.">texture</abbr>": "<abbr title="In this example, it will use 'treecko_shiny.png' from the 'treecko' folder. You will want to change both instances of 'treecko' to be your Pokémon's name">cobblemon:textures/pokemon/treecko/treecko_shiny.png</abbr>"
}
]
}
# <li value=4> In the section for <code>"species"</code>, change "treecko" in <code>"cobblemon:treecko"</code> to be your Pokémon's name.
# In the section for <code>"poser"</code>, change "treecko" in <code>"cobblemon:treecko"</code> to be your Pokémon's name.
# In the section for <code>"model"</code>, change "treecko" in <code>"cobblemon:treecko.geo"</code> to be your Pokémon's name.
# In the section for <code>"textures"</code>, change '''both instances''' of "treecko" in <code>"cobblemon:textures/pokemon/treecko/treecko.png"</code> to be your Pokémon's name.
# Under the <code>"shiny"</code> aspect section for <code>"textures"</code>, change '''both instances''' of "treecko" in <code>"cobblemon:textures/pokemon/treecko/treecko_shiny.png"</code> to be your Pokémon's name.
#* Don't delete the "_shiny" part of the name.
#* You can remove the shiny variation if you didn't make any shiny textures.
# Save the file
# Place this new resolver JSON into your Pokémon's <code>resolvers</code> folder of your addon.

You just created your Pokémon's resolver file. When it's time to load your addon in game, it should be using the model, textures, and animations you created for it!

=== Part 5: Create your Pokémon's Species file ===
Now that we’ve got all the assets in place, we can now create the <code>species</code> file! The species file contains all the entity data your Pokémon needs to exist. This is done from the data folder within your pack. This section will be extensive, but it will explain some of the basic properties of the <code>species file</code>. For a more detailed description of the properties in the species file, you can refer to [https://wiki.cobblemon.com/index.php/Species its wiki page]

This part of the guide can be skipped if you are able to create your Pokémon's <code>species</code> file through this [https://tools.cobblemon.com/fakemon/ Fakemon Generator] made for Cobblemon! It will automatically create a zipped species JSON after you fill out some information for your Pokémon. The Fakemon Generator is very beginner friendly and can prevent you from making typos in the process of making a species file by hand.

==== Creating the Species JSON ====
This JSON will contain all the necessary data any Pokémon needs. This includes its name, type, abilities, stats, moves, etc.

# Create a new text file and name it after your Pokémon. Include the file extension of <code>.json</code>
#* Example: <code>bulbasaur.json</code>
#* Make sure this new file name ends in .json and not any other file extension like .txt. You may need to search "how to show file extensions" for whatever operating system you have.
# Open this new JSON in your preferred text editor
# Let's start by adding an opening and a closing curly bracket to the file like so:
#* In the following sections you will be adding information '''in between''' these brackets.
{

}

==== Basic Information ====
Let's add some basic information about your Pokémon.

# Copy and paste the following data '''inside the previously created curly brackets.'''
#*Hover over the underlined text to see more information.
"<abbr title="Whether or not this Pokémon is fully implemented. This determines whether it will show up in /spawnallpokemon or similar commands">implemented</abbr>": true,
"<abbr title="The name of the Pokémon species">name</abbr>": "<abbr title="In this example, the Pokémon will be called Tentaquil!">tentaquil</abbr>",
"<abbr title="Labels for this Pokémon. These labels can be used for spawning">labels</abbr>": [ "<abbr title="Here you are labeling your Pokémon as a 'custom' Pokémon.">custom</abbr>" ],
"<abbr title="Here we point to the Pokédex descriptions for this Pokémon.">pokedex</abbr>": [
"<abbr title="These are lang keys! We will need to define these later in a lang file, which is really easy. We'll cover this, but just replace 'tentaquil' with your own Pokémon's name for now.">cobblemon.species.tentaquil.desc1</abbr>",
"<abbr title="These are lang keys! We will need to define these later in a lang file, which is really easy. We'll cover this, but just replace 'tentaquil' with your own Pokémon's name for now.">cobblemon.species.tentaquil.desc2</abbr>"
],
"<abbr title="Height for the Pokédex. The value here is written in decimeters. To convert to meters, divide this value by 10.">height</abbr>": <abbr title="Tentaquil has a height of 11 decimeters, or 1.1 meters!">11</abbr>,
"<abbr title="Weight for the Pokédex and the amount of damage for moves based on weight. The value here is written in hectograms. To convert to kilograms, divide this value by 10.">weight</abbr>": <abbr title="Tentaquil has a weight of 300 hectograms, or 30 kilograms!">300</abbr>,
"<abbr title="Whether or not this pokemon can ride on the players shoulder.">shoulderMountable</abbr>": false,
# <li value=2>Change the 3 instances of "tentaquil" to your Pokémon's name
# Change the values of <code>"height"</code>, <code>"weight"</code>, and <code>"shoulderMountable"</code> if desired.


==== Stats ====
Now let's include the stats. You can refer to the stats of official Pokémon as guidelines if you plan on making the stats more practical and faithful to the official games. You can find the mod's official <code>species</code> files on the [https://gitlab.com/cable-mc/cobblemon/-/tree/main/common/src/main/resources/data/cobblemon/species Gitlab] which are organized by generation.

# Copy and paste the following data '''in a new line after the previous data.'''
#*Hover over the underlined text to see more information.
"<abbr title="The type assigned to your Pokémon.">primaryType</abbr>": "<abbr title="In this example, the Pokémon will be a poison type. You can change this if you like, but it must be an official type.">poison</abbr>",
"<abbr title="The second type assigned to your Pokémon. This line is optional.">secondaryType</abbr>": "<abbr title="In this example, the Pokémon will also be a water type. You can change this if you like, but it must be an official type.">water</abbr>",
"<abbr title="The base stats of your pokémon. Again, these are up to you.">baseStats</abbr>": {
"<abbr title="The base hp stat of your pokémon.">hp</abbr>": 125,
"<abbr title="The base attack stat of your pokémon.">attack</abbr>": 105,
"<abbr title="The base defense stat of your pokémon.">defence</abbr>": 95,
"<abbr title="The base special attack stat of your pokémon.">special_attack</abbr>": 120,
"<abbr title="The base special defense stat of your pokémon.">special_defence</abbr>": 85,
"<abbr title="The base speed stat of your pokémon.">speed</abbr>": 70
},
"<abbr title="The catch rate of your Pokémon. The higher the value, the easier it is to catch your Pokémon.">catchRate</abbr>": <abbr title="Catch rate values can start as low as 3 for legendary Pokémon and go as high as 255 for early game Pokémon like caterpie.">100</abbr>,
"<abbr title="What percentage of this pokémon are male.">maleRatio</abbr>": <abbr title="This would make the Pokémon have a 50% male ratio. You can set this value to 0 to make a female only species like Miltank. You can also set it to -1 to make genderless Pokémon like Ditto.">0.5</abbr>,
"<abbr title="How much experience is granted by this pokémon upon being defeated.">baseExperienceYield</abbr>": <abbr title="270 would let this Pokémon drop the same amount of exp as a legendary pokemon! Weak Pokémon have a value as low as 50. Blissey has the highest value at 635.">270</abbr>,
"<abbr title="How quickly this Pokémon will level up.">experienceGroup</abbr>": "<abbr title="It is recommended that you leave this alone for now. If you spell something wrong when trying to change it, your Pokémon will not level up at all.">fluctuating</abbr>",
"<abbr title="How long it will take this Pokémon's eggs to hatch.">eggCycles</abbr>": <abbr title="This value can be as low as 15 for quick hatching eggs or as high as 120 for slow hatching eggs like legendaries.">25</abbr>,
"<abbr title="The egg groups that this Pokémon can breed with.">eggGroups</abbr>": [
"<abbr title="It is recommended that you leave these alone unless you know what you're doing. If these values aren't valid, the game will crash.">water_1</abbr>",
"<abbr title="It is recommended that you leave these alone unless you know what you're doing. If these values aren't valid, the game will crash.">monster</abbr>"
],
"<abbr title="What this pokémon's friendship stat starts at when caught.">baseFriendship</abbr>": <abbr title="For most non-legendary Pokémon, this value is usually 50.">50</abbr>,
"<abbr title="How many EV's this pokémon gives upon being defeated.">evYield</abbr>": {
"<abbr title="The amount of hp EV's this Pokémon will drop.">hp</abbr>": 2,
"<abbr title="The amount of special attack EV's this Pokémon will drop.">special_attack</abbr>": 1
},
# <li value=2> Change any of these values if desired
#* It is recommended that you leave most of these values alone if you are unsure about your Pokémon's stats. They can always be changed later.


==== Moves and Abilities ====
Here you will include the abilities and move pool for your Pokémon.

# Copy and paste the following data '''in a new line after the previous data.'''
#*Hover over the underlined text to see more information.
"<abbr title="Here we're defining our list of moves. You can list as many as you like! If you'd like to include more moves, you cannot use spaces or underscores for moves that are named with multiple words like 'double slap.' You need to smoosh the words together! It would be written in this JSON as 'doubleslap'">moves</abbr>": [
"<abbr title="This would let disable be one of the 'egg moves' for this Pokémon">egg:disable</abbr>",
"<abbr title="This would let the Pokémon learn crushclaw at level 20">20:crushclaw</abbr>",
"<abbr title="This would allow the Pokémon to use a 'rest tm' when tm's get implemented">tm:rest</abbr>",
"<abbr title="This would allow the Pokémon to learn hone claws from a tutor when that gets implemented">tutor:honeclaws</abbr>"
],
"<abbr title="Here we define the list of abilities. You can have up to two abilities listed, and one hidden ability. The names of abilities must be one word just like with the moves.">abilities</abbr>": [
"<abbr title="This would make tough claws be the only default ability for this Pokémon.">toughclaws</abbr>",
"<abbr title="This would let serene grace be the hidden ability for this Pokémon. Hidden abilities are not implemented at this time.">h:serenegrace</abbr>"
],
# <li value=2> Change any of these values if desired
#* You probably should edit the moves and abilities for your Pokémon, but it can always be done later!


==== Entity Properties ====
Here you will list some properties of your Pokémon like its behavior, drops, and size.

# Copy and paste the following data '''in a new line after the previous data.'''
#*Hover over the underlined text to see more information.
"<abbr title="This refers to the scale of the Pokémon model.">baseScale</abbr>": <abbr title=" A scale of 1 means that the Pokémon will be the same size it was modeled at in Blockbench.">1</abbr>,
"<abbr title="These are the parameters that handle hit collision. There are only values for height and width since hitboxes are square prisms.">hitbox</abbr>": {
"<abbr title="The width of the hitbox. We will change this value later in the guide.">width</abbr>": 1,
"<abbr title="The height of the hitbox. We will change this value later in the guide.">height</abbr>": 1,
"<abbr title="This determines whether the hitbox is fixed in place or not. You usually always want this on false.">fixed</abbr>": false
},
"<abbr title="Here you will define what a Pokémon will drop when defeated.">drops</abbr>": {
"<abbr title="This indicates how many drop attempts there will be.">amount</abbr>": "<abbr title="In this instance, there will be 2 attempts to drop items from the entries listed below.">2</abbr>",
"<abbr title="This lists the potential items to drop.">entries</abbr>": [
{
"<abbr title="Here you will list the item id.">item</abbr>": "<abbr title="In this example, the Pokémon will attempt to drop slime balls! You can also include drops from other mods.">minecraft:slimeball</abbr>",
"<abbr title="The amount of items that will drop.">quantityRange</abbr>": "<abbr title="In this instance, it will drop 1-2 slime balls. Since there are 2 drop attempts, as specified from 'amount,' then there's a chance at getting 4 slime balls when defeating this pokemon!">1-2</abbr>",
"<abbr title="The chance for the item to drop.">percentage</abbr>": <abbr title="This means it will have a 66% chance to drop 1-2 slimeballs.">66</abbr>
}
]
},
"<abbr title="Here we will define the behavior of the Pokémon.">behaviour</abbr>": {
"<abbr title="Here you are listing behaviors regarding movement.">moving</abbr>": {
"<abbr title="This determines whether or not a Pokémon can look around. This really depends on your model.">canLook</abbr>": <abbr title="If your Pokémon doesn't have a proper head and neck, you might want to set this to false.">true</abbr>,
"<abbr title="Here you will list behaviors about flying.">fly</abbr>": {
"<abbr title="Whether or not a Pokémon can fly. If true, it will be assigned AI to fly.">canFly</abbr>": false
},
"<abbr title="Here you will list behaviors about swimming. This would include swimming in water and lava!">swim</abbr>": {
"<abbr title="Here you will determine how fast your Pokémon moves when swimming.">swimSpeed</abbr>": 0.2,
"<abbr title="Here you will determine if your Pokémon knows how to swim. If false, then the Pokémon will float to the surface instead of swimming around in water.">canSwimInWater</abbr>": true,
"<abbr title="Whether or not a Pokémon can breathe underwater. You want this set to true for most aquatic Pokémon.">canBreatheUnderwater</abbr>": true
}
}
}
# <li value=2> Change any of these values if desired
#* It is recommended to leave these alone for now.


==== Save the file! ====
That should be enough data for your custom Pokémon to be functional in game. Now you can save the file.

# Save the file
# Place this new species JSON into the <code>custom</code> folder of your addon.


=== Part 6: Creating the lang file ===
In this section we will walk you through on how to display the Pokémon's name in game. Let's begin by making a language file!

Minecraft will take whatever text is declared in this language file to show in game if a matching key is defined. The purpose of this is so that text such as names can be translated for different languages.

# Create a new text file and name it <code>en_us.json</code>
#* If US English is not your language, you can refer to the [https://minecraft.wiki/w/Language Minecraft Wiki page for language files] to get file name for your language.
#* Make sure this new file name ends in .json and not any other file extension like .txt. You may need to search "how to show file extensions" for whatever operating system you have.
# Open this new JSON in your preferred text editor
# Copy and paste this example data into the JSON:
#* Hover over the underlined text to see more information.
#* Remember that you want to change the string on the right side of the colon to whatever language you play with. The string on the left side of the colon must remain in English to be read properly by the mod.
{
"<abbr title="Here you will specify how your Pokémon's name will appear in English.">cobblemon.species.tentaquil.name</abbr>": "<abbr title="This will be the name that appears above the Pokémon's head in game. You are allowed to use capital letters, periods, and hyphens here.">Tentaquil</abbr>",
"<abbr title="Here you will give a short description of your Pokémon for the pokédex.">cobblemon.species.tentaquil.desc1</abbr>": "<abbr title="This will appear in the English pokédex when it gets implemented.">If its bold colors do not sufficiently ward off predators, it secretes toxins that smell strongly of copper.</abbr>",
"<abbr title="Here you will give a short description of your Pokémon for the pokédex.">cobblemon.species.tentaquil.desc2</abbr>": "<abbr title="This will appear in the English pokédex when it gets implemented.">There has only been one recorded sighting of this pokémon. Until recently, this was considered to be a joke.</abbr>"
}
# Swap out "tentaquil" for the name of your Pokémon
#* The value after <code>cobblemon.species.tentaquil.name</code> is what your Pokémon's name will look like over its head. So you can use capital letters, periods, and hyphens.
# Change the descriptions of the Pokémon if desired.
# Save the file
# Place this file in the <code>lang</code> folder of your addon.

The keys ending with <code>desc1</code> and <code>desc2</code> are the Pokémon's Pokédex entries. Although the Pokédex has not been implemented yet, try to keep the entries short and brief as there may eventually be a character limit.

You can add as many Pokémon names (along with their Pokédex entries) as you want to the same language file if you are planning to add more custom Pokémon to your pack.


=== Part 7: Testing your Pokemon in Game ===
You Pokemon should now have enough data to be functional in game! Let's try loading your addon in a new creative world.
# Launch Minecraft with the Cobblemon mod enabled.
# Click on "Singleplayer"
# Click on "Create New World"
# Name this new world whatever you like
# Set it to Creative and allow cheats!
# Click on "Data Packs"
# Click on "Open Pack Folder"
# Copy your addon folder and paste it into this datapack folder.
#* Your addon should appear in the list of available datapacks
#* If it appears as red, you can still select it and load it without issues if you have been following this guide.
# Select your addon from the list of available datapacks and click done
#* It should warn you that the datapack is outdated, but you can ignore this warning!
# Click on "Create New World"
# After the world has loaded, spawn your Pokémon with this command: <code>/pokespawn <your_pokemon></code>
# Your Pokémon should have a strange looking name and should have spawned as the substitute doll, which is a green dinosaur-like doll.
#* This is because the resource pack hasn't been activated yet. We will do that next.
#* If a Pokémon can at least spawn as the substitute doll, that means all of it's data is valid.
# Open your options menu.
# Click on "Resource Packs"
# Click on "Open Pack Folder"
# Copy your addon folder and paste it into this resource pack folder.
#* Your addon should appear in the list of available resource packs
# Select your addon from the list of available resource packs and click done.
#* If you get a warning that the resource pack is outdated, you can ignore this warning!
# After the game refreshes the resourcepacks, you should be able to see the model you created!
# Ensure that your Pokémon's model, animations, and name are working properly.
# Do not close Minecraft yet. In the following sections of this guide, we will be editing the addon files while the game is loaded.

You may notice that your Pokémon does not appear properly in the Party menus and HUD. Its appearance in the GUI is controlled by the <code>poser</code> file. We will fix it in the next couple of sections.

Your Pokémon may also appear bigger or smaller than you intended. This can be corrected in its <code>species</code> file. We will fix it in the next section.

=== Part 8: Adjusting the Scale of your Pokémon in game ===
We will be adjusting the size of your Pokémon in game. This will be done by editing the <code>species</code> file you created earlier.

Remember that datapack folder that you copy and pasted your addon folder into? It was a temporary folder used for world creation. This means that your addon is now in a different folder. We want to edit the in game files so we can see the changes without having to restart the game! This section of the guide will show you how to access that folder from in game.

# Have Minecraft open in the main menu
#* You'll always want Minecraft open in this section of the guide.
# Open your options menu.
# Click on "Resource Packs"
#* Although we are looking for your addon in the datapacks folder, this is a simple way to navigate to the datapack folder.
# Click on "Open Pack Folder"
# From this new folder window, go back one folder or press <code>ALT+[UP ARROW]</code>.
# Click on the <code>saves</code> folder.
# Click on the folder named after the Creative World you made earlier in this guide.
# Click on the <code>datapacks</code> folder.
# You should see your addon folder now!
# Open your addon folder and navigate to the <code>species</code> JSON of your Pokémon.
# Open the JSON in your preferred text editor.
# Look for the following data in this file:
"<abbr title="This refers to the scale of the Pokémon model.">baseScale</abbr>": <abbr title=" A scale of 1 means that the Pokémon will be the same size it was modeled at in Blockbench.">1</abbr>,
"<abbr title="These are the parameters that handle hit collision. There are only values for height and width since hitboxes are square prisms.">hitbox</abbr>": {
"<abbr title="The width of the hitbox. We will change this value now.">width</abbr>": 1,
"<abbr title="The height of the hitbox. We will change this value now.">height</abbr>": 1,
"<abbr title="This determines whether the hitbox is fixed in place or not. You usually always want this on false.">fixed</abbr>": false
},
# <li value=13> Let's start by changing the <code>baseScale</code> value first! This controls the size of the Pokémon model.
#* By default, this value should be 1.
#* You can use decimals to get a precise size for your Pokémon.
# Change the value for <code>baseScale</code>
#* If you want your Pokémon to be bigger, make the value higher than 1
#* If you want your Pokémon to be smaller, make the value lower than 1, but higher than 0.
# Save the file.
# Load your Creative Single Player world from the main menu.
#* You always have to load the world from the main menu to see changes to <code>data</code> files.
#* The command <code>/reload</code> does not work with Cobblemon datapacks.
# Examine your Pokémon and decide if it still needs to be adjusted.
# Repeat steps 10-17 until your Pokémon's in game size is just right!
# Now that your Pokémon's size is correct, we can adjust its <code>hitbox</code> values! This controls the Pokémon's hitbox and the size of its shadow.
#* By default, this value should be 1.
#* You can use decimals to get a precise size for your Pokémon.
# Open your addon folder and navigate to the <code>species</code> JSON of your Pokémon.
# Open the JSON in your preferred text editor.
# Look for the following data in this file:
"<abbr title="These are the parameters that handle hit collision. There are only values for height and width since hitboxes are square prisms.">hitbox</abbr>": {
"<abbr title="The width of the hitbox. We will change this value now.">width</abbr>": 1,
"<abbr title="The height of the hitbox. We will change this value now.">height</abbr>": 1,
"<abbr title="This determines whether the hitbox is fixed in place or not. You usually always want this on false.">fixed</abbr>": false
},
# <li value=23> Change the values for <code>width</code> and <code>height</code>
#* If you want your Pokémon's hitbox to be bigger, make the values higher than 1
#* If you want your Pokémon's hitbox to be smaller, make the values lower than 1, but higher than 0.
# Save the file.
# Load your Creative Single Player world from the main menu.
#* You always have to load the world from the main menu to see changes to <code>data</code> files.
# Press <code>F3+B</code> to show hitboxes.
# Examine your Pokémon and decide if it still needs to be adjusted.
#* Most of the time, you want the red line around the same height as the eye(s) of your Pokémon.
#* That red line on the hitbox indicates when the entity will start suffocating. If the hitbox somehow has a block above this red line, then the entity will start suffocating.
# Repeat steps 20-27 until your Pokémon's in game hitbox is just right!
# Once your Pokémon's size and hitbox are just right, go back to the main menu of Minecraft and proceed to the next part of the guide.


=== Part 9: Adjusting your Pokémon's poser file in game ===
In this part of the guide, we will be editing the <code>poser</code> file so your Pokémon can look nice in the GUIs! This time we will be editing files in the resource pack folder! This means you can press <code>F3+T</code> to reload the resource pack in game rather than loading from the main menu like we did for the species file.

# Have Minecraft open in the main menu
#* You'll always want Minecraft open in this section of the guide.
# Open your options menu.
# Click on "Resource Packs"
# Click on "Open Pack Folder"
# From this new folder window, you should see your addon folder.
# Open your addon folder and navigate to the <code>poser</code> JSON of your Pokémon.
# Open the JSON in your preferred text editor.
# Look for the following data in this file:
"<abbr title="These refer to the portraits on the party menu on the left side of the screen. This will require some trial and error. I advise coming back to this after you’ve implemented your Pokémon. (Tip: you can refresh your resource pack with F3 + T for quick edits.)">portraitScale": 1</abbr>,
"<abbr title="These refer to the portraits on the party menu on the left side of the screen. This will require some trial and error. I advise coming back to this after you’ve implemented your Pokémon. (Tip: you can refresh your resource pack with F3 + T for quick edits.)">portraitTranslation": [ 0, 0.5, 0 ]</abbr>,
"<abbr title="These refer to the full body view of the Pokémon often seen in GUI, but most notably the summary UI. Like the previous code block, this section will require some trial and error, and you should come back to edit this later. (Tip: you can refresh your resource pack with F3 + T for quick edits.)">profileScale": 1</abbr>,
"<abbr title="These refer to the full body view of the Pokémon often seen in GUI, but most notably the summary UI. Like the previous code block, this section will require some trial and error, and you should come back to edit this later. (Tip: you can refresh your resource pack with F3 + T for quick edits.)">profileTranslation": [ 0, 0.4, 0 ]</abbr>,
# <li value=9> Let's start by editing <code>portraitScale</code> and <code>portraitTranslation</code>. These values control how your Pokémon looks on the right side of your screen.
#* <code>portraitScale</code> makes your Pokémon bigger or smaller in the GUI. It can be treated like a "zoom" value for the camera that renders your Pokémon in this GUI. The higher the value, the more it will zoom into your Pokémon.
#* <code>portraitTranslation</code> has a set of 3 values in brackets. These 3 values can be treated like the xyz coordinates for the camera that renders your Pokémon in the GUI. These values can use decimals and negative numbers!
#* This part requires a lot of trial and error. Sometimes if you change a value too drastically, it will stop appearing on the GUI. It is recommended to change the values in increments of 0.3 to get your bearings on how these values work.
# Change the values for <code>portraitScale</code> and <code>portraitTranslation</code>
# Save the file
# Go back to Minecraft and press <code>F3+T</code> to refresh all resource packs
# After loading, examine your Pokémon in the party GUI on the left side of your screen.
#* Generally, you want this GUI to show your Pokémon's entire face
# Repeat steps 6-13 until your Pokémon looks just right!
# Next we will edit the values for <code>profileScale</code> and <code>profileTranslation</code>. These values control how your Pokémon looks in the Party GUI when you press M.
#* <code>profileScale</code> makes your Pokémon bigger or smaller in the GUI.
#* <code>portraitTranslation</code> controls the position of the camera rendering your Pokémon in this menu. These values can use decimals and negative numbers!
#* This part also requires a lot of trial and error. It is recommended to change the values in increments of 0.3 again.
# Open your addon folder and navigate to the <code>poser</code> JSON of your Pokémon.
# Open the JSON in your preferred text editor.
# Look for the following data in this file:
"<abbr title="These refer to the portraits on the party menu on the left side of the screen. This will require some trial and error. I advise coming back to this after you’ve implemented your Pokémon. (Tip: you can refresh your resource pack with F3 + T for quick edits.)">portraitScale": 1</abbr>,
"<abbr title="These refer to the portraits on the party menu on the left side of the screen. This will require some trial and error. I advise coming back to this after you’ve implemented your Pokémon. (Tip: you can refresh your resource pack with F3 + T for quick edits.)">portraitTranslation": [ 0, 0.5, 0 ]</abbr>,
"<abbr title="These refer to the full body view of the Pokémon often seen in GUI, but most notably the summary UI. Like the previous code block, this section will require some trial and error, and you should come back to edit this later. (Tip: you can refresh your resource pack with F3 + T for quick edits.)">profileScale": 1</abbr>,
"<abbr title="These refer to the full body view of the Pokémon often seen in GUI, but most notably the summary UI. Like the previous code block, this section will require some trial and error, and you should come back to edit this later. (Tip: you can refresh your resource pack with F3 + T for quick edits.)">profileTranslation": [ 0, 0.4, 0 ]</abbr>,
# <li value=19> Change the values for <code>profileScale</code> and <code>profileTranslation</code>
# Save the file
# Go back to Minecraft and press <code>F3+T</code> to refresh all resource packs
# After loading, press M and examine your Pokémon in the party GUI.
#* Generally, you want this GUI to show your Pokémon's entire body.
#* You mainly want your Pokémon's body to stay within the camera borders on the left side of the menu. This will mostly prevent your Pokémon from overlapping on the right side of the menu.
# Repeat steps 16-22 until your Pokémon looks just right!
# Once your Pokémon looks just right in the party menus, go back to the main menu of Minecraft and proceed to the next part of the guide.

At this point in the guide, your Pokémon should be fully functional in game. The last thing it needs is a way for it to spawn naturally in the game!


=== Part 10: Create your Pokémon's Spawn File ===
Once you create the spawn file for your Pokémon, it is considered complete! We will be using an example spawn file as a template to spawn your Pokémon. You can edit it to your liking with different [https://gitlab.com/cable-mc/cobblemon/-/wikis/Spawner/Spawn-Condition spawn conditions.] A list of biome tags you can use can be found [https://docs.google.com/document/d/1iB0EJSc2r6mRJXIo1n3XpHbZ5udwJVnrh2pXdhTyH8c/edit here].

# Create a new text file and name it <code><pokemon>.json</code>
#* Example: <code>bulbasaur.json</code>
#* Make sure this new file name ends in .json and not any other file extension like .txt. You may need to search "how to show file extensions" for whatever operating system you have.
# Open this new JSON in your preferred text editor
# Copy and paste this example data into the JSON:
#* Hover over the underlined text to see more information.
{
"<abbr title="This determines whether this spawn data is enabled">enabled": true</abbr>,
"<abbr title="These are lists that say whether the spawn data requires specific mods to be present. Namely, this is mostly for pokémon that spawn in biomes introduced by other mods.">neededInstalledMods": []</abbr>,
"<abbr title="These are lists that say whether the spawn data requires specific mods to be present. Namely, this is mostly for pokémon that spawn in biomes introduced by other mods.">neededUninstalledMods": []</abbr>,
"<abbr title="Here we are declaring where it will spawn.">spawns</abbr>": [
{
"<abbr title="Spawn locations require unique ID's. Calling them something like yourpokemon-1, yourpokemon-2 and so on is acceptable.">id": "tentaquil-1"</abbr>,
"<abbr title="Which pokémon are we trying to spawn here?">pokemon": "tentaquil</abbr>",
"<abbr title="Presets are a collection of potential block candidates to spawn on, this way you don't need to clarify a ton of blocks every time you make a spawn file.">presets</abbr>": [ "<abbr title="natural is the most common preset. You can pick others like underground, freshwater, redstone or more.">natural</abbr>" ],
"<abbr title="We are spawning a pokémon here, so no need to change this.">type": "pokemon</abbr>",
"<abbr title="What sort of surface is this spawning on? We will keep it on 'grounded' for this example.">context": "grounded</abbr>",
"<abbr title="How rare is this pokémon?">bucket": "uncommon</abbr>",
"<abbr title="This is the minimum and maximum level this pokémon can spawn at.">level": "18-60</abbr>",
"<abbr title="This number determines how likely it is to spawn considering its rarity.">weight": 10.0</abbr>,
"<abbr title="Additional spawn conditions are listed in this section.">condition</abbr>": {
"<abbr title="Whether or not this pokémon should be able to see the sky when it spawns.">canSeeSky</abbr>": true,
"<abbr title="Here we list the biomes we want the pokémon to spawn in.">biomes</abbr>": [ "<abbr title="The Cobblemon tag for forest biomes. Allows Tentaquil to spawn in any biome tagged as a forest.">#cobblemon:is_forest</abbr>" ]
}
}
]
}
# <li value=4> Replace the 2 instances of "tentaquil" with the name of your Pokémon
# Edit any of the other values if desired.
#* With the current template, your Pokémon will be an uncommon spawn in the forest.
# Save the file
# Place this new file in the <code>spawn_pool_world</code> folder of your addon.
#* Ensure that you place it in the addon folder that is in the datapack folder!
# Load your Creative Single Player world from the main menu.
#* You always have to load the world from the main menu to see changes to <code>data</code> files.
# Check if your Pokémon spawns where you assigned it to. You can use <code>/checkspawn <rarity></code> when in the assigned biome.
#* 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.
# Ensure that your Pokémon at least appears in the <code>checkspawn</code> list after meeting its conditions.
#* If you made your Pokémon rare or ultra-rare, then it may take hours before you even see it spawn naturally.
# If your Pokémon appears in the checkspawn list, or if you see it spawn naturally, then you can consider this guide completed!

Congratulations! You are now a Cobblemon modder. Hopefully your Pokémon will have no issues if you've been following along. If you have any issues with your addon, help can be found in the Cobblemon Discord server.

== Sharing your Pokémon Addon ==
Before you share your addon with others or upload it to a server, it is best to package your addon into a <code>.zip</code>. This will allow you to share the single <code>.zip</code> file instead of all the files individually.

If you have been following this guide, you may have realized that some files that got updated while testing in game are now separated. We need to combine the <code>data</code> and <code>assets</code> folders again.

# Create a new folder
# Name this new folder. This will be the final product name for your addon.
# Navigate to your addon folder inside the <code>datapacks</code> folder
# Open your addon folder
# Copy the <code>data</code> folder and the <code>pack.mcmeta</code> file
#* If you have a <code>pack.png</code>, copy that file too
# Paste them inside of your new addon folder
# Navigate to your addon folder inside the <code>resourcepacks</code> folder
# Open your addon folder
# Copy the <code>assets</code> folder
# Paste inside of your new addon folder
# Your up to date files should now be reunited in the new addon folder. Its structure and contents should look like the following folder tree:
==== Folder Structure ====
<div class="treeview">
*''(new addon folder name)''
** '''pack.mcmeta'''
** '''pack.png'''
**assets
***cobblemon
****bedrock
*****pokemon
******animations
*******<pokemon name>
********'''<pokemon>.animation.json'''
******models
*******<pokemon name>
********'''<pokemon>.geo.json'''
******posers
*******'''<pokemon>.json'''
******resolvers
*******<pokemon>
********'''0_<pokemon>_base.json'''
****lang
*****'''en_us.json'''
****textures
*****pokemon
******<pokemon>
*******'''<pokemon>.png'''
*******'''<pokemon>_shiny.png'''
**data
***cobblemon
****spawn_pool_world
*****'''<pokemon>.json'''
****species
*****custom
******'''<pokemon>.json'''
</div>
# <li value=12> Ensure you followed steps 1-11 correctly.
#* If you followed along correctly, then you copied the correct and updated files so it should work properly when shared.
# Open your new addon folder
# Select all of the following items together: <code>data</code>, <code>assets</code>, <code>pack.mcmeta</code>, <code>pack.png</code>(optional)
# Compress the files with your preferred zip file software.
#* If you are on Windows, you can compress them with the following method: Right click the selected items > send to > Compressed (zipped) folder
# Ensure that they are in a <code>.zip</code> file
#* Minecraft wont read <code>.rar</code> files
# Ensure that the <code>pack.mcmeta</code> file is one of the first things you see when you open your zipped addon.
#* Minecraft will only read 1 folder deep for the <code>pack.mcmeta</code>

Your addon should now be ready to share! Remember that this new <code>zip</code> file will still need to have a copy placed in both the <code>datapacks</code> and <code>resourcepacks</code> folders of those who will receive it. If you want to share the files on a server, then the server needs a copy in its datapack folder of the world. And every player will need a copy in their resourcepack folder!

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

Spawn Rules

2024-06-28T05:47:47Z

Hiroku: it's not a future feature anymore weee

Spawn Rules are a datapack feature that allow addons to modify spawning behaviour in a global way. Spawn Rules contain a set of rule components, and there are several component types to choose from. Spawn rules are loaded from the `spawn_rules` folder.

"weight":
The weight rule component allows you to selectively modify the weight of spawn details as they are used. For example, you can make the weight of a Pikachu spawn in an area that is well lit to be multiplied by 20.
{
"type": "weight",
"spawnSelector": "v.spawn.pokemon.species == 'pikachu'",
"contextSelector": "v.context.light > 8",
"weight": "v.weight * 20"

"filter":
The filter rule component allows you to block or allow spawns. This is like adding a global rule against spawning. For example, you can make Pikachu unable to spawn in an area that is not well lit.
{
"type": "filter",
"spawnSelector": "v.spawn.pokemon.species == 'pikachu'",
"contextSelector": "v.context.light < 8",
"allow": "false"

"location":
The location rule component allows you to block or allow locations to be considered for any spawning. This is more aggressive than the filter rule component because it cancels the spawning process much sooner. This is best used to create no-spawn zones.
{
"type": "location",
"allow": "v.y > 100 || v.world.is_of('minecraft:overworld')"

Spawn Detail Properties
Every spawn detail that is made available under the name "spawn" has properties that can be checked in your spawn rule components.
* "weight": The base weight of the spawn.
* "percentage": The base percentage spawn chance (usually null)
* "id": The unique ID of the spawn.
* "bucket": The bucket of the spawn.
* "width": The specified width required for spawning.
* "height": The specified height required for spawning.
* "context": The context type of the spawn.
* "labels": A list of label strings.

Pokémon Spawn Detail Properties
Pokémon spawn details have more properties than the general spawn detail.
* "pokemon": The specified Pokémon as a variable. This is what was specified in the file.

Pokémon Properties
Pokémon Properties referenced from MoLang expressions have many properties.
* "species": The species of the Pokémon, such as cobblemon:bulbasaur, if set.
* "level": The level of the Pokémon, if set.
* "shiny": True or false depending on if the Pokémon is explicitly marked as either. It can be null.
* "gender": The gender name, if set.
* "friendship": The friendship value of the Pokémon, if set.

Location properties
When using the "location" rule component, many variables are supplied.
* "x": The x coordinate being checked.
* "y": The y coordinate being checked.
* "z": The z coordinate being checked.
* "context": The context type being checked, such as "grounded" or "seafloor".
* "world": The world it's in. This contains two functions, is_of and is_in for checking the ID or if it fits a specific tag, respectively. For example, v.world.is_in('yourmod:your_world_tag').
* "dimension_type": The dimension it's in. This contains the same two functions as the "world" property.

Context properties
When using a context selector, a context will be added as a variable and it contains many variables.
* "light": The light level, from 0 to 15.
* "x": The x coordinate.
* "y": The y coordinate.
* "z": The z coordinate.
* "moon_phase": The phase of the moon, between 0 and 7 inclusive.
* "world": The world of the context, in the same format in the "location" properties.
* "biome": The biome of the context. This, like world and dimension type, contains two functions: is_of and is_in.

Example (weird) spawn rule:
{
"displayName": "Pikachu Daylight Multiplier - (Example file)",
"enabled": "true",
"components": [
{
"type": "weight",
"spawnSelector": "v.spawn.pokemon.species == 'pikachu'",
"contextSelector": "v.context.light > 8",
"weight": "v.weight * 20"
},
{
"type": "filter",
"spawnSelector": "v.spawn.pokemon.species == 'pikachu'",
"contextSelector": "v.context.light < 8",
"allow": "false"
},
{
"type": "location",
"allow": "v.y > 100 || v.world.is_of('minecraft:overworld')"
}
]

Dialogues

2024-06-28T04:38:09Z

Hiroku: Created Dialogues page

Dialogues are a feature that can be used from API or from datapacks to play conversations in a GUI. They display entities, view pages of text, and handle various types of input.

A dialogue that has been registered through a datapack can be opened using the /opendialogue command.

Every case of a MoLang expression can be either a single text property or can be an array of text to support running multiple expressions to produce a result.

[[File:Dialogue_Intro.png|400px|center]]

=Dialogue=

A Dialogue JSON file consists of the following main elements:

- <code>escapeAction</code>: A string or array that defines the action to be taken when the dialogue is escaped. This can be a MoLang expression or a sequence of MoLang expressions.

- <code>speakers</code>: An object that defines the speakers in the dialogue. Each speaker is represented by a key-value pair, where the key is the speaker's identifier and the value is an object that describes what the speaker looks like and their name.

- <code>pages</code>: An array of objects, each representing a page in the dialogue.

==Speakers==

Each speaker is represented by an object with the following properties:

- <code>name</code>: A string or object that defines the speaker's name. This is usually just text. If it's an object, it must have a <code>type</code> property set to <code>"expression"</code> and an <code>expression</code> property that contains a MoLang expression. You would use an expression if you wanted the name to be dynamic.

- <code>face</code>: An object or MoLang expression that defines the speaker's face. This will be rendered in a frame of the GUI. For objects, it must have a <code>type</code> property set to the type of face. The only object type support currently is "standard". The others are done using MoLang expressions rather than an object.

===Faces===
The speaker faces can be defined in multiple ways. If it is an object it is going to be a "standard" face type.

===="standard"====
The standard face type is for when the face displayed is not connected to a specific entity in the world but does follow Cobblemon's format of identifier and aspect list. The object must have the following properties:

- <code>modelType</code>: One of 'pokemon', 'npc'

- <code>identifier</code>: The identifier of the Pokémon or NPC, such as <code>cobblemon:bulbasaur</code>.

- <code>aspects</code>: An array of aspects that will be applied to the model.

For example:

"face": {
"type": "artificial",
"modelType": "pokemon",
"identifier": "cobblemon:pikachu",
"aspects": [
"shiny"
]
}

====player====
By using <code>q.player.face()</code> you can make the player's model render for this face.

For example:

"face": "q.player.face();"

====npc====
By using <code>q.npc.face()</code> you can show a direct reference to the NPC you're having the dialogue with, if this was dialogue started with an NPC entity.

For example:

"face": "q.npc.face();"

==Pages==

Each page is represented by an object with the following properties:

- <code>id</code>: A string that uniquely identifies the page. This is needed for instances where you might want to jump to a specific page. Page numbers could be used, but you should use page IDs.

- <code>speaker</code>: A string that specifies the speaker's identifier. This depends upon the speaker by this identifier existing in the speakers list.

- <code>lines</code>: An array of strings or objects, each representing a line of text. If it's an object, it must have a <code>type</code> property set to <code>"expression"</code> and an <code>expression</code> property that contains a MoLang expression that evaluates to a string. You would use an expression if you want to include variables to make dynamic text.

- <code>input</code>: An object or string that defines the input prompt. If it's an object, it must have a <code>type</code> property set to <code>"option"</code>, <code>"text"</code>, <code>"auto-continue"</code>, or <code>"none"</code>, and other properties depending on the type. By default, the input value will be <code>none</code>.

- <code>escapeAction</code>: A string or array that defines the action to be taken when the page is escaped. This can be a MoLang expression or a sequence of MoLang expressions.

==Input Types==

The <code>input</code> property in a page object can have different structures depending on the <code>type</code>.

For all inputs that specify an <code>action</code> property which is set to a MoLang expression, you can access the time it took for them to make that input using <code>v.seconds_taken_to_input</code>.

==="option"===
The input is a set of options. The object must have an <code>options</code> property that is an array of objects, each representing an option. It can also specify whether the options should be displayed vertically or horizontally by whether or not the <code>vertical</code> property is true or false.

Each option object can have the following properties:

- <code>value</code>: The unique value of the dialogue option. This is not displayed to the player and is instead used to reference this option from scripts.
- <code>text</code>The display text for the option. This can be a simple string or can be an object
- <code>action</code>: The MoLang expression to run when the user chooses the option.
- <code>isVisible</code>: A MoLang expression which must return either true or false. If false, the option will not be visible for the player. Defaults to true.
- <code>isSelectable</code>: A MoLang expression which must return either true or false. If false, the option will be greyed out (but only if it is visible). Defaults to true.

[[File:Dialogue_Options.png|600px|center]]

==="text"===
The input is a text field. The <code>action</code> property is a MoLang expression that will run when the player hits enter with text typed in. As specified earlier, you can check the text that they input using <code>v.selected_option</code> inside of the MoLang expression.

[[File:Dialogue_Input.png|600px|center]]

==="auto-continue"===
The dialogue will automatically progress after some period of time. There are several optional properties for this.

- <code>delay</code>: The delay in seconds until it progresses. By default this is 5 seconds.

- <code>allowSkip</code>: Whether the user is able to skip the delay by clicking. By default this is true. If false, the player will be forced to wait for the delay.

- <code>showTimer</code>: Whether a bar will be displayed to indicate how much more time the player has until it auto-continues. Defaults to false.

- <code>action</code>: A MoLang expression that runs when either the player clicks (only when <code>allowSkip</code> is true) or the delay finishes. By default this moves to the next page.

==="none"===
There is no input except that it waits until the user clicks to continue. The object can have an <code>action</code> property that defines the MoLang expression to run when the player clicks. By default, it moves to the next page.

===Timeouts===
All input types except for <code>"none"</code> and <code>"autocontinue"</code> can have a 'timeout' object which allows you to apply time constraints to the player viewing the page.

The timeout object can have 3 properties:

- <code>duration</code>: The time, in seconds, that the player will have to complete the input. By default this is 10 seconds.

- <code>showTimer</code>: Whether or not a bar will be shown to show the player how much time they have left. By default this is true.

- <code>action</code>: A MoLang expression to run if they do not enter the input in time. By default this will close the dialogue.

[[File:Dialogue_Timer.png|600px|center]]

=Example=
The following example is built-in to the mod, labelled "example".

{
"escapeAction": "q.dialogue.set_page('quitter')",
"speakers": {
"pikachu": {
"name": "The Voice of Hiro",
"face": {
"type": "artificial",
"modelType": "pokemon",
"identifier": "cobblemon:pikachu",
"aspects": [
"shiny"
]
}
},
"player": {
"face": "q.player.face();",
"name": {
"type": "expression",
"expression": "q.player.username"
}
}
},
"pages": [
{
"id": "player-chat",
"speaker": "player",
"lines": [
{
"type": "expression",
"expression": "'Hello, I\\'m ' + q.player.username + '!'"
}
]
},
{
"speaker": "pikachu",
"lines": [
{
"type": "expression",
"expression": "'Nice to meet you, ' + q.player.username + '! Welcome to the world of dialogues!'"
}
]
},
{
"id": "intro",
"speaker": "pikachu",
"lines": [ "Do you want to learn more?"],
"input": {
"type": "option",
"vertical": false,
"options": [
{
"text": "Yes",
"value": "yes",
"action": [
"v.player_response = 'That sounds great!';",
"v.next_page = 'page1';",
"q.dialogue.set_page('player-surrogate');"
]
},
{
"text": "No",
"value": "no",
"action": [
"v.player_response = 'No, I really don\\'t care.';",
"v.next_page = 'quitter';",
"q.dialogue.set_page('player-surrogate');"
]
},
{
"text": "Sword!",
"value": "sword",
"isVisible": "q.player.main_held_item.is_of('minecraft:iron_sword')",
"isSelectable": "q.player.data.scared_npc != true;",
"action": [
"v.player_response = 'How about you die! Muahahaha!';",
"v.next_page = 'sword';",
"q.dialogue.set_page('player-surrogate');"
]
},
{
"text": "Sword again!",
"value": "sword2",
"isVisible": "q.player.main_held_item.is_of('minecraft:iron_sword')",
"isSelectable": "q.player.data.scared_npc == true;",
"action": [
"v.player_response = 'How about you die... again! Muahahaha!';",
"v.next_page = 'sword-again';",
"q.dialogue.set_page('player-surrogate');"
]
}
]
}
},
{
"id": "player-surrogate",
"speaker": "player",
"lines": [
{
"type": "expression",
"expression": "v.player_response;"
}
],
"input": "q.dialogue.set_page(v.next_page);"
},
{
"id": "page1",
"speaker": "pikachu",
"lines": [
"Well you see, this is a dialogue.",
"You can have multiple pages, and each page can have multiple lines."
]
},
{
"id": "page2",
"speaker": "pikachu",
"lines": ["On an unrelated note, did you know that I'm deeply afraid of iron swords? Anyway, cya!"],
"input": {
"type": "auto-continue",
"delay": 5,
"allowSkip": true,
"action": "q.dialogue.close();"
}
},
{
"id": "quitter",
"speaker": "pikachu",
"lines": ["Fine. Be that way."],
"input": "q.dialogue.close();",
"escapeAction": "q.dialogue.close();"
},
{
"id": "sword",
"speaker": "pikachu",
"lines": ["Oh god no, please don't hurt me!"],
"escapeAction": "q.dialogue.input('');",
"input": [
"t.data = q.player.data();",
"t.data.scared_npc = true;",
"q.player.save_data();",
"q.dialogue.close();"
]
},
{
"id": "sword-again",
"speaker": "pikachu",
"lines": ["I'm ready for you this time. YOU will die today!"],
"escapeAction": "0",
"input": {
"type": "option",
"vertical": true,
"timeout": {
"delay": 6,
"action": "q.dialogue.input('stand');"
},
"options": [
{
"text": "Parry his attack.",
"value": "parry",
"action": [
"v.reaction = 'parry';",
"q.dialogue.set_page('sword-again-decided');"
]
},
{
"text": "Stand perfectly still.",
"value": "stand",
"action": [
"v.reaction = 'stand still';",
"q.dialogue.set_page('sword-again-decided');"
]
},
{
"text": "Drop your sword.",
"value": "drop",
"action": [
"v.reaction = 'drop your sword';",
"q.dialogue.set_page('sword-again-decided');"
]
}
]
}
},
{
"id": "sword-again-decided",
"lines": [
{
"type": "expression",
"expression": "v.reaction == 'parry' ? 'You parry his attack and kill him.' : (v.reaction == 'stand still' ? 'He kills you.' : 'You drop your sword and he kills you.')"
}
],
"input": {
"type": "auto-continue",
"delay": 3,
"allowSkip": false,
"showTimer": false,
"action": "q.dialogue.set_page('sword-again-reaction');"
}
},
{
"id": "sword-again-reaction",
"speaker": "pikachu",
"lines": [
{
"type": "expression",
"expression": "'Nah, I\\'m just kidding. Interesting that you chose to ' + v.reaction + ' though.'"
}
]
},
{
"id": "name-question",
"speaker": "pikachu",
"lines": [ "Here's a puzzle though... What is my name? Lowercase only."],
"input": {
"type": "text",
"timeout": {
"delay": 10,
"action": "q.dialogue.set_page('too-slow');"
},
"action": [
"q.dialogue.set_page('name-speak');",
"t.data = q.player.data();"
]
}
},
{
"id": "name-speak",
"speaker": "player",
"lines": [
{
"type": "expression",
"expression": "'Your name is ' + v.selected_option + ', right?'"
}
],
"input": "q.dialogue.set_page('name-guess');"
},
{
"id": "name-guess",
"speaker": "pikachu",
"lines": [
{
"type": "expression",
"expression": "v.selected_option == 'hiroku' ? 'Correct! You know things that you shouldn\\'t...' : ('Wrong! I\\'m not \"' + v.selected_option + '\". Whoever that is.')"
}
],
"input": {
"type": "auto-continue",
"delay": 5,
"allowSkip": true,
"action": "q.dialogue.set_page('farewell');"
}
},
{
"id": "farewell",
"speaker": "pikachu",
"lines": ["Anyway, I'm done with this dialogue. Bye!"],
"input": "q.dialogue.close();"
},
{
"id": "too-slow",
"speaker": "pikachu",
"lines": ["Don't know? Sad. Well I don't know your name either, so I guess we're even."],
"input": "q.dialogue.close()"
}
]
}

File:Dialogue Input.png

2024-06-28T04:33:56Z

Hiroku:

File:Dialogue Timer.png

2024-06-28T04:33:37Z

Hiroku:

File:Dialogue Options.png

2024-06-28T04:31:31Z

Hiroku:

File:Dialogue Intro.png

2024-06-28T04:30:02Z

Hiroku: