NobleSteeds release

Mount Duplication and Reliability Update

Prevents mount duplication with safer chunk-aware relocation, cleans up stale entities, fixes unloaded mount renaming, and improves calls, stables, storage, market, and auto-stable handling.

Free Release
Version
1.0.1
Published
September 29, 2026
Minecraft
1.18.2 - 1.21.11 / 26.1.x - 26.2.x
Java
Java 17+

Release Notes

Mount Duplication Fixes

  • Reworked relocation to find and teleport the existing mount entity instead of creating a replacement.
  • Added asynchronous loading for source and destination chunks.
  • Added chunk tickets and entity-loading retries while resolving mounts.
  • Prevented relocation when the original mount cannot be safely verified.
  • Added locking to prevent simultaneous relocation operations on the same mount.
  • Updated /ns call and the Call Mount management option.
  • Updated command and GUI stable teleportation.
  • Updated auto-stable on logout.
  • Updated mount storage and market handling.

Duplicate Cleanup

  • Added startup reconciliation for mounts in already-loaded chunks.
  • Confirmed stale duplicate entities are removed automatically.
  • Active mounts have their saved names and tracking data restored.
  • Stored or market-listed mounts found physically spawned are removed.
  • Ambiguous entities are preserved and reported instead of being deleted unsafely.
  • Unloaded mounts are checked when their chunks load.

Mount Renaming

  • Fixed renaming mounts located in unloaded chunks.
  • Saved names are applied when mounts are loaded.
  • Mount names are synchronized during startup and entity loading.

Configuration Changes

  • horse-management.summon-cooldown-seconds now defaults to 0.
  • The summon cooldown is optional and is no longer required for duplicate protection.
  • horse-management.auto-stable.enabled now defaults to false.
  • Auto-stable operations remain queued one mount at a time.
  • horse-management.auto-stable.queue-delay-ticks remains available to reduce back-to-back chunk activity.

Upgrade Information

No data migration is required when upgrading.

1. Stop the Minecraft server completely.
2. Back up your worlds and plugin data directory.
3. Replace the previous jar with the updated jar.
4. Start the server normally.
5. Do not use /reload.

Existing YAML, SQLite, and MySQL data remains compatible with this release.