# CobbleBoss Boss User Guide<\/p>\n
## 1. Data Pack Structure<\/p>\n
CobbleBoss data packs use the `cobbleboss` namespace.<\/p>\n
Normal Boss files are placed in:<\/p>\n
“`text
\ndata\/cobbleboss\/bosses\/
\n“`<\/p>\n
Paid multiplayer Boss team files are placed in:<\/p>\n
“`text
\ndata\/cobbleboss\/boss_teams\/
\n“`<\/p>\n
Main structure:<\/p>\n
“`text
\npack.mcmeta
\ndata\/cobbleboss\/bosses\/
\ndata\/cobbleboss\/boss_teams\/
\n“`<\/p>\n
Recommended file naming:<\/p>\n
– Use lowercase English letters.
\n– Use underscores instead of spaces.
\n– Use clear names related to the Boss.
\n– Keep each Boss file independent.<\/p>\n
## 2. What A Boss JSON Controls<\/p>\n
A Boss JSON controls:<\/p>\n
– Which Pokemon the Boss is
\n– Boss display name
\n– Boss glow color
\n– Natural spawn rules
\n– Rewards after victory
\n– Punishments after defeat
\n– Moves
\n– EVs
\n– Custom battle stats
\n– Nature
\n– Ability
\n– Form
\n– Held items
\n– Battle mode
\n– Actions per turn
\n– Shield settings
\n– Phase skills
\n– Boss size<\/p>\n
## 3. Recommended Reading Order<\/p>\n
For beginners, understand these parts first:<\/p>\n
– Boss identity
\n– Spawn rules
\n– Rewards and punishments
\n– Battle configuration
\n– Visual settings
\n– Advanced raid mechanics<\/p>\n
Most important fields:<\/p>\n
– `unique_id`
\n– `species_id`
\n– `random_configs`<\/p>\n
Recommended fields:<\/p>\n
– `display_name`
\n– `glow`
\n– `moves`
\n– `battle_mode`
\n– `actions_per_turn`
\n– `scale`<\/p>\n
Optional fields:<\/p>\n
– `spawn_rule`
\n– `reward_rule`
\n– `punish_rule`
\n– `effort_values`
\n– `custom_battle_stats`
\n– `phase_skills`
\n– `held_items`
\n– `nature`
\n– `ability`
\n– `form`
\n– `shield_layers`
\n– `shield_recover_per_turn`
\n– `shield_weaken_turns`<\/p>\n
## 4. Top-Level Boss Fields<\/p>\n
### `unique_id`<\/p>\n
Purpose:<\/p>\n
The unique internal ID of the Boss.<\/p>\n
Recommendation:<\/p>\n
Required.<\/p>\n
Notes:<\/p>\n
– Must be unique.
\n– Commands use this ID.
\n– Do not reuse the same ID in multiple Boss files.
\n– Recommended format is lowercase English letters with underscores.<\/p>\n
### `display_name`<\/p>\n
Purpose:<\/p>\n
The name shown to players in game.<\/p>\n
Recommendation:<\/p>\n
Recommended.<\/p>\n
Notes:<\/p>\n
– Supports Minecraft color codes.
\n– Useful for making Boss names more obvious.
\n– If omitted, the species name may be used instead.<\/p>\n
### `species_id`<\/p>\n
Purpose:<\/p>\n
Defines which Pokemon species the Boss is.<\/p>\n
Recommendation:<\/p>\n
Required.<\/p>\n
Notes:<\/p>\n
– Usually uses the `cobblemon` namespace.
\n– This determines the actual Pokemon created by the Boss system.<\/p>\n
### `glow`<\/p>\n
Purpose:<\/p>\n
Controls the Boss glowing outline color after it spawns.<\/p>\n
Position:<\/p>\n
Top-level field.<\/p>\n
Recommendation:<\/p>\n
Optional.<\/p>\n
How it works:<\/p>\n
– If set, the Boss receives a glowing outline.
\n– If missing or empty, the Boss does not glow.
\n– Uses Minecraft color names.<\/p>\n
Available colors:<\/p>\n
– `black`
\n– `dark_blue`
\n– `dark_green`
\n– `dark_aqua`
\n– `dark_red`
\n– `dark_purple`
\n– `gold`
\n– `gray`
\n– `dark_gray`
\n– `blue`
\n– `green`
\n– `aqua`
\n– `red`
\n– `light_purple`
\n– `yellow`
\n– `white`<\/p>\n
Notes:<\/p>\n
– Invalid colors can cause the Boss file to fail loading.
\n– This only controls entity glow, not announcement color.<\/p>\n
### `spawn_rule`<\/p>\n
Purpose:<\/p>\n
Controls natural spawning rules.<\/p>\n
Recommendation:<\/p>\n
Optional.<\/p>\n
Important:<\/p>\n
For natural spawning, a Boss usually needs:<\/p>\n
– `spawn_locations`
\n– `spawn_times`
\n– `spawn_biomes` or `spawn_structures`
\n– `spawn_weight`<\/p>\n
Notes:<\/p>\n
– A Boss without usable spawn rules may not participate in natural spawning.
\n– `spawn_biomes` and `spawn_structures` are checked as biome-or-structure matching.<\/p>\n
### `reward_rule`<\/p>\n
Purpose:<\/p>\n
Controls rewards after players defeat the Boss.<\/p>\n
Recommendation:<\/p>\n
Optional.<\/p>\n
Can contain:<\/p>\n
– Direct item rewards
\n– Direct command rewards
\n– Reward pools that roll once and randomly choose one entry
\n– Count
\n– Chance
\n– Weight
\n– Rolls<\/p>\n
### `punish_rule`<\/p>\n
Purpose:<\/p>\n
Controls punishments after players lose to the Boss.<\/p>\n
Recommendation:<\/p>\n
Optional.<\/p>\n
Can contain:<\/p>\n
– Level reduction
\n– EV reduction
\n– IV reduction
\n– Command punishment
\n– Chance<\/p>\n
### `random_configs`<\/p>\n
Purpose:<\/p>\n
Defines one or more possible battle configurations for this Boss.<\/p>\n
Recommendation:<\/p>\n
Required.<\/p>\n
How it works:<\/p>\n
– A Boss can have multiple random configurations.
\n– One configuration is selected when the Boss is created.
\n– Different configurations can have different moves, stats, held items, battle modes, shield settings, and size.<\/p>\n
## 5. Spawn Rule Fields<\/p>\n
### `spawn_locations`<\/p>\n
Purpose:<\/p>\n
Restricts where the Boss can spawn.<\/p>\n
Available values:<\/p>\n
– `land`
\n– `water_surface`
\n– `underwater`
\n– `cave`
\n– `sky`
\n– `lava`<\/p>\n
Notes:<\/p>\n
– Natural spawning needs a valid spawn location type.
\n– Use values that match the Boss theme.<\/p>\n
### `spawn_times`<\/p>\n
Purpose:<\/p>\n
Restricts the time period when the Boss can spawn.<\/p>\n
Available values:<\/p>\n
– `all_day`
\n– `early_morning`
\n– `morning`
\n– `noon`
\n– `afternoon`
\n– `dusk`
\n– `night`
\n– `midnight`<\/p>\n
Time mapping:<\/p>\n
– `early_morning`: 0 – 2999 ticks
\n– `morning`: 3000 – 5999 ticks
\n– `noon`: 6000 – 11999 ticks
\n– `afternoon`: 12000 – 14999 ticks
\n– `dusk`: 15000 – 17999 ticks
\n– `night`: 18000 – 20999 ticks
\n– `midnight`: 21000 – 23999 ticks
\n– `all_day`: no time restriction<\/p>\n
Notes:<\/p>\n
– Minecraft has 24000 ticks per day.
\n– Multiple time values can be used.
\n– `all_day` means the Boss can spawn at any time.<\/p>\n
### `spawn_biomes`<\/p>\n
Purpose:<\/p>\n
Restricts which biomes the Boss can spawn in.<\/p>\n
How it works:<\/p>\n
– A normal biome ID limits spawning to that biome.
\n– A biome tag starting with `#` allows all biomes in that tag.<\/p>\n
Notes:<\/p>\n
– Use biome IDs for precise control.
\n– Use biome tags for broader biome groups.
\n– This can be combined with `spawn_structures`.<\/p>\n
### `spawn_structures`<\/p>\n
Purpose:<\/p>\n
Allows Boss spawning when the player is inside specific structures.<\/p>\n
How it works:<\/p>\n
– Uses structure IDs.
\n– If the player is inside a matching structure, the Boss can match this rule.
\n– This is checked together with biome rules as biome-or-structure matching.<\/p>\n
Notes:<\/p>\n
– This is for structure IDs, not structure tags.
\n– Useful for dungeon, temple, ruin, stronghold, or custom structure Bosses.<\/p>\n
### `spawn_weight`<\/p>\n
Purpose:<\/p>\n
Controls natural spawn selection weight.<\/p>\n
How it works:<\/p>\n
– When multiple Bosses are valid, higher weight means higher selection chance.
\n– It is not a direct percentage.<\/p>\n
Notes:<\/p>\n
– Use positive values.
\n– If all valid weights are 0, selection may fall back to random valid Boss selection.<\/p>\n
## 6. Reward Rule Fields<\/p>\n
### `reward_items`<\/p>\n
Purpose:<\/p>\n
List of direct reward entries.<\/p>\n
How it works:<\/p>\n
– Each entry rolls independently.
\n– If three entries each have `chance: 0.1`, each one has its own 10% chance.
\n– The player can receive multiple entries from the same `reward_items` list.<\/p>\n
Each reward entry can contain:<\/p>\n
– `item_id`
\n– `count`
\n– `command`
\n– `chance`
\n– `weight`<\/p>\n
`weight` is only used when the same reward entry is placed inside `reward_pools.entries`. It is harmless but unnecessary in direct `reward_items`.<\/p>\n
### `reward_pools`<\/p>\n
Purpose:<\/p>\n
List of reward pools.<\/p>\n
How it works:<\/p>\n
– Each pool rolls once using its `chance`.
\n– If the pool succeeds, the mod randomly chooses one entry from `entries`.
\n– If `rolls` is greater than 1, the pool chooses that many entries.
\n– Selection is weighted by each entry’s `weight`.
\n– Selection is with replacement, so the same entry can be selected more than once when `rolls` is greater than 1.<\/p>\n
Each reward pool can contain:<\/p>\n
– `chance`
\n– `rolls`
\n– `entries`<\/p>\n
Each pool entry can contain:<\/p>\n
– `item_id`
\n– `count`
\n– `command`
\n– `chance`
\n– `weight`<\/p>\n
Important:<\/p>\n
– Pool-level `chance` controls whether the pool gives anything.
\n– Entry-level `chance` is parsed for compatibility, but pool entries are selected by random weight after the pool succeeds.
\n– If you want separate independent chances, use `reward_items`.
\n– If you want “10% chance for one item from this list”, use `reward_pools`.<\/p>\n
### `item_id`<\/p>\n
Purpose:<\/p>\n
The item given to the player.<\/p>\n
Notes:<\/p>\n
– Use a valid item ID.
\n– Can be Minecraft, Cobblemon, or another mod item.<\/p>\n
### `count`<\/p>\n
Purpose:<\/p>\n
The number of items given.<\/p>\n
Notes:<\/p>\n
– If omitted, it usually acts as 1.
\n– Count is only used for item rewards.
\n– Must be greater than 0.<\/p>\n
### `command`<\/p>\n
Purpose:<\/p>\n
Executes a command as a reward.<\/p>\n
Notes:<\/p>\n
– Useful for giving Pokemon, money, points, titles, permissions, or other server rewards.
\n– Supports the `{player}` placeholder.
\n– Write the command without a leading slash.<\/p>\n
### `chance`<\/p>\n
Purpose:<\/p>\n
Controls probability.<\/p>\n
For direct `reward_items`:<\/p>\n
– If `chance` is greater than 0, that custom chance is used.
\n– If `chance` is missing or 0, the reward uses the default drop rate from `boss-reward.toml`.<\/p>\n
For `reward_pools`:<\/p>\n
– If pool `chance` is greater than 0, that custom chance is used.
\n– If pool `chance` is missing or 0, the pool uses the default drop rate from `boss-reward.toml`.<\/p>\n
Meaning:<\/p>\n
– `1` means 100%.
\n– `0.5` means 50%.
\n– `0.1` means 10%.<\/p>\n
### `rolls`<\/p>\n
Purpose:<\/p>\n
Controls how many entries are selected from a successful reward pool.<\/p>\n
Notes:<\/p>\n
– If omitted, it defaults to 1.
\n– Must be greater than 0.
\n– The same entry can be selected more than once.<\/p>\n
### `weight`<\/p>\n
Purpose:<\/p>\n
Controls selection chance inside a reward pool.<\/p>\n
How it works:<\/p>\n
– Higher weight means higher chance inside that pool.
\n– Default weight is 1.
\n– Weight is not a direct percentage.<\/p>\n
Example:<\/p>\n
– Entry A weight 1
\n– Entry B weight 3
\n– Entry B is three times as likely as Entry A inside that pool.<\/p>\n
### Reward Examples<\/p>\n
Independent rewards:<\/p>\n
“`json
\n“reward_rule”: {
\n “reward_items”: [
\n {
\n “item_id”: “cobblemon:poke_ball”,
\n “count”: 3,
\n “chance”: 0.1
\n },
\n {
\n “item_id”: “cobblemon:great_ball”,
\n “count”: 2,
\n “chance”: 0.1
\n },
\n {
\n “item_id”: “cobblemon:ultra_ball”,
\n “count”: 1,
\n “chance”: 0.1
\n }
\n ]
\n}
\n“`<\/p>\n
One reward from a pool:<\/p>\n
“`json
\n“reward_rule”: {
\n “reward_pools”: [
\n {
\n “chance”: 0.1,
\n “rolls”: 1,
\n “entries”: [
\n {
\n “item_id”: “cobblemon:poke_ball”,
\n “count”: 3
\n },
\n {
\n “item_id”: “cobblemon:great_ball”,
\n “count”: 2
\n },
\n {
\n “item_id”: “cobblemon:ultra_ball”,
\n “count”: 1
\n }
\n ]
\n }
\n ]
\n}
\n“`<\/p>\n
Weighted pool:<\/p>\n
“`json
\n“reward_rule”: {
\n “reward_pools”: [
\n {
\n “chance”: 0.25,
\n “rolls”: 1,
\n “entries”: [
\n {
\n “item_id”: “minecraft:diamond”,
\n “count”: 1,
\n “weight”: 1
\n },
\n {
\n “item_id”: “minecraft:emerald”,
\n “count”: 3,
\n “weight”: 3
\n },
\n {
\n “command”: “give {player} minecraft:gold_ingot 8”,
\n “weight”: 5
\n }
\n ]
\n }
\n ]
\n}
\n“`<\/p>\n
Direct rewards and pools can be used together:<\/p>\n
“`json
\n“reward_rule”: {
\n “reward_items”: [
\n {
\n “item_id”: “minecraft:gold_ingot”,
\n “count”: 2,
\n “chance”: 1.0
\n }
\n ],
\n “reward_pools”: [
\n {
\n “chance”: 0.1,
\n “entries”: [
\n {
\n “item_id”: “cobblemon:poke_ball”,
\n “count”: 3
\n },
\n {
\n “item_id”: “cobblemon:great_ball”,
\n “count”: 2
\n },
\n {
\n “item_id”: “cobblemon:ultra_ball”,
\n “count”: 1
\n }
\n ]
\n }
\n ]
\n}
\n“`<\/p>\n
## 7. Punish Rule Fields<\/p>\n
### `punish_items`<\/p>\n
Purpose:<\/p>\n
List of punishment entries.<\/p>\n
Each punishment entry can contain:<\/p>\n
– `level`
\n– `evs`
\n– `ivs`
\n– `command`
\n– `chance`<\/p>\n
### `level`<\/p>\n
Purpose:<\/p>\n
Reduces Pokemon level after losing.<\/p>\n
Notes:<\/p>\n
– Level will not be reduced below 1.
\n– Use carefully because level loss can feel severe.<\/p>\n
### `evs`<\/p>\n
Purpose:<\/p>\n
Reduces effort values.<\/p>\n
Available stats:<\/p>\n
– `hp`
\n– `attack`
\n– `defense`
\n– `special_attack`
\n– `special_defense`
\n– `speed`<\/p>\n
Notes:<\/p>\n
– Only fill stats you want to reduce.
\n– Missing stats are ignored.<\/p>\n
### `ivs`<\/p>\n
Purpose:<\/p>\n
Reduces individual values.<\/p>\n
Available stats:<\/p>\n
– `hp`
\n– `attack`
\n– `defense`
\n– `special_attack`
\n– `special_defense`
\n– `speed`<\/p>\n
Notes:<\/p>\n
– IV punishment is very severe.
\n– Recommended only for high-risk Boss designs.<\/p>\n
### `command`<\/p>\n
Purpose:<\/p>\n
Executes a command as punishment.<\/p>\n
Notes:<\/p>\n
– Useful for applying effects, taking currency, teleporting, broadcasting, or triggering server systems.
\n– Supports the `{player}` placeholder.
\n– Write the command without a leading slash.<\/p>\n
### `chance`<\/p>\n
Purpose:<\/p>\n
Controls the probability of this punishment.<\/p>\n
Important:<\/p>\n
– If `chance` is greater than 0, that custom chance is used.
\n– If `chance` is missing or 0, the punishment uses the default penalty chance from `boss-penalty.toml`.<\/p>\n
## 8. Random Config Fields<\/p>\n
### `shiny`<\/p>\n
Purpose:<\/p>\n
Controls whether the Boss is shiny.<\/p>\n
Notes:<\/p>\n
– `true` makes the Boss shiny.
\n– `false` makes it normal.
\n– If omitted, it usually defaults to false.<\/p>\n
### `effort_values`<\/p>\n
Purpose:<\/p>\n
Sets the Boss EV spread.<\/p>\n
Available stats:<\/p>\n
– `hp`
\n– `attack`
\n– `defense`
\n– `special_attack`
\n– `special_defense`
\n– `speed`<\/p>\n
Rules:<\/p>\n
– Each stat should be between 0 and 252.
\n– Total EVs should not exceed 510.<\/p>\n
### `custom_battle_stats`<\/p>\n
Purpose:<\/p>\n
Overrides or limits Boss battle stats.<\/p>\n
Available stats:<\/p>\n
– `hp`
\n– `attack`
\n– `defense`
\n– `special_attack`
\n– `special_defense`
\n– `speed`<\/p>\n
Each stat rule uses:<\/p>\n
– `value`
\n– `mode`<\/p>\n
### `value`<\/p>\n
Purpose:<\/p>\n
The target stat value.<\/p>\n
Notes:<\/p>\n
– Usually a positive number.
\n– Useful for raid-style Bosses.<\/p>\n
### `mode`<\/p>\n
Purpose:<\/p>\n
Controls how the stat value is applied.<\/p>\n
Available values:<\/p>\n
– `exact`
\n– `minimum`
\n– `maximum`<\/p>\n
Meanings:<\/p>\n
– `exact`: use this value directly.
\n– `minimum`: stat will be at least this value.
\n– `maximum`: stat will be at most this value.<\/p>\n
### `moves`<\/p>\n
Purpose:<\/p>\n
Sets the Boss moves.<\/p>\n
Notes:<\/p>\n
– Usually use up to 4 moves.
\n– Move names should match Cobblemon move IDs.
\n– Invalid move names can cause Boss creation failure.<\/p>\n
### `nature`<\/p>\n
Purpose:<\/p>\n
Sets the Boss nature.<\/p>\n
Notes:<\/p>\n
– If omitted, the Boss uses a default nature.
\n– Use Cobblemon nature names.<\/p>\n
### `ability`<\/p>\n
Purpose:<\/p>\n
Sets the Boss ability.<\/p>\n
Notes:<\/p>\n
– If omitted, default ability behavior is used.
\n– Invalid ability names can cause Boss creation failure.<\/p>\n
### `form`<\/p>\n
Purpose:<\/p>\n
Sets the Boss form.<\/p>\n
Notes:<\/p>\n
– Use this for special forms.
\n– Leave empty if not needed.
\n– The value should match Cobblemon form or aspect behavior.<\/p>\n
### `held_items`<\/p>\n
Purpose:<\/p>\n
Sets possible held items for the Boss.<\/p>\n
Notes:<\/p>\n
– Can contain one or more item IDs.
\n– If multiple items are configured, the Boss may randomly use one.
\n– Invalid item IDs can cause Boss creation failure.<\/p>\n
### `battle_mode`<\/p>\n
Purpose:<\/p>\n
Sets the Boss battle mode and battle layout.<\/p>\n
Available values:<\/p>\n
– `1v1` \/ `one_vs_one`
\n– `2v1` \/ `two_vs_one`
\n– `3v1` \/ `three_vs_one`
\n– `4v1` \/ `four_vs_one`
\n– `5v1` \/ `five_vs_one`
\n– `6v1` \/ `six_vs_one`<\/p>\n
Important:<\/p>\n
`battle_mode` does not limit `actions_per_turn`.<\/p>\n
Notes:<\/p>\n
– This field controls the battle mode and layout.
\n– Boss action count is controlled separately by `actions_per_turn`.<\/p>\n
### `actions_per_turn`<\/p>\n
Purpose:<\/p>\n
Sets how many actions the Boss can take each turn.<\/p>\n
Rules:<\/p>\n
– Must be at least 1.
\n– Not limited by `battle_mode`.<\/p>\n
Notes:<\/p>\n
– Higher values make the Boss much harder.
\n– This is one of the main difficulty controls.<\/p>\n
### `scale`<\/p>\n
Purpose:<\/p>\n
Sets the Boss size.<\/p>\n
Position:<\/p>\n
Inside `random_configs`.<\/p>\n
How it works:<\/p>\n
– If set, the Boss uses this custom size.
\n– If omitted, the Boss size is calculated automatically from its level.<\/p>\n
Rules:<\/p>\n
– Must be greater than 0.
\n– The final value is clamped by the mod’s allowed size range.<\/p>\n
Notes:<\/p>\n
– Use this to create giant Bosses.
\n– Leave it empty for automatic level-based size.<\/p>\n
## 9. Boss Shield System<\/p>\n
Purpose:<\/p>\n
The Boss shield system gives a Boss extra protection during battle.<\/p>\n
How it works:<\/p>\n
– A Boss can start battle with shield layers.
\n– Certain attacks can consume shield layers.
\n– Super-effective damaging moves can consume shield layers.
\n– Special moves can consume configured shield layers.
\n– While shield still exists, some shield interactions can reduce or block damage.
\n– When shield reaches 0, the shield breaks.
\n– After shield breaks, the Boss can enter a weakened state.
\n– After weakened turns end, shield can recover each turn if recovery is configured.<\/p>\n
Important:<\/p>\n
The global shield switch in `boss-shield.toml` must be enabled.<\/p>\n
The Boss also needs shield fields inside `random_configs`.<\/p>\n
### `shield_layers`<\/p>\n
Purpose:<\/p>\n
Sets the Boss initial shield layers.<\/p>\n
Position:<\/p>\n
Inside `random_configs`.<\/p>\n
How it works:<\/p>\n
– `0` means this Boss has no shield.
\n– A value greater than 0 enables shield behavior for this Boss.
\n– This value is also used as the maximum shield layer count.<\/p>\n
Rules:<\/p>\n
– Must be 0 or higher.<\/p>\n
Notes:<\/p>\n
– This is the main field that enables shield for a specific Boss.
\n– If this value is 0, the other shield fields usually have no effect.<\/p>\n
### `shield_recover_per_turn`<\/p>\n
Purpose:<\/p>\n
Controls how many shield layers the Boss recovers each turn after shield break and weakened state.<\/p>\n
Position:<\/p>\n
Inside `random_configs`.<\/p>\n
How it works:<\/p>\n
– `0` means shield does not recover.
\n– A value greater than 0 allows shield recovery.
\n– Shield recovery cannot exceed maximum shield layers.<\/p>\n
Rules:<\/p>\n
– Must be 0 or higher.<\/p>\n
Notes:<\/p>\n
– Use 0 for one-time shield break behavior.
\n– Use higher values for raid-style repeated shield breaking.<\/p>\n
### `shield_weaken_turns`<\/p>\n
Purpose:<\/p>\n
Controls how many turns the Boss stays weakened after shield breaks.<\/p>\n
Position:<\/p>\n
Inside `random_configs`.<\/p>\n
How it works:<\/p>\n
– When shield reaches 0, the shield breaks.
\n– The Boss enters weakened state for this many turns.
\n– During weakened turns, shield recovery waits.
\n– After weakened turns end, shield recovery can begin if configured.<\/p>\n
Rules:<\/p>\n
– Must be 0 or higher.<\/p>\n
Notes:<\/p>\n
– Use this to create a damage window after shield break.
\n– Larger values give players more time to attack.
\n– `0` means no weakened delay.<\/p>\n
## 10. Phase Skill System<\/p>\n
### `phase_skills`<\/p>\n
Purpose:<\/p>\n
Changes Boss moves based on HP percentage.<\/p>\n
How it works:<\/p>\n
– Each phase has an HP percentage.
\n– When Boss HP reaches that percentage, the Boss can switch to another moveset.<\/p>\n
Notes:<\/p>\n
– Useful for multi-phase Boss fights.
\n– Avoid duplicate HP thresholds.
\n– Moves should be valid Cobblemon move names.<\/p>\n
### `hp_percent`<\/p>\n
Purpose:<\/p>\n
The HP percentage that triggers the phase.<\/p>\n
Rules:<\/p>\n
– Usually 1 to 100.
\n– Lower or equal HP enters that phase.<\/p>\n
Notes:<\/p>\n
– Higher values trigger earlier.
\n– Lower values trigger later.<\/p>\n
### `moves`<\/p>\n
Purpose:<\/p>\n
The moves used in this phase.<\/p>\n
Notes:<\/p>\n
– Usually 1 to 4 moves.
\n– Use this to make the Boss change strategy during battle.<\/p>\n
## 11. Stat Key Reference<\/p>\n
The following stat keys are used in `effort_values`, `evs`, `ivs`, and `custom_battle_stats`:<\/p>\n
– `hp`
\n– `attack`
\n– `defense`
\n– `special_attack`
\n– `special_defense`
\n– `speed`<\/p>\n
## 12. Configuration Files<\/p>\n
All configuration files are placed under:<\/p>\n
“`text
\nconfig\/cobbleboss\/
\n“`<\/p>\n
Unified config files:<\/p>\n
– `level-mapping.json`
\n– `pokemon-max-level.json`
\n– `boss-spawn.toml`
\n– `boss-level.toml`
\n– `boss-reward.toml`
\n– `boss-penalty.toml`
\n– `boss-battle-check.toml`
\n– `boss-capture.toml`
\n– `boss-immune.toml`
\n– `boss-music.toml`
\n– `boss-shield.toml`
\n– `player-level-limit.toml`<\/p>\n
Important:<\/p>\n
Fabric and NeoForge use the same field names and top-level TOML structure.<\/p>\n
If an old NeoForge config was generated before this unified version, delete the old config file or manually move values to the top level.<\/p>\n
### `level-mapping.json`<\/p>\n
Purpose:<\/p>\n
Maps player Pokemon level to Boss level.<\/p>\n
Notes:<\/p>\n
– Used only when custom level mapping is enabled.
\n– The left side is player level.
\n– The right side is Boss level.
\n– If no mapping is found, normal level calculation can be used.<\/p>\n
### `pokemon-max-level.json`<\/p>\n
Purpose:<\/p>\n
Controls Cobblemon’s global maximum Pokemon level.<\/p>\n
Fields:<\/p>\n
– `configName`
\n– `maxPokemonLevel`
\n– `description`<\/p>\n
Notes:<\/p>\n
– Default max level is usually 900.
\n– This affects the global Pokemon level limit used by Cobblemon.<\/p>\n
### `boss-spawn.toml`<\/p>\n
Purpose:<\/p>\n
Controls natural Boss spawning.<\/p>\n
Fields:<\/p>\n
– `enableBossSpawn`
\n– `checkIntervalTicks`
\n– `spawnChance`
\n– `enableSpawnTimeRandom`
\n– `randomValueMin`
\n– `randomValueMax`
\n– `spawnFrequency`<\/p>\n
Notes:<\/p>\n
– `checkIntervalTicks` range is 100 to 72000.
\n– `spawnChance` range is 0 to 1.
\n– `randomValueMin` and `randomValueMax` range is 1 to 10000.
\n– `spawnFrequency` range is 0 to 100.<\/p>\n
### `boss-level.toml`<\/p>\n
Purpose:<\/p>\n
Controls Boss level calculation.<\/p>\n
Fields:<\/p>\n
– `bossLevelMultiplier`
\n– `minBossLevel`
\n– `maxBossLevel`
\n– `includePCPokemon`
\n– `scaleByMaxLevel`
\n– `enableCustomLevelMapping`
\n– `enableLevelRandom`
\n– `randomMin`
\n– `randomMax`<\/p>\n
Notes:<\/p>\n
– `bossLevelMultiplier` range is 1.0 to 10.0.
\n– `minBossLevel` range is 1 to 100.
\n– `maxBossLevel` range is 50 to 200.
\n– `enableCustomLevelMapping` controls whether `level-mapping.json` is used.<\/p>\n
### `boss-reward.toml`<\/p>\n
Purpose:<\/p>\n
Controls default Boss reward chance.<\/p>\n
Fields:<\/p>\n
– `minDropRate`
\n– `maxDropRate`
\n– `levelScale`<\/p>\n
Important:<\/p>\n
Direct reward entries and reward pools with `chance` greater than 0 use their own chance.<\/p>\n
Direct reward entries and reward pools without `chance`, or with `chance` 0, use the default drop rate from this config.<\/p>\n
Notes:<\/p>\n
– `minDropRate` and `maxDropRate` range is 0 to 1.
\n– `levelScale` range is 1 to 1000.<\/p>\n
### `boss-penalty.toml`<\/p>\n
Purpose:<\/p>\n
Controls default punishment chance.<\/p>\n
Fields:<\/p>\n
– `enablePenalty`
\n– `minPenaltyChance`
\n– `maxPenaltyChance`
\n– `penaltyLevelScale`<\/p>\n
Important:<\/p>\n
Punish entries with `chance` greater than 0 use their own chance.<\/p>\n
Punish entries without `chance`, or with `chance` 0, use the default penalty chance from this config.<\/p>\n
Notes:<\/p>\n
– `minPenaltyChance` and `maxPenaltyChance` range is 0 to 1.
\n– `penaltyLevelScale` range is 1 to 1000.<\/p>\n
### `boss-battle-check.toml`<\/p>\n
Purpose:<\/p>\n
Controls Boss battle restriction checks.<\/p>\n
Fields:<\/p>\n
– `enableBattleCheck`
\n– `cancelBattle`
\n– `enablePokemonCheck`
\n– `bannedPokemonList`
\n– `enableItemCheck`
\n– `bannedItemsList`
\n– `enableMoveCheck`
\n– `bannedMovesList`<\/p>\n
Notes:<\/p>\n
– `enableBattleCheck` is the main switch.
\n– `cancelBattle` controls whether battle is cancelled when banned content is detected.
\n– `bannedPokemonList` uses Pokemon species IDs.
\n– `bannedItemsList` uses item IDs.
\n– `bannedMovesList` uses move IDs.<\/p>\n
### `boss-capture.toml`<\/p>\n
Purpose:<\/p>\n
Controls whether Boss Pokemon can be captured.<\/p>\n
Fields:<\/p>\n
– `preventBossCapture`
\n– `showCaptureMessage`<\/p>\n
Notes:<\/p>\n
– `preventBossCapture` should usually stay enabled.
\n– `showCaptureMessage` controls whether players see a message when capture is blocked.<\/p>\n
### `boss-immune.toml`<\/p>\n
Purpose:<\/p>\n
Controls whether Boss entities are invulnerable in the world.<\/p>\n
Fields:<\/p>\n
– `enableBossImmune`<\/p>\n
Important:<\/p>\n
This mainly protects Boss entities outside normal battle damage.<\/p>\n
It does not mean the Boss is immune to every move inside battle.<\/p>\n
Notes:<\/p>\n
– Recommended to keep enabled.
\n– Helps prevent players from killing Bosses with non-battle methods.<\/p>\n
### `boss-music.toml`<\/p>\n
Purpose:<\/p>\n
Controls Boss battle music.<\/p>\n
Fields:<\/p>\n
– `enableBossBattleMusic`
\n– `stopOnBattleEnd`<\/p>\n
Important:<\/p>\n
The music system no longer uses `bossBattleMusicSoundId`.<\/p>\n
When a Boss battle starts, the mod randomly selects a music sound event from:<\/p>\n
1. The mod’s built-in `assets\/cobbleboss\/sounds.json`.
\n2. Enabled resource packs that define music in `sounds.json`.<\/p>\n
Resource packs that are only placed in the `resourcepacks` folder but not enabled in the client resource pack menu are ignored.<\/p>\n
Notes:<\/p>\n
– Default built-in sound event is `cobbleboss:boss_battle_theme`.
\n– Custom music must be provided by a resource pack.
\n– The sound file should be OGG format.
\n– Players need the resource pack enabled to hear resource-pack music.
\n– Old configs containing `bossBattleMusicSoundId` should be regenerated or cleaned up.<\/p>\n
### `boss-shield.toml`<\/p>\n
Purpose:<\/p>\n
Controls the global Boss shield system.<\/p>\n
Fields:<\/p>\n
– `enableBossShield`
\n– `superEffectiveLayers`
\n– `moveLayerOverrides`<\/p>\n
Meaning:<\/p>\n
– `enableBossShield`: enables or disables Boss shield behavior.
\n– `superEffectiveLayers`: shield layers consumed by super-effective damaging moves.
\n– `moveLayerOverrides`: special move-to-shield-layer rules.<\/p>\n
Notes:<\/p>\n
– If `enableBossShield` is false, Boss JSON shield fields will not work.
\n– `moveLayerOverrides` uses move IDs and shield layer values.<\/p>\n
### `player-level-limit.toml`<\/p>\n
Purpose:<\/p>\n
Controls player Pokemon level limit.<\/p>\n
Fields:<\/p>\n
– `enableLevelLimit`
\n– `maxPlayerPokemonLevel`<\/p>\n
Notes:<\/p>\n
– `enableLevelLimit` enables the player Pokemon level cap.
\n– `maxPlayerPokemonLevel` sets the maximum allowed player Pokemon level.<\/p>\n
## 13. Resource Pack Music<\/p>\n
Boss battle music can be customized through resource packs.<\/p>\n
How it works:<\/p>\n
– The mod has built-in music in `assets\/cobbleboss\/sounds.json`.
\n– Enabled resource packs can add more music events.
\n– When a Boss battle starts, the mod randomly chooses one available music event.
\n– There is no need to specify one sound ID in config.<\/p>\n
Resource pack paths:<\/p>\n
“`text
\npack.mcmeta
\nassets\/cobbleboss\/sounds.json
\nassets\/cobbleboss\/sounds\/music\/
\n“`<\/p>\n
Example structure:<\/p>\n
“`text
\nmy_boss_music_pack.zip
\npack.mcmeta
\nassets\/cobbleboss\/sounds.json
\nassets\/cobbleboss\/sounds\/music\/boss_1.ogg
\nassets\/cobbleboss\/sounds\/music\/boss_2.ogg
\nassets\/cobbleboss\/sounds\/music\/boss_3.ogg
\n“`<\/p>\n
Example `sounds.json`:<\/p>\n
“`json
\n{
\n “music.boss_1”: {
\n “category”: “music”,
\n “sounds”: [
\n {
\n “name”: “cobbleboss:music\/boss_1”,
\n “stream”: true
\n }
\n ]
\n },
\n “music.boss_2”: {
\n “category”: “music”,
\n “sounds”: [
\n {
\n “name”: “cobbleboss:music\/boss_2”,
\n “stream”: true
\n }
\n ]
\n }
\n}
\n“`<\/p>\n
Matching files:<\/p>\n
“`text
\nassets\/cobbleboss\/sounds\/music\/boss_1.ogg
\nassets\/cobbleboss\/sounds\/music\/boss_2.ogg
\n“`<\/p>\n
Sound ID examples:<\/p>\n
– `music.boss_1` in `assets\/cobbleboss\/sounds.json` becomes `cobbleboss:music.boss_1`.
\n– `music.boss_2` in `assets\/cobbleboss\/sounds.json` becomes `cobbleboss:music.boss_2`.<\/p>\n
Music detection:<\/p>\n
The mod treats a sound event as Boss music if one of these is true:<\/p>\n
– The event key starts with `music`.
\n– The event key contains `.music`.
\n– The event has `”category”: “music”`.
\n– One of its sound file paths is inside a `music\/` folder.<\/p>\n
Notes:<\/p>\n
– Use OGG format.
\n– Use `stream: true` for music.
\n– Players need the resource pack enabled to hear custom music.
\n– Use original or licensed music only.
\n– If the resource pack is not enabled, the client will not register its sound events.<\/p>\n
## 14. Fixed Spawn Point Commands<\/p>\n
Main command:<\/p>\n
“`text
\n\/spawnpokemonbossat
\n“`<\/p>\n
Permission:<\/p>\n
Requires administrator permission.<\/p>\n
Functions:<\/p>\n
– `create`
\n– `addboss`
\n– `removeboss`
\n– `setweight`
\n– `remove`
\n– `list`
\n– `info`
\n– `trigger`
\n– `settext`
\n– `cleartext`
\n– `announcement enable`
\n– `announcement text`
\n– `announcement color`
\n– `announcement clear`<\/p>\n
### `create`<\/p>\n
Purpose:<\/p>\n
Creates a fixed Boss spawn point.<\/p>\n
Parameters:<\/p>\n
– Spawn point ID
\n– Dimension
\n– X coordinate
\n– Y coordinate
\n– Z coordinate
\n– Boss level
\n– Respawn seconds
\n– Optional hologram text<\/p>\n
Notes:<\/p>\n
– Spawn point ID must be unique.
\n– Respawn time is in seconds.
\n– Boss level range is 1 to 900.<\/p>\n
### `addboss`<\/p>\n
Purpose:<\/p>\n
Adds a Boss to a fixed spawn point pool.<\/p>\n
Parameters:<\/p>\n
– Spawn point ID
\n– Boss unique ID
\n– Weight<\/p>\n
Notes:<\/p>\n
– Boss unique ID must exist in loaded Boss data.
\n– Higher weight means higher chance inside that fixed spawn point.<\/p>\n
### `removeboss`<\/p>\n
Purpose:<\/p>\n
Removes a Boss from a fixed spawn point pool.<\/p>\n
### `setweight`<\/p>\n
Purpose:<\/p>\n
Changes the weight of a Boss in a fixed spawn point pool.<\/p>\n
### `remove`<\/p>\n
Purpose:<\/p>\n
Deletes a fixed spawn point.<\/p>\n
Notes:<\/p>\n
– Removes spawn point data.
\n– Removes related hologram display.
\n– Handles the currently active fixed Boss.<\/p>\n
### `list`<\/p>\n
Purpose:<\/p>\n
Lists all fixed spawn points.<\/p>\n
Shows:<\/p>\n
– Spawn point ID
\n– Dimension
\n– Coordinates
\n– Boss level
\n– Respawn time
\n– Boss pool
\n– Current active Boss<\/p>\n
### `info`<\/p>\n
Purpose:<\/p>\n
Shows detailed information for one spawn point.<\/p>\n
Shows:<\/p>\n
– Dimension
\n– Coordinates
\n– Boss level
\n– Respawn time
\n– Next respawn tick
\n– Current active Boss
\n– Hologram text
\n– Boss pool
\n– Announcement status
\n– Announcement text
\n– Announcement color<\/p>\n
### `trigger`<\/p>\n
Purpose:<\/p>\n
Manually makes a spawn point ready to spawn again.<\/p>\n
Notes:<\/p>\n
– Useful for testing.
\n– Does not delete the spawn point.<\/p>\n
### `settext`<\/p>\n
Purpose:<\/p>\n
Sets fixed spawn point hologram text.<\/p>\n
Supported placeholders:<\/p>\n
– `{id}`
\n– `{level}`
\n– `{time}`
\n– `{x}`
\n– `{y}`
\n– `{z}`
\n– `{dimension}`
\n– `{boss_count}`
\n– `{boss_pool}`
\n– `{active_boss_id}`
\n– `{active_boss}`
\n– `{active_weight}`<\/p>\n
Notes:<\/p>\n
– Use `|` to separate multiple hologram lines.
\n– Hologram placeholders are different from announcement placeholders.<\/p>\n
### `cleartext`<\/p>\n
Purpose:<\/p>\n
Clears custom hologram text and restores default hologram behavior.<\/p>\n
### `announcement enable`<\/p>\n
Purpose:<\/p>\n
Enables or disables fixed spawn point announcement.<\/p>\n
How it works:<\/p>\n
– `true` enables announcement.
\n– `false` disables announcement.<\/p>\n
Notes:<\/p>\n
– There is no separate announcement disable command.
\n– Use `announcement enable` with true or false.<\/p>\n
### `announcement text`<\/p>\n
Purpose:<\/p>\n
Sets custom announcement text.<\/p>\n
Supported placeholders:<\/p>\n
– `{boss}`
\n– `{boss_id}`
\n– `{species}`
\n– `{point}`
\n– `{dimension}`
\n– `{x}`
\n– `{y}`
\n– `{z}`
\n– `{position}`<\/p>\n
### `announcement color`<\/p>\n
Purpose:<\/p>\n
Sets announcement message color.<\/p>\n
Available colors:<\/p>\n
– `black`
\n– `dark_blue`
\n– `dark_green`
\n– `dark_aqua`
\n– `dark_red`
\n– `dark_purple`
\n– `gold`
\n– `gray`
\n– `dark_gray`
\n– `blue`
\n– `green`
\n– `aqua`
\n– `red`
\n– `light_purple`
\n– `yellow`
\n– `white`<\/p>\n
Notes:<\/p>\n
– Default color is `gold`.
\n– This changes announcement color, not Boss glow color.<\/p>\n
### `announcement clear`<\/p>\n
Purpose:<\/p>\n
Restores the default announcement text.<\/p>\n
Notes:<\/p>\n
– Does not remove the spawn point.
\n– Does not clear hologram text.
\n– Only resets the fixed spawn announcement template.<\/p>\n
### Fixed Spawn Boss Pool Weight<\/p>\n
Purpose:<\/p>\n
Controls selection chance inside one fixed spawn point.<\/p>\n
Rules:<\/p>\n
– Minimum weight: 1
\n– Maximum weight: 1000000<\/p>\n
Notes:<\/p>\n
– This is separate from natural `spawn_rule.spawn_weight`.
\n– Higher weight means higher chance inside that fixed spawn point pool.<\/p>\n
## 15. Basic Boss Commands<\/p>\n
### `checkpokemonboss`<\/p>\n
Purpose:<\/p>\n
Checks which Bosses can spawn at the player’s current location.<\/p>\n
Shows:<\/p>\n
– Time until next Boss refresh
\n– Matching Bosses
\n– Boss display names
\n– Spawn weights<\/p>\n
Permission:<\/p>\n
Usually available to normal players.<\/p>\n
### `spawnpokemonboss`<\/p>\n
Purpose:<\/p>\n
Directly spawns a Boss near the player.<\/p>\n
Parameters:<\/p>\n
– Boss unique ID
\n– Optional level<\/p>\n
Permission:<\/p>\n
Requires administrator permission.<\/p>\n
Notes:<\/p>\n
– Uses Boss unique ID, not species ID.
\n– Level range is 1 to 900.
\n– Useful for testing Boss configuration.<\/p>\n
### `spawnpokemonbossat`<\/p>\n
Purpose:<\/p>\n
Manages fixed Boss spawn points.<\/p>\n
Permission:<\/p>\n
Requires administrator permission.<\/p>\n
## 16. Beginner Setup Suggestions<\/p>\n
For the simplest setup:<\/p>\n
– Enable natural Boss spawning.
\n– Use a reasonable spawn interval.
\n– Use a low spawn chance at first.
\n– Enable Boss capture prevention.
\n– Enable Boss immunity.
\n– Use level mapping or level multiplier.
\n– Add rewards with reasonable chance values.
\n– Add glow to make Bosses easier to find.
\n– Leave scale empty unless you want giant Bosses.<\/p>\n
For stricter Boss servers:<\/p>\n
– Enable battle checks.
\n– Ban specific Pokemon if needed.
\n– Ban specific items if needed.
\n– Ban specific moves if needed.
\n– Increase Boss stats through `custom_battle_stats`.
\n– Use `actions_per_turn` carefully.
\n– Add shield settings for raid-style fights.<\/p>\n
For casual servers:<\/p>\n
– Keep punishments low or disabled.
\n– Use visible Boss glow.
\n– Use moderate Boss size.
\n– Give guaranteed small rewards and rare special rewards.
\n– Use reward pools for “one item from this group” rewards.
\n– Avoid extremely high `actions_per_turn`.<\/p>\n
## 17. Common Problems<\/p>\n
### Boss does not load<\/p>\n
Possible reasons:<\/p>\n
– Duplicate `unique_id`.
\n– Invalid `species_id`.
\n– Invalid move name.
\n– Invalid ability name.
\n– Invalid item ID.
\n– Invalid glow color.
\n– Invalid scale value.
\n– Broken JSON format.
\n– Empty `reward_pools.entries`.
\n– Invalid reward pool `rolls`.
\n– Invalid reward pool entry `weight`.<\/p>\n
### Boss does not spawn naturally<\/p>\n
Possible reasons:<\/p>\n
– Natural spawning is disabled.
\n– Spawn chance is too low.
\n– Spawn interval has not passed.
\n– Current biome does not match.
\n– Current structure does not match.
\n– Current time does not match.
\n– Current location type does not match.
\n– `spawn_weight` is missing or too low.
\n– Boss file is not loaded.<\/p>\n
### Boss music does not play<\/p>\n
Possible reasons:<\/p>\n
– Boss music config is disabled.
\n– The selected sound event is not registered on the client.
\n– Resource pack is not enabled.
\n– Sound file path is wrong.
\n– Sound file is not OGG format.
\n– Client does not have the resource pack.
\n– The resource pack was placed in the folder but not moved to the enabled list.
\n– Music volume is muted.<\/p>\n
Important:<\/p>\n
The mod randomly chooses from built-in music and enabled resource packs.<\/p>\n
It does not use `bossBattleMusicSoundId`.<\/p>\n
### Boss shield does not work<\/p>\n
Possible reasons:<\/p>\n
– Global Boss shield config is disabled.
\n– `shield_layers` is 0 or missing.
\n– The move used does not consume shield layers.
\n– `superEffectiveLayers` is set to 0.
\n– The move is not super-effective.
\n– The move is not listed in `moveLayerOverrides`.
\n– Boss was spawned from old or outdated data.<\/p>\n
### Boss is too small or too large<\/p>\n
Possible reasons:<\/p>\n
– `scale` is set too low or too high.
\n– Boss level causes automatic scale calculation.
\n– Scale is clamped by the mod’s allowed range.<\/p>\n
### Boss does not glow<\/p>\n
Possible reasons:<\/p>\n
– `glow` is not set.
\n– Glow color is invalid.
\n– Boss was spawned from old data.
\n– Another system removed the glow effect.<\/p>\n
### Announcement color does not change<\/p>\n
Possible reasons:<\/p>\n
– The color name is invalid.
\n– The wrong spawn point ID was used.
\n– Announcement is disabled.
\n– The message being checked is not the fixed spawn announcement.<\/p>\n
### Old NeoForge config does not work<\/p>\n
Possible reasons:<\/p>\n
– The config was generated before unified config fields.
\n– Old grouped TOML sections are still present.
\n– Old shield snake_case fields are still present.
\n– Old `bossBattleMusicSoundId` is still present.<\/p>\n
Fix:<\/p>\n
– Delete the old config file and let the mod regenerate it.
\n– Or move the old values to the new top-level fields.
\n– Remove old music sound ID configuration.<\/p>\n
## 18. Summary<\/p>\n
CobbleBoss configuration can be understood like this:<\/p>\n
– Use `unique_id`, `species_id`, `display_name`, and `glow` to define Boss identity and appearance.
\n– Use `spawn_rule` to define where and when it appears.
\n– Use `reward_rule` and `punish_rule` to define win and loss results.
\n– Use `reward_items` for independent reward rolls.
\n– Use `reward_pools` for “roll once, then choose one reward from this list”.
\n– Use `random_configs` to define stats, moves, battle mode, action count, shield, phase skills, held items, form, ability, shiny state, and size.
\n– Use config files to control global Boss behavior.
\n– Use resource packs to add random Boss battle music.
\n– Use fixed spawn point commands to create controlled Boss spawn locations.<\/p>\n
## 19. Paid Feature: Multiplayer Team Boss Battles<\/p>\n
This is an advanced paid feature.<\/p>\n
Data pack path:<\/p>\n
“`text
\ndata\/cobbleboss\/boss_teams\/
\n“`<\/p>\n
A Boss team file defines a group Boss battle.<\/p>\n
Fields:<\/p>\n
– `team_id`
\n– `pokemon_unique_ids`
\n– `spawn_structures`
\n– `defeat_rewards`
\n– `punish_rule`<\/p>\n
### `team_id`<\/p>\n
Purpose:<\/p>\n
The unique ID of the Boss team.<\/p>\n
Notes:<\/p>\n
– If no namespace is written, `cobbleboss` is used.
\n– Commands can use this ID.<\/p>\n
### `pokemon_unique_ids`<\/p>\n
Purpose:<\/p>\n
The Boss Pokemon unique IDs used by this team.<\/p>\n
Notes:<\/p>\n
– These IDs must match normal Boss JSON `unique_id` values.
\n– The team system creates Boss Pokemon from existing Boss definitions.<\/p>\n
### `spawn_structures`<\/p>\n
Purpose:<\/p>\n
Controls which structures can trigger this Boss team.<\/p>\n
Notes:<\/p>\n
– Uses structure IDs.
\n– When a player is inside a matching structure and sends out a Pokemon, the team battle can be triggered.
\n– Structure instances are recorded so the same structure is not repeatedly triggered.<\/p>\n
### `defeat_rewards`<\/p>\n
Purpose:<\/p>\n
Rewards after defeating the Boss team.<\/p>\n
Fields:<\/p>\n
– `reward_items`
\n– `reward_pools`
\n– `item_id`
\n– `count`
\n– `command`
\n– `chance`
\n– `rolls`
\n– `weight`<\/p>\n
How it works:<\/p>\n
– `reward_items` behave as independent reward rolls.
\n– `reward_pools` roll once, then randomly choose entries from the pool.
\n– Team reward pools use the same format as normal Boss reward pools.<\/p>\n
Chance note:<\/p>\n
If `chance` is greater than 0, that custom chance is used.<\/p>\n
If `chance` is missing or 0, the default reward chance can be used.<\/p>\n
Example:<\/p>\n
“`json
\n“defeat_rewards”: {
\n “reward_items”: [
\n {
\n “item_id”: “minecraft:gold_ingot”,
\n “count”: 4,
\n “chance”: 1.0
\n }
\n ],
\n “reward_pools”: [
\n {
\n “chance”: 0.1,
\n “rolls”: 1,
\n “entries”: [
\n {
\n “item_id”: “cobblemon:poke_ball”,
\n “count”: 3
\n },
\n {
\n “item_id”: “cobblemon:great_ball”,
\n “count”: 2
\n },
\n {
\n “item_id”: “cobblemon:ultra_ball”,
\n “count”: 1
\n }
\n ]
\n }
\n ]
\n}
\n“`<\/p>\n
### `punish_rule`<\/p>\n
Purpose:<\/p>\n
Punishments after losing to the Boss team.<\/p>\n
Fields:<\/p>\n
– `punish_items`
\n– `level`
\n– `evs`
\n– `ivs`
\n– `command`
\n– `chance`<\/p>\n
Chance note:<\/p>\n
If `chance` is greater than 0, that custom chance is used.<\/p>\n
If `chance` is missing or 0, the default penalty chance can be used.<\/p>\n
### `spawnpokemonbossteam`<\/p>\n
Purpose:<\/p>\n
Manually starts a Boss team battle for a player.<\/p>\n
Command meaning:<\/p>\n
“`text Permission:<\/p>\n Requires administrator permission.<\/p>\n Notes:<\/p>\n – `bossTeamId` can be written with or without namespace. ### Multiplayer Team Battle Behavior<\/p>\n How it works:<\/p>\n – The system scans nearby valid players. Notes:<\/p>\n – This feature is best explained after normal Boss configuration. A mod that allows you to infinitely add and customize your own exclusive Bosses in the Cobblemon world.<\/p>\n","protected":false},"featured_media":41992,"template":"","meta":{"_minecraft_slug":"cobbleboss","_minecraft_project_id":"1O31TjSK","_minecraft_author":"RainApricot","_minecraft_license":"LicenseRef-All-Rights-Reserved","_minecraft_downloads":736472,"_minecraft_follows":20,"_minecraft_client_side":"required","_minecraft_server_side":"required","_minecraft_storage_type":"zip","_minecraft_archive_name":"cobbleboss.zip","_minecraft_size_bytes":4567686,"_minecraft_version_count":12,"_minecraft_updated_at":"2026-05-16T15:10:30.907330Z","_minecraft_date_created":"2025-11-23T06:42:28.503903Z","_minecraft_date_modified":"2026-05-08T06:31:53.048246Z","_minecraft_project_url":"https:\/\/modrinth.com\/mod\/cobbleboss","_minecraft_icon_attachment_id":41992,"_minecraft_imported_at":"2026-06-01T23:21:31+00:00","_minecraft_import_hash":"c5d33cd212ef2bb392489d2bb2d00ce4","_minecraft_versions":"","_minecraft_links":"","_minecraft_gallery":"","_minecraft_api_metadata":""},"mod_category":[87,43,97,89,126,866,158,867,92,159],"mod_loader":[99,160],"minecraft_version":[37],"class_list":["post-41991","mod","type-mod","status-publish","has-post-thumbnail","hentry","mod_category-adventure","mod_category-cursed","mod_category-fabric","mod_category-game-mechanics","mod_category-management","mod_category-minigame","mod_category-neoforge","mod_category-social","mod_category-utility","mod_category-worldgen","mod_loader-fabric","mod_loader-neoforge","minecraft_version-1-21-1"],"yoast_head":"\n
\n\/spawnpokemonbossteam
\n“`<\/p>\n
\n– If no namespace is written, `cobbleboss` is used.
\n– This command is mainly for testing and admin-controlled events.<\/p>\n
\n– Nearby players must not already be in battle.
\n– Spectators and removed players are ignored.
\n– The current team battle system is designed around up to 2 players.
\n– The current Boss team battle system uses up to 2 Boss Pokemon.
\n– This creates a 2v2 raid-style battle when enough players and Bosses are available.
\n– If multiplayer conditions are not met, it can fall back to a single-player team Boss battle.<\/p>\n
\n– It is intended for servers that want raid-style gameplay.
\n– Boss stats, rewards, shield, and `actions_per_turn` should be balanced carefully for team battles.<\/p>\n","protected":false},"excerpt":{"rendered":"