immortail

protect your tamed (furry) friends from dying (in minecraft). tested only on paper 1.21.11.

video demo

immortail-demo.mp4

Note

made this for personal use because no good options existed for permission-based tamed mob protection. i don't know java that well, this is whim work :3

how it works

grant a player immortail.protect and their tamed mobs become truly invulnerable. revoke it and protection drops on the next sync cycle (every 5s).

• two protection modes, switchable at runtime:
  • invulnerable (default) - truly unkillable, blocks all damage including /kill
  • resistance - uses resistance 5 potion effect, /kill and void still work
• configurable aggression control - prevent protected mobs from griefing players
• per-player aggression overrides via LuckPerms permissions
• mob registry persists across chunk unloads and restarts
• instant protection on chunk load (no delay)
• tracks protected mobs via persistent data containers so it won't interfere with other plugins

commands

all commands require immortail.admin (default: op).

command	description
/immortail	help
/immortail list	all protected/unprotected mobs by type
/immortail list <player>	a player's mobs + permission status
/immortail info	plugin status, build, update status, mode, aggro settings, mob counts
/immortail mode [invulnerable|resistance]	view or change protection mode
/immortail aggro	view global aggression settings
/immortail aggro <setting> <true|false>	change an aggression setting
/immortail aggro <player>	view a player's effective aggression (global + perm overrides)
/immortail pets <player>	list a player's mobs with names, UUIDs, status
/immortail defuse	immediately calm all angry protected mobs
/immortail prune	drop stale tracked-mob records (dead worlds, offline-deleted mobs)
/immortail reload	re-read config + force re-sync all mobs

permissions

permission	description	default
immortail.protect	protect all tamed mob types for this player/group	false
immortail.protect.<type>	protect a specific mob type only (e.g. immortail.protect.wolf)	false
immortail.admin	access to /immortail commands	op
immortail.aggro.pvp	this player's mobs can target/damage players (overrides config)	false
immortail.aggro.tamed	this player's mobs can target/damage other tamed mobs	false
immortail.aggro.pve	this player's mobs can target/damage hostile mobs	false

all permissions work with both players and groups via LuckPerms.

quick setup

protect all tamed mobs for everyone:

/lp group default permission set immortail.protect true

protect all tamed mobs for a specific player:

/lp user marcwl permission set immortail.protect true

protect only wolves for a group:

/lp group vip permission set immortail.protect.wolf true

mob type filtering

by default, immortail.protect covers all tamed mob types. you can restrict which types are protected server-wide via config:

# config.yml

# empty = all types protected (default)
protected-types: []

# or restrict to specific types
protected-types: [wolf, cat, parrot]

when protected-types is set, immortail.protect only covers those types. players/groups can still get additional types via immortail.protect.<type> permissions.

aggression settings

by default, protected mobs cannot attack players or other tamed mobs (anti-grief), but can still fight hostile mobs.

# config.yml
aggression:
  allow-pvp: false              # can protected mobs attack players?
  allow-tamed: false            # can protected mobs attack other tamed mobs?
  allow-pve: true               # can protected mobs attack hostile mobs?
  allow-mob-retaliation: true   # can hostile mobs target protected mobs?

per-player/group overrides via LuckPerms:

/lp group pvp permission set immortail.aggro.pvp true
/lp user marcwl permission set immortail.aggro.pvp true

update checking

on startup (and every 6h) immortail checks github for newer versions and surfaces the result in /immortail info. admins are notified on join if you're behind.

it compares two ways, so it works whether you run a tagged release or a build straight off main:

• release tag - your version vs the latest github release (dromzeh/immortail)
• commit - the commit your jar was built from vs the latest commit on main, so it'll tell you you're behind even when there's no new release tag yet

the build commit is baked into the jar at build time (git rev-parse); a build with no git info, or one whose commit isn't pushed, just shows what it can. disable all outbound requests with:

# config.yml
check-for-updates: false

Note

the jar version is derived from git automatically (git describe) - there's nothing to hand-bump. release builds sitting on a v* tag use the tag (v1.2.0 -> 1.2.0); other builds use the nearest tag plus commits-ahead (1.2.0-5-gabc1234), and fall back to the commit comparison. just push a v* tag to cut a release.

supported mobs

anything that implements bukkit's Tameable interface (wolves, cats, parrots, horses, donkeys, mules, llamas, camels, etc.) plus foxes via the trust system. arctic foxes are included under the fox type.

happy ghasts (1.21.6+) are supported while harnessed. they have no vanilla owner, so whoever equips the harness (or first interacts with an already-harnessed, unclaimed one - e.g. dispenser-equipped) counts as the owner for the permission model; shearing the harness off ends ownership. the type for immortail.protect.<type> and protected-types is happy_ghast.

building

requires java 21.

./gradlew build

jar outputs to build/libs/immortail-v<version>.jar.

license

MIT