CobbleBoss

CobbleBoss Boss User Guide

1. Data Pack Structure

CobbleBoss data packs use the cobbleboss namespace.

Normal Boss files are placed in:

data/cobbleboss/bosses/

Paid multiplayer Boss team files are placed in:

data/cobbleboss/boss_teams/

Main structure:

pack.mcmeta
data/cobbleboss/bosses/
data/cobbleboss/boss_teams/

Recommended file naming:

• Use lowercase English letters.
• Use underscores instead of spaces.
• Use clear names related to the Boss.
• Keep each Boss file independent.

2. What A Boss JSON Controls

A Boss JSON controls:

• Which Pokemon the Boss is
• Boss display name
• Boss glow color
• Natural spawn rules
• Rewards after victory
• Punishments after defeat
• Moves
• EVs
• Custom battle stats
• Nature
• Ability
• Form
• Held items
• Battle mode
• Actions per turn
• Shield settings
• Phase skills
• Boss size

3. Recommended Reading Order

For beginners, understand these parts first:

• Boss identity
• Spawn rules
• Rewards and punishments
• Battle configuration
• Visual settings
• Advanced raid mechanics

Most important fields:

• unique_id
• species_id
• random_configs

Recommended fields:

• display_name
• glow
• moves
• battle_mode
• actions_per_turn
• scale

Optional fields:

• spawn_rule
• reward_rule
• punish_rule
• effort_values
• custom_battle_stats
• phase_skills
• held_items
• nature
• ability
• form
• shield_layers
• shield_recover_per_turn
• shield_weaken_turns

4. Top-Level Boss Fields

unique_id

Purpose:

The unique internal ID of the Boss.

Recommendation:

Required.

Notes:

• Must be unique.
• Commands use this ID.
• Do not reuse the same ID in multiple Boss files.
• Recommended format is lowercase English letters with underscores.

display_name

Purpose:

The name shown to players in game.

Recommendation:

Recommended.

Notes:

• Supports Minecraft color codes.
• Useful for making Boss names more obvious.
• If omitted, the species name may be used instead.

species_id

Purpose:

Defines which Pokemon species the Boss is.

Recommendation:

Required.

Notes:

• Usually uses the cobblemon namespace.
• This determines the actual Pokemon created by the Boss system.

glow

Purpose:

Controls the Boss glowing outline color after it spawns.

Position:

Top-level field.

Recommendation:

Optional.

How it works:

• If set, the Boss receives a glowing outline.
• If missing or empty, the Boss does not glow.
• Uses Minecraft color names.

Available colors:

• black
• dark_blue
• dark_green
• dark_aqua
• dark_red
• dark_purple
• gold
• gray
• dark_gray
• blue
• green
• aqua
• red
• light_purple
• yellow
• white

Notes:

• Invalid colors can cause the Boss file to fail loading.
• This only controls entity glow, not announcement color.

spawn_rule

Purpose:

Controls natural spawning rules.

Recommendation:

Optional.

Important:

For natural spawning, a Boss usually needs:

• spawn_locations
• spawn_times
• spawn_biomes or spawn_structures
• spawn_weight

Notes:

• A Boss without usable spawn rules may not participate in natural spawning.
• spawn_biomes and spawn_structures are checked as biome-or-structure matching.

reward_rule

Purpose:

Controls rewards after players defeat the Boss.

Recommendation:

Optional.

Can contain:

• Direct item rewards
• Direct command rewards
• Reward pools that roll once and randomly choose one entry
• Count
• Chance
• Weight
• Rolls

punish_rule

Purpose:

Controls punishments after players lose to the Boss.

Recommendation:

Optional.

Can contain:

• Level reduction
• EV reduction
• IV reduction
• Command punishment
• Chance

random_configs

Purpose:

Defines one or more possible battle configurations for this Boss.

Recommendation:

Required.

How it works:

• A Boss can have multiple random configurations.
• One configuration is selected when the Boss is created.
• Different configurations can have different moves, stats, held items, battle modes, shield settings, and size.

5. Spawn Rule Fields

spawn_locations

Purpose:

Restricts where the Boss can spawn.

Available values:

• land
• water_surface
• underwater
• cave
• sky
• lava

Notes:

• Natural spawning needs a valid spawn location type.
• Use values that match the Boss theme.

spawn_times

Purpose:

Restricts the time period when the Boss can spawn.

Available values:

• all_day
• early_morning
• morning
• noon
• afternoon
• dusk
• night
• midnight

Time mapping:

• early_morning: 0 - 2999 ticks
• morning: 3000 - 5999 ticks
• noon: 6000 - 11999 ticks
• afternoon: 12000 - 14999 ticks
• dusk: 15000 - 17999 ticks
• night: 18000 - 20999 ticks
• midnight: 21000 - 23999 ticks
• all_day: no time restriction

Notes:

• Minecraft has 24000 ticks per day.
• Multiple time values can be used.
• all_day means the Boss can spawn at any time.

spawn_biomes

Purpose:

Restricts which biomes the Boss can spawn in.

How it works:

• A normal biome ID limits spawning to that biome.
• A biome tag starting with # allows all biomes in that tag.

Notes:

• Use biome IDs for precise control.
• Use biome tags for broader biome groups.
• This can be combined with spawn_structures.

spawn_structures

Purpose:

Allows Boss spawning when the player is inside specific structures.

How it works:

• Uses structure IDs.
• If the player is inside a matching structure, the Boss can match this rule.
• This is checked together with biome rules as biome-or-structure matching.

Notes:

• This is for structure IDs, not structure tags.
• Useful for dungeon, temple, ruin, stronghold, or custom structure Bosses.

spawn_weight

Purpose:

Controls natural spawn selection weight.

How it works:

• When multiple Bosses are valid, higher weight means higher selection chance.
• It is not a direct percentage.

Notes: