Skip to content

Max_Items.json

Unariginal edited this page Sep 4, 2026 · 1 revision

Max_Items.json

Defines the four Dynamax-related bag items: Dynamax Candy, Max Honey, Max Mushrooms, and Max Soup. All four share the same tiny JSON schema, but each has completely different, hard-coded use logic — this file only controls whether an item is consumed on use and its tooltip lore. Located at GenesisForms/items/bag_items/max_items.json.

📄 Full default file
{
  "dynamax_candy": {
    "consumable": true,
    "lore": [
      "<gray>A candy that is packed with energy.",
      "<gray>If consumed, it raises the Dynamax Level of a Pokémon by one.",
      "<gray>A higher level means higher HP when Dynamaxed."
    ]
  },
  "max_honey": {
    "consumable": true,
    "lore": [
      "<gray>Honey that Dynamax Vespiquen produces. Adding this honey to Max Soup makes the taste very smooth.",
      "<gray>It also has the same effect as a Max Revive."
    ]
  },
  "max_mushrooms": {
    "consumable": true,
    "lore": [
      "<gray>Mushrooms that have the power of changing Dynamax forms.",
      "<gray>They boost all stats of a Pokémon during battle."
    ]
  },
  "max_soup": {
    "consumable": true,
    "lore": [
      "<gray>The soup can be fed to any Pokémon that has a Gigantamax form, which either adds or removes the Gigantamax Factor."
    ]
  }
}

Top Level

Field Type Description
dynamax_candy object Raises a Pokémon's Dynamax Level by 1.
max_honey object Fully revives a fainted Pokémon, in or out of battle.
max_mushrooms object An in-battle-only bag item that boosts the active Pokémon's stats.
max_soup object Toggles the Gigantamax Factor on an eligible Pokémon.

Note

These four keys are fixed — the mod looks each one up by exact ID (dynamax_candy, max_honey, max_mushrooms, max_soup). You can edit consumable/lore for each, or remove an entry to stop that item from being registered at all, but you can't add arbitrary new IDs here the way you can in Tera_Shards.json — there's no per-item logic to attach to a new key.

Item Object

Field Type Default Description
consumable boolean true Whether one copy of the item is removed from the stack (respecting creative mode) each time it's successfully used. If false, the item is reusable indefinitely.
lore string array Lore lines shown on the item tooltip. Supports MiniMessage color tags (e.g. <gray>).

Per-Item Behavior

Dynamax Candy

Right-clicking opens Cobblemon's party-select prompt to pick a target Pokémon. If the Pokémon's current Dynamax Level is below Cobblemon's configured maximum (Cobblemon.config.maxDynamaxLevel), its Dynamax Level is incremented by exactly 1 and its dynamax_level species feature is synced to match. There's no way to raise it by more than 1 per candy, and it cannot exceed Cobblemon's own max.

Max Honey

Fully heals/revives a Pokémon, matching its lore ("the same effect as a Max Revive"):

  • In battle: opens a battle party-select prompt limited to fainted Pokémon on the player's side, then forces a Showdown revive 1 action for the chosen Pokémon.
  • Out of battle: opens a party-select prompt limited to fainted Pokémon, then sets the chosen Pokémon's current HP to its max HP (routed through Cobblemon's PokemonHealedEvent so other listeners can react/adjust the amount).

Max Honey does not target healthy Pokémon — the selection prompt only offers Pokémon with 0 HP.

Max Mushrooms

Warning

Max Mushrooms only work in an active Cobblemon battle, on your own currently-active Pokémon. Using it outside of battle, or with no active Pokémon, does nothing.

This is a Cobblemon BagItem whose Showdown input is the literal string "max_mushroom". When used, it forces a bag-item action for the active battle Pokémon with that input and lets Cobblemon/Showdown's battle engine resolve the actual effect.

Max Soup

Right-clicking opens Cobblemon's party-select prompt. Max Soup only accepts a Pokémon whose species has at least one Gigantamax form (checked via the species' form labels containing "gmax"). On a valid target it toggles (not just adds) the Pokémon's Gigantamax Factor — using it a second time on the same Pokémon removes the factor again. The player is sent a "Gigantamax Factor applied" or "Gigantamax Factor removed" message depending on the resulting state.

Max Soup additionally requires both dynamax_settings.enable_dynamax and dynamax_settings.enable_gigantamax to be true in Config.json; if either is false, it fails silently.

Global Toggles

  • dynamax_settings.enable_dynamax in Config.json — gates Dynamax Candy and Max Soup.
  • dynamax_settings.enable_gigantamax in Config.json — additionally gates Max Soup.
  • general_settings.disabled_items in Config.json — listing an item's ID here (e.g. "max_honey") disables that item entirely.

Note

Max Mushrooms is not gated by dynamax_settings in code — only by general_settings.disabled_items. This is worth confirming still holds if you're relying on enable_dynamax to lock down the whole Dynamax feature set on your server.

See Also

  • Config.json — the dynamax_settings block (enable_dynamax, enable_gigantamax).
  • Accessories.json — the dynamax_band accessory, which is what actually lets a Pokémon Dynamax in battle.
  • Commands — admin commands for giving items directly.

Config Files

─ items/accessories/Accessories.json

─ items/bag_items/Max_Items.json

─ items/bag_items/Tera_Shards.json

─ items/held_items/Held_Battle_Items.json

─ items/held_items/Held_Form_Items.json

─ items/held_items/Z_Crystals.json

─ items/key_items/Fusion_Items.json

─ items/key_items/Key_Form_Items.json

─ items/key_items/Possession_Items.json

Clone this wiki locally