Skip to content
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

[Bug]: Monster not following target #4865

Closed
4 tasks done
ArturKnopik opened this issue Dec 4, 2024 · 0 comments · Fixed by #4866 · May be fixed by #4867
Closed
4 tasks done

[Bug]: Monster not following target #4865

ArturKnopik opened this issue Dec 4, 2024 · 0 comments · Fixed by #4866 · May be fixed by #4867
Labels
bug An issue describing unexpected behavior of code priority: critical Issues with this label should be resolved as quickly as possible

Comments

@ArturKnopik
Copy link
Contributor

ArturKnopik commented Dec 4, 2024 •
edited
Loading

By submitting this bug issue, you agree to the following.

  • This is a bug in the software that resides in this repository, and not a support matter (use https://otland.net/forums/support.16/ for support)
  • This issue is reproducible without changes to the C++ code in this repository
  • This bug has not been resolved in master branch
  • There is no existing issue for this bug already

Does this bug crash tfs?

no

Server Version

1.7 (Master)

Operation System

Windows

OS Description

No response

Bug description

Monster not following target

Possible Pull Requests which are to blame

Probably this one: #4811

Steps to reproduce

  1. Enter to game world using normal character
  2. Find monster that attack(ex: cyclops)
  3. Watch monster behavior

Actual Behavior

Monster moving in random directions

Expected Behavior

Monster follow player

Backtrace

n/a
@ArturKnopik ArturKnopik added bug An issue describing unexpected behavior of code needs-confirmation not confirmed by a developer yet labels Dec 4, 2024
@github-project-automation github-project-automation bot moved this to Backlog in TFS 1.8 Dec 4, 2024
@ArturKnopik ArturKnopik mentioned this issue Dec 4, 2024
Merged
3 tasks
@ghost ghost linked a pull request Dec 5, 2024 that will close this issue
fix monster attack behavior #4866
Merged
3 tasks
@ramon-bernardo ramon-bernardo mentioned this issue Dec 7, 2024
Open
3 tasks
@ArturKnopik ArturKnopik added priority: critical Issues with this label should be resolved as quickly as possible and removed needs-confirmation not confirmed by a developer yet labels Dec 19, 2024
@github-project-automation github-project-automation bot moved this from Backlog to Done in TFS 1.8 Dec 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug An issue describing unexpected behavior of code priority: critical Issues with this label should be resolved as quickly as possible
Projects
TFS 1.8
Status: Done
Milestone
No milestone
1 participant
@ArturKnopik