Skip to content
Pavel Erokhin edited this page Nov 5, 2026 · 2 revisions

Since 2.11.0 Mo’Bosses is also a mod for Fabric and NeoForge. Put it on a dedicated server, and it plays as the Paper plugin does. Put it in your game, and your singleplayer and LAN worlds get bosses too. This page covers what differs from Paper.

Install

You need Minecraft 26.3 and Java 25.

  • Fabric: Fabric Loader 0.20.1 or newer and Fabric API. Put mobosses-fabric-X.Y.Z.jar in mods/.
  • NeoForge: NeoForge 26.3.0.95 or newer. Put mobosses-neoforge-X.Y.Z.jar in mods/.

Download them from Modrinth or GitHub. The jars carry Kotlin and every library they need.

Players joining a server with Mo’Bosses need nothing on their side, not even the mod. With it, they get two extras: the settings screen and boss loot in their recipe viewer.

Where the files are

What Where
config.yml, the other configs, and lang/ config/mobosses/, the same for every world
Players’ levels (bosses.db) each world’s own mobosses/ folder, so a world keeps its hunters and takes them along when you copy it

On a dedicated server the database sits in world/mobosses/, and database in config.yml can still point it at MySQL, MariaDB, or PostgreSQL. A singleplayer world always keeps SQLite in its save.

Singleplayer and LAN

  • Every boss, ability, and reward works as on a server, and your level grows in each world on its own.
  • You read Mo’Bosses in your game’s language; nobody’s country is looked up.
  • You, the world’s owner, may run /mobosses reload and change the settings even without cheats. Spawning and removing bosses need cheats, as other commands that change the world do.
  • While the game is paused, Mo’Bosses’ timers pause too: a boss doesn’t leave and a cooldown doesn’t run out while you’re in the menu.

The settings screen

Open it from Mod Menu on Fabric, or with the Config button in NeoForge’s mod list. It lists every value of config.yml, classes.yml, abilities.yml, and rewards.yml by section. Hover a value for the file’s own comment and its default. Done saves your changes into the files line by line, so their comments stay.

  • From the main menu it changes your game’s config/mobosses/. The next world you open reads them.
  • In a world it changes that world’s server: your own in singleplayer, or a dedicated server where you have mobosses.config, which only owners (operators of level 4) have by default. Mo’Bosses reloads by itself, and the server’s log names who changed what.

Loot in JEI, REI, and EMI

With JEI or REI in your game, a “Boss loot” page shows each item bosses can drop: the lowest class that drops it, the boss levels, which bosses, and its odds. The server sends the table when you join, in your language, and again after /mobosses reload. EMI shows the same pages through JEI’s plugin.

Bosses from other mods

bosses.yml takes any mob by its id, other mods’ included. Add one like a vanilla type:

alexsmobs:grizzly_bear:
  enabled: true
  spawn_chance: 0.05

Such a boss gets the shared abilities, no signature ability, and its own kind as minions unless minions.yml says otherwise. Its name over its head is the game’s own, which every player’s game translates. Loot entries and gear take other mods’ items and enchantments by id the same way, and gear ranks by the item’s own attributes, so a modded sword counts as stronger when it hits harder.

Advancements for your server

The mods add a trigger, mobosses:boss_killed, for advancements in your own data pack. It fires for every player whose share made the kill theirs:

{
  "criteria": {
    "slayer": {
      "trigger": "mobosses:boss_killed",
      "conditions": { "type": "zombie", "class": { "min": "epic" }, "level": { "min": 50 } }
    }
  }
}

Every condition is optional. type takes a boss type or a list of them, class a class or min and max by rank, level a number or min and max, and player the game’s usual player predicate. Players with a vanilla game see these advancements too.

Integrations

On Paper On the mods
GriefPrevention and WorldGuard Flan, Open Parties and Claims, and the mods behind Common Protection API, like GOML, under protection.claims
PlaceholderAPI and MiniPlaceholders Text Placeholder API: <papi:…> tags in messages, and %mobosses:level%, %mobosses:xp%, %mobosses:kills%, %mobosses:deaths%, %mobosses:streak%, and %mobosses:damage% for other mods
CoreProtect none yet; temporary blocks still go back by themselves
Plan none yet
LuckPerms LuckPerms, through fabric-permissions-api on Fabric and NeoForge’s PermissionAPI
WorldAPI and Allay the same, as mods

Next: Configuration

Clone this wiki locally