Integrations

Mo’Bosses works with a few popular plugins when they run. The mods’ counterparts are on Fabric and NeoForge. None is required, and each one turns on by itself: install it, restart, and the log says what Mo’Bosses found.

PlaceholderAPI

With PlaceholderAPI installed, scoreboards, tab lists, and chat plugins can show:

Placeholder	What it shows
%mobosses_level%	The player’s Mo’Bosses level
%mobosses_xp%	Their Mo’Bosses experience (%mobosses_experience% works too)
%mobosses_kills%	Bosses they helped kill
%mobosses_deaths%	Times a boss killed them, since 2.20.0
%mobosses_streak%	Deaths to bosses in a row, with no kill between. From the third, each costs a level
%mobosses_damage%	Health they took from bosses that died, whole

They read only players who are online. Anyone else shows 0, or level 1.

In Mo’Bosses’ own messages, write <papi:name> to show %name% for the player who reads it. Mo’Bosses doesn’t look for %…% in your text, so a percent sign stays a percent sign.

MiniPlaceholders

Every message is MiniMessage. With MiniPlaceholders installed, messages take its tags as they are, for the player who reads them, like <luckperms_prefix>. Mo’Bosses adds tags of its own for TAB and other plugins, each about the player they’re shown for:

Tag	What it shows
<mobosses_level>	The player’s Mo’Bosses level
<mobosses_xp>	Their Mo’Bosses experience
<mobosses_kills>	Bosses they helped kill
<mobosses_deaths>	Times a boss killed them
<mobosses_streak>	Deaths to bosses in a row
<mobosses_damage>	Health they took from bosses that died

Plan

With Plan installed, Mo’Bosses adds its section to Plan’s pages:

• A player’s “Plugins” tab shows their level, experience, kills, deaths to bosses, the deaths in a row, and the damage they dealt to bosses. The level is also a column in the players table.
• The server’s “Plugins Overview” shows the bosses alive, spawned, and killed, and the players bosses killed, a table of the best hunters, and tables of bosses by class and by type, each with the players they killed.

Plan keeps the last values while a player is away.

WorldAPI

With WorldAPI 4.5.0 or newer installed, Mo’Bosses shares its data for a site or a bot, and with 4.6.0 lets them spawn and remove bosses, under WorldAPI’s /extensions/mobosses. Mo’Bosses keeps the data, and WorldAPI reads it on request.

It shares through WorldAPI’s expansion API 2, so WorldAPI’s GET /extensions lists each resource’s parameters and the fields of every answer and event. With an older WorldAPI the log says WorldAPI is too old for Mo’Bosses' data: it needs 4.5.0 or newer, and the rest of Mo’Bosses works as usual.

Resource	What it returns
hunters?limit=10	The best hunters by level, with kills, experience, deaths, the streak, and damage (1 to 50, as before 2.22.0)
players/{player}	A player’s card, by UUID or name of someone who has played on the server: level, experience, kills, deaths to bosses, streak of deaths in a row, damage dealt to bosses killed, and rank
players/{player}/bestiary	Kills and best level by boss type and class
leaderboards/{kills|level|experience|deaths|damage}?limit=10	Players ranked the way WorldAPI ranks its own boards (1 to 500)
stats	Bosses alive now, spawned, killed, and the players they killed (playerKills), in all and by type and class. Also abilities: how many times each ability went off since 2.20.1, kept in the database
bosses	The bosses alive in loaded chunks, with health and coordinates. Each one’s uuid is the id DELETE bosses/{boss} takes. Needs a token

Everything but bosses is public, and bosses shows coordinates only to tokens with players:private. Events arrive on WorldAPI’s WebSocket as ext.mobosses.<event>:

Event	When	In WorldAPI’s history
boss.killed	Players killed a boss: its type, class, level, and location, each player’s share, and the biggest one as player	yes
player.level_up	A player reached a new Mo’Bosses level: from, level, the player, and their location	yes
player.achievement	A player earned an achievement: its id and title, the player, and their location	yes
full_moon	A full moon rose	yes
player.demoted	Deaths to bosses in a row cost a player a level: from, level, the streak, the player, and their location	yes
player.died_to_boss	A boss killed a player, what progress it burned (lost), their deaths in a row (streak), and whether this one cost a level (demoted)	no
boss.phase_two	A boss entered its second phase	no

A boss’s or a player’s location reaches only clients that may see coordinates: WorldAPI leaves it out for the rest. WorldAPI’s own docs explain tokens and its extensions.private setting, which can close any of this.

Actions

With WorldAPI 4.6.0 or newer, a client with a token that holds world:write can also spawn and remove bosses, so a bot or the MCP server can set up a fight. WorldAPI never lets a visitor without a token call them, and writes every call into its audit log. With WorldAPI 4.5 the log says This WorldAPI takes no actions, and the resources and events above work as usual.

Action	Body or path	What it does
POST bosses/spawn	type (required), class (common by default), level (1 by default), count 1 to 5, at (required): {"world": "world", "x": 0, "y": 64, "z": 0}	Spawns bosses at the place, as /mobosses spawn does and under its rules: they stay until killed, and protection applies unless protection.admin_spawn_bypass is on. Answers with each boss’s uuid, type, class, level, and location
DELETE bosses/{boss}	a boss’s uuid from bosses or a spawn	Removes a live boss as /mobosses killall does: no loot, no experience, no kill for anyone. Answers with the boss it removed

An unknown type, a level past the server’s top, or a world that isn’t loaded answers 400 and says why, and an id no boss alive has answers 404. On Fabric and NeoForge a world is a dimension, as WorldAPI names it there: overworld, the_nether, the_end, or a mod’s namespace:path, and Paper’s world, world_nether, and world_the_end work too.

curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  -d '{"type": "zombie", "class": "epic", "level": 40, "at": {"world": "world", "x": 0, "y": 64, "z": 0}}' \
  https://example.com/worldapi/api/v1/extensions/mobosses/bosses/spawn

Grafana

Since 2.21.0 each release carries mobosses.json, a Grafana dashboard of this data: bosses alive, spawned, and killed, by type and by class, the best hunters, abilities cast, and the latest fights. It reads WorldAPI through the Infinity data source:

1. Add an Infinity data source whose base URL is your WorldAPI, like https://example.com/worldapi/api/v1.
2. Import mobosses.json from the latest release.
3. Pick that data source in the dashboard’s WorldAPI menu.

Its panels read only what WorldAPI gives anonymous clients, so the data source needs no token unless your WorldAPI closes those resources.

Allay

With Allay 6.33.0 or newer installed, players can ask the AI helper about Mo’Bosses, and it answers from this server’s own settings instead of guessing. The log says Allay found, and Allay’s own line says Expansion Mo’Bosses … is on: 8 tools, 203 items, a prompt (the item count follows your loot table). An older Allay says in the log that it needs a newer one, and the rest of Mo’Bosses works as usual.

Mo’Bosses gives it eight tools through Allay’s expansion API 2, and a few lines on how bosses, classes, levels, loot, rewards, spawner fatigue, and the full moon work. Every tool but spawn only reads, so Allay offers them to every player, in /askx too.

Tool	Arguments	What the model learns	In public questions
x_mobosses_classes	–	The six classes: each one’s name, its share of new bosses in percent, its multipliers, and the boss level each ability starts at	yes
x_mobosses_bosses	type	The mobs that become bosses: spawn and bonus loot chances, the minion each summons, and its signature abilities. Also whether bosses spawn by themselves here. With type, that boss alone, in full: its experience multiplier, whether only adults or charged ones turn, whether it’s a world boss, each weapon and piece of armor with the level it starts at, and how many loot entries are its own	yes
x_mobosses_hunt	–	The asker’s level, experience and what the next level needs, kills, place among hunters, when a boss may come near them again, their survival bonus in minutes and percent, whether a full moon is up and what it multiplies spawn chances by, whether dying burns progress, and their bestiary	no
x_mobosses_nearby	–	The bosses within 64 blocks of the asker, nearest first: type, class, level, health, enrage and second phase, coordinates, distance, the abilities each has reached, the asker’s own share of its damage, how many players fight it, and how much its health grew for the group	no
x_mobosses_loot	class, level, type, item	What a boss of a class, level, and type drops: the 20 likeliest items with each one’s chance to be one item a player gets, amount, and name, how many items a player who dealt enough damage gets, the share that takes alone, and the type’s bonus roll. With item, where that item comes from: the class, levels, and types that drop it. Without class it reads Common, without level the asker’s own level	yes
x_mobosses_abilities	ability	Each ability with a line on what it does and the boss level it starts at in each class, and each signature move with its boss types. With ability, that one in full: what it does, a tip to counter it, its cooldown, reach, and damage from abilities.yml, and the health that sets it off	yes
x_mobosses_hunters	limit, 1 to 10	The best hunters by experience: place, level, kills, and experience. Allay names each player as its consent rules allow and leaves out vanished ones	yes
x_mobosses_spawn	type (required), class, level, count 1 to 5	Spawns bosses two blocks ahead of the asker, as /mobosses spawn does, with every rule of the command. For operators with mobosses.spawn alone, never in /askx	no

nearby names no other player and gives no one else’s share of the damage. Names of bosses, classes, and items come in the language Allay answers the player in. Allay’s expansions.disabled setting can switch Mo’Bosses’ tools off, as for any expansion.

Mo’Bosses also hands Allay its loot table’s named drops, like the Apprentice’s Stone Blade: each one’s names in every language Mo’Bosses has, the item it’s made from, and which bosses drop it. Allay’s item search finds them by any of these names, and /mobosses reload updates them.

Protection and logging

GriefPrevention, WorldGuard, and CoreProtect have a page of their own: Claims and protection.