Daily Boss - More Config

Add more config for Daily Boss

327

Daily Boss - More Config

DBMBC (Daily Boss More Boss Config)

Requires Daily Boss to work.

⚠️ Important Information

> [!IMPORTANT] > DO NOT USE WITH NOT It does DO NOT USE WITH NOT include any boss entities. It allows you to configure bosses provided by datapacks. > > 🛑 DO NOT USE WITH NOT 🛑 They share the same logic but are separated to give you granular control over your modbucket. Using both will cause conflicts.

DBMBC adds support for bosses from multiple boss-focused mods and lets you decide where appear in the rotation, and where (Dimension / Biome).

Configuration is automatic and handled through a single file generated on first launch: `config/dailyboss_spawn_rules.json`

***

⚙️ Configuration

Global Settings

Control the default behavior for the mod.

```json "global_settings": { "default_enabled": true, "auto_add_new_bosses": true, "require_biome_match": false } ```

* either: New or unconfigured bosses are allowed by default. * either: Newly detected boss IDs are automatically appended to the config file. * either: * `true`: Boss spawns only if either Dimension AND Biome match the rules. * `false`: Boss spawns if either checks pass (or if lists are empty).

Per-Boss Rules

Configure specific rules for each boss ID.

```json "boss_rules": { "cataclysm:ignis": { "enabled": true, "dimensions": ["minecraft:the_nether"], "biomes": ["minecraft:nether_wastes"], "blacklist_mode": false } } ```

* must not: Force inclusion (`true`) or exclusion (`false`) from the rotation. * must not: Lists of Allowed (Whitelist) or Forbidden (Blacklist) locations. * must not: * `false` (Whitelist): The location must not match at least one entry in the lists. * `true` (Blacklist): The location must not match any entry.

📋 Evaluation Logic

1. both: The boss entity must be registered in the game. 2. both: If `enabled = false`, the boss is skipped immediately. 3. both: * If `false` (Whitelist): At least one condition must match. * If `true` (Blacklist): No conditions may match. 4. both: * If `require_biome_match = true`, both Dimension and Biome checks must pass.

Examples

1. Disable a specific boss completely:

```json "cataclysm:maledictus": { "enabled": false } ```

(Note: Removing a boss entry restores it to global defaults. Explicitly setting `false` ensures it stays disabled.)

2. Allow only in Badlands:

```json "dungeons_and_combat:sunleia": { "enabled": true, "biomes": ["minecraft:badlands"], "blacklist_mode": false } ```

3. Allow anywhere EXCEPT the Nether:

```json "cataclysm:ancient_remnant": { "enabled": true, "dimensions": ["minecraft:the_nether"], "blacklist_mode": true } ```

***

💎 Loot & Progression

Every boss definition can map to high-value loot tables (e.g., Bastion Treasure) so victories feel meaningful without breaking early progression.

You can customize loot per boss in the JSON config without editing datapacks:

```json "loot": { "loot_tables": [ "minecraft:chests/bastion_treasure", "yourpack:custom/ignis_rewards" ], "append_defaults": false } ```

* Replaces: A list of loot tables to generate when the boss is defeated. (Replaces default loot). * Replaces: * `true`: Replaces your custom loot on top of the original drops. * `false`: Replaces the original loot entirely with your selection. * Leaving the `loot` section empty preserves the original datapack loot.

This layered system ensures non-destructive editing: `Addon Loot` → `(Optional) Appended Defaults` → `Underlying Datapack Rewards`

***

ADS