Mount Collection

By
Mahghuuuls

Adds a personal mount collection with selection, recall, and configurable recovery after lethal damage.

Mount Collection adds a personal mount collection inspired by the mount system in World of Warcraft. Choose a mount in the collection screen, then recall it with a key press. With Recovery enabled, when an eligible mount would die, it enters Recovery instead, allowing you to recall it at full health after a configurable delay.

Built-in support covers vanilla mounts. Add-ons can support modded mounts through the provider API. Support is defined per mount type because being rideable, being tamed, and having an owner are different things: pigs, for example, can be ridden without having a native owner.

AI usage disclaimer: This mod was developed with AI-agent assistance using this agent workflow. The project owner reviewed the work during development.

Using the collection

With the default settings:

Ride an eligible mount and press H to register it. Horses, donkeys, mules, and llamas must be tamed and owned by you. Skeleton and zombie horses must be tamed and either owned by you or ownerless. Pigs can be registered while you ride them.
Assign Open Mount Collection in Controls; it is unbound by default. Browse your mounts, rotate their previews, rename them, and click Select to choose what H recalls. Highlighting a row does not change selection.
While not riding, press H to recall your Selected Mount. Recall needs a safe destination and has a configurable cooldown. You automatically ride the arriving mount when nearby placement and normal riding requirements allow it.
Confirm Abandon to remove a living mount from your collection without deleting the animal.

Registered living mounts remain in the world; the collection does not store them away.

Recovery protects eligible registered mounts from lethal damage. By default, wait five minutes of active server time, then recall the mount at full health with its equipment and inventory retained. It does not return automatically. Normal recall does not heal a living mount.

Configuration

Server settings are in config/mountcollection.cfg and also apply in singleplayer:

Registration and recall filters: Separate entity-ID blacklists or whitelists control which supported mount types can be registered and recalled. Both default to empty blacklists. Allowing an entity does not add support for it or bypass its eligibility requirements.
Destination dimensions: A blacklist or whitelist of numeric dimension IDs controls where mounts may be recalled. The default empty blacklist excludes no dimensions.
Recall cooldown: Defaults to 10 seconds of active server time. Set it to 0 to disable the cooldown.
Placement search: Configure the normal and fallback search radii around the player, defaulting to 4 and 8 blocks. Safe placement is still required.
Flying mounts: Optionally block recall of mounts that an add-on identifies as flying, including restoration from Recovery. This is off by default and does not prevent registration or collection management.
Recovery: Enable or disable lethal-damage protection and change the recovery time, which defaults to 300 seconds. A duration of 0 removes the wait, but you must still recall the mount. Duration changes apply to future Recovery events.
Inhibited integration: Enable or disable effect-based recall blocking when the optional integration is present. Enabled by default.
Diagnostics: Enable detailed diagnostic logging for troubleshooting. Disabled by default.

Client settings are in config/mountcollection-client.cfg:

Automatic riding: Automatically try to ride a recalled mount when placement and its native riding rules allow it. Enabled by default.
Boarding notices: Show a notice when recall succeeds but automatic riding cannot. Enabled by default; disabling it does not hide actual recall errors.

Restart the server or reopen the singleplayer world after changing server settings. Restart the client after changing client settings.

For add-on developers

The experimental provider API lets add-ons support additional mount types without changing Mount Collection itself. A provider can:

Define supported entities and their registration requirements, such as ownership, taming, age, or equipment.
Describe placement needs for solid ground, water, or lava, and identify flying mounts.
Supply native boarding checks and seat geometry for automatic riding, plus supported preparation behavior such as clearing a sitting pose.
Store bounded, versioned provider data with collection records and migrate that data when its format changes.
Opt into Recovery by capturing and restoring mount-specific state.
Add client-side previews using detached preview entities.

Mount Collection retains control of collection identity, recall, safe placement, cooldowns, persistence, and synchronization. Living-mount support does not automatically imply Recovery support, and arbitrary rideable entities are not supported without a provider.

The API is experimental and may change incompatibly. See the provider API documentation and examples for the registration contract and extension points.