Skip to content

Walk back Dispatcher #3322

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
2 of 5 tasks
mdbeng opened this issue Feb 4, 2025 · 1 comment
Closed
2 of 5 tasks

Walk back Dispatcher #3322

mdbeng opened this issue Feb 4, 2025 · 1 comment
Labels
Priority: High Represent a high impact in key areas of the base/user experience Stale No activity Status: Pending Test This PR or Issue requires more testing Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.

Comments

@mdbeng
Copy link
Contributor

mdbeng commented Feb 4, 2025 •
edited by murilo09
Loading

Priority

High

Area

  • Datapack
  • Source
  • Map
  • Other

What happened?

When 2 or more players are not reachable by the creature they get stuck in a loop where they are checking for target multiple times and they dont walk back or dance step properly because they are in this loop, how to reproduce this? trap 2 characters or more and you can see their behavior changing, i would just do it with 1 character first then with 2 so we can spot the difference on the dispatcher event.

Image

also i tested this in windows / linux with multiple scenarios and places. They have the same behavior mentioned above.

What OS are you seeing the problem on?

Linux

Code of Conduct

  • I agree to follow this project's Code of Conduct
@mdbeng mdbeng added the Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. label Feb 4, 2025
@github-actions github-actions bot added Priority: High Represent a high impact in key areas of the base/user experience Status: Pending Test This PR or Issue requires more testing labels Feb 4, 2025
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented May 8, 2025

This issue is stale because it has been open 120 days with no activity.

@github-actions github-actions bot added the Stale No activity label May 8, 2025
@mdbeng mdbeng closed this as completed May 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Priority: High Represent a high impact in key areas of the base/user experience Stale No activity Status: Pending Test This PR or Issue requires more testing Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mdbeng