Bug Closed · Resolved

@NearestPlayer doesn't update to NearestPlayer ~onTimer

#5344 opened by Unknown 1 year ago

Unknownreported this bug

Summary

When I target @NearestPlayer with an ~onTimer trigger, it triggers to the nearest player (presumably) when the mob spawns in, and then never updates again after that. Steps to reproduce

  1. Get a friend

  2. Have friend sit next to mob sending a message to nearestplayer on timer and spawn it

  3. Have friend move further away from mob, it still targets initial player

Provide a full set of steps used to reproduce the bug, including links to SEPARATE Pastebin pastes for each relevant configuration file.

Current behavior

targets player (that was closest when mob was spawned) AFTER FURTHER TESTING, it doesnt even target the closest player when it spawns... so i dont know what its targeting. it still doesnt switch targets ever. (/ mobs first target) indefinity instead of switching to nearestplayer Intended correct behavior

should switch targets to nearest player Server log file

https://pastebin.com/rjDZHPUB

Debug log snippet

https://pastebin.com/TxPXvmUd

Proposed fixes

idk force mob to consider target change to nearestplayer each trigger

Unknowncommented

Closing due to inactivity and major version changes. Stop by our Discord support-chat channels for additional troubleshooting and to get community verification this is a plugin issue on modern versions; if this is still a relevant issue, please re-post with a modern-version server log and current steps to reproduce.

Sign in to join the discussion.