Pathfinder

[1.1.0] - 2026-02-19

Added

• PathfinderMarkerStorage – In-memory storage for pathfinder markers per player per world. Replaces the removed PlayerWorldData.getWorldMapMarkers() / setWorldMapMarkers() API. Uses entity ref index as the player key so it is safe to call from both the World thread (when adding/clearing markers) and the WorldMap thread (when the map provider runs).
• PathfinderMarkerFactory – Builds MapMarker instances for the current Hytale API, using Message.raw(name).getFormattedMessage() for the marker name field.

Changed

• Hytale API compatibility (latest release)
  • MarkerProvider – Implemented new update(World, Player, MarkersCollector) signature; pathfinder markers are read from storage and added via the collector.
  • MapMarker – No longer uses the old 5-argument constructor; markers are created via the no-arg constructor with field assignment and the correct FormattedMessage for the name.
  • Marker visibility – Pathfinder markers now use MarkersCollector.addIgnoreViewDistance() so far-away biome markers still show on the map and compass (same behavior as the old “unlimited visibility” path).
• PathfinderMarkerStorage.playerKey(Player) – Uses only Ref.getIndex() (no Store access) so it can be used from the WorldMap thread without triggering Hytale’s thread-affinity assertion. Previously used deprecated Entity.getUuid() and then UUIDComponent via the store, which is not allowed off the World thread.
• PathfinderCommand, PathfinderSearchService, PathfinderBiomeSearchPage – All marker add/clear/list logic now uses PathfinderMarkerStorage and PathfinderMarkerFactory instead of PlayerWorldData and the old MapMarker constructor.

Fixed

• FormattedMessage – Resolved ClassCastException when creating markers (e.g. from the biome map GUI). Message is not a FormattedMessage; the code now uses Message.raw(name).getFormattedMessage() to obtain the protocol type.
• Far-away biome markers – Markers for biomes found at large distances were not shown because MarkersCollector.add() only sends markers within chunk view distance. Pathfinder now uses addIgnoreViewDistance() for its markers so they always appear.

Note

• Pathfinder markers are stored in memory only and do not persist across server restarts.