Changelog - Version 1.1.8

Release Summary

This release fixes important Spawn Marker behavior around tamed mobs and combat leash.

The main goals are:

• prevent tamed/retyped marker mobs from being controlled by the marker forever
• stop marker time-condition cleanup from deleting mobs after they are tamed
• make marker leash less disruptive during combat
• preserve the normal marker leash configuration outside combat

Fixes

Marker mobs now release tracking when tamed or retyped

Spawn Marker mobs now follow the same safety rule used by region-spawned mobs: if the NPC role name no longer matches the entity id stored in the tracker, the marker tracker is removed from that mob.

Practical impact:

• tamed marker mobs no longer teleport back to the marker
• tamed marker mobs no longer count against marker capacity
• tamed marker mobs are ignored by marker reconciliation
• tamed marker mobs are no longer removed when their original time/weather condition expires

This is especially important for markers that spawn tameable mobs, because ownership or role changes should transfer the mob out of the marker runtime system.

Marker leash now respects combat

Marker leash teleport now detects combat using the same LockedTarget check used by region containment.

New behavior:

• outside combat, marker mobs use the configured leash radius as before
• during combat, marker mobs are only teleported back after reaching a fixed 48 block distance
• marker teleport has a 3 second cooldown per mob

Practical impact:

• mobs can move farther while actively fighting
• combat feels less abrupt around markers
• the normal marker leash setting remains unchanged for non-combat behavior

Internal Notes

• 64 remains the marker reconciliation scan radius only.
• The marker leash maximum configured through the UI remains 32.
• Combat leash is intentionally fixed at 48 blocks and does not scale with marker configuration.
• Marker tracker cleanup mirrors the existing region tracker cleanup concept, but is applied in the marker runtime path because markers use MarkerTrackerComponent.

Compatibility

• Data compatibility: fully compatible with 1.1.7
• Migration required: no
• New config fields: none
• Existing markers keep their current leash, spawn, and activation settings

Version: 1.1.8