Skip to content

Commands & Permissions ​

Every /emakimobs subcommand, its permission node, and ready-to-copy examples are listed below. The root command is /emakimobs, with /emobs as an alias. Running it without a subcommand prints the usage hint; an unknown subcommand does the same

Commands ​

Every subcommand's mob_id argument is case-sensitive: it is matched exactly against definition ids, and an unknown id reports an unknown mob

CommandPermissionDescription
/emakimobs spawn <mob_id> [player]emakimobs.spawnSpawn the specified mob at the target player's location. When player is omitted, spawns at the command sender's location; from the console, player is required. player is matched exactly by name (Bukkit.getPlayerExact); a missing or offline player reports no target
/emakimobs reloademakimobs.reloadReload all mob definitions, loot tables, spawn rules, and target selectors without restarting the server. When the precheck finds an ERROR the commit is rejected and the previous content is restored; the reported count is then the number of definitions still in effect
/emakimobs list [page]emakimobs.listPaginate through every registered mob definition (10 per page, sorted by id), with a header line giving total pages, total count and the current page. page defaults to 1; a non-positive integer reports an invalid page and an out-of-range page reports the range
/emakimobs info <mob_id>emakimobs.infoShow the mob's vanilla type, components key count, ea_attributes key count, configured trigger list, and whether a matching loot_tables/<mob_id>.yml exists
/emakimobs kill <mob_id> [radius]emakimobs.adminRemove managed mobs of that id. With radius, only targets within that radius of the executor are removed, so the radius form is player-only; radius must be a finite value ≥ 0
/emakimobs kill all [radius]emakimobs.adminRemove all managed mobs regardless of id. Without radius it scans every world; with radius only targets within that range are removed (also player-only)
/emakimobs count [mob_id]emakimobs.countCount managed mobs; with mob_id omitted it counts all of them (reported as * in the message). Only entities whose PDC id is still in the currently loaded set are counted; an unregistered mob_id reports an unknown mob
/emakimobs find <mob_id> [radius]emakimobs.countFind managed mobs and list them sorted by distance (up to 20 entries plus a truncation line). radius omitted means unlimited range; player-only. Each entry shows id, UUID and health on hover, and clicking runs /emakimobs tp <uuid>
/emakimobs tp <uuid>emakimobs.adminTeleport to the managed mob with that UUID; a missing or unmanaged target is rejected. Usually triggered from a find list entry
/emakimobs edit [id]emakimobs.editOpen the in-game definition editor: omitting id opens the file browser (paging, create, delete), passing id opens that mob definition for field-by-field editing
/emakimobs helpemakimobs.usePrint the command help list
/emakimobs debug ...emakimobs.debugForwards to the module's debug subcommand (CoreLib debug command, module filter mobs); reports when the debug handler is unavailable

count, kill and find scan entities through the dispatcher and deliver the result back to the sender (the player's own thread, or the global thread for the console). Once shutdown has started, no result is delivered. Candidates are scanned with world.getEntities() across every world plus the PDC isManaged marker, so mobs in reloaded chunks are neither undercounted nor missed

Permission nodes ​

emakimobs.use gates the whole command: without it the command is not usable (canUse fails) and no subcommand runs. The remaining nodes are checked per subcommand, each reporting a missing-permission message

PermissionDefaultDescription
emakimobs.usetrue (all players)Base permission to use the /emakimobs command
emakimobs.spawnopManually spawn custom mobs
emakimobs.reloadopReload configuration files
emakimobs.listopList registered mob definitions
emakimobs.infoopInspect a single mob definition
emakimobs.countopCount managed mobs; also gates find
emakimobs.editopOpen the in-game definition editor
emakimobs.debugopModule debug subcommand
emakimobs.adminopAdministration; used by kill (including kill all) and tp

Tab completion filters subcommands by your permissions and completes mob_id for spawn / info / kill / count / find, online player names for spawn, the radius for find / kill, and the page number for list

Examples ​

# Spawn an elite zombie at your own location
/emakimobs spawn elite_zombie

# Spawn a bone lord at player Steve's location
/emakimobs spawn bone_lord Steve

# Paginate through the registered mob definitions
/emakimobs list 1

# Inspect the bone lord definition
/emakimobs info bone_lord

# Count living elite zombies
/emakimobs count elite_zombie

# Remove elite zombies within 32 blocks
/emakimobs kill elite_zombie 32

# Remove all managed mobs within 64 blocks
/emakimobs kill all 64

# Remove every managed mob in every world
/emakimobs kill all

# Find elite zombies nearby and click to teleport
/emakimobs find elite_zombie 48

# Reload all config files
/emakimobs reload

CAUTION

The spawn command places the mob at the exact coordinates of the target player. Test in open areas to prevent mobs from becoming stuck inside blocks