-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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.
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
fix(MMAP/core/PathGenerator): Try to fix more water creatures #13705
fix(MMAP/core/PathGenerator): Try to fix more water creatures #13705
Conversation
You'll need to regenerate mmaps in order to get the fix. |
i'm going to mention this so there is no rush with people thinking this is some golden unicorn end all. |
I think that's the normal running animation |
If anyone can. Please try:
.go xyz -4051.062988 2796.326172 -2 1 .go xyz -94.3 -1116.1 35.1 0 |
|
Indeed, he's just running here. The water effect on his feet always appear until NPC is fully on land. |
Feels better than before |
…zerothcore#9990)" This reverts commit 66e6d33.
…set if player is just jumping in water or has waterwalk
9f543d9
to
4363d5e
Compare
I've been testing for quite a while now and everything I can think of is much better than what it was. No regressions that I can see. |
Removed blank space causing issues on CI |
when this will be merged? |
I have tested this edit and it is a huge improvement fixing murlocs across darkshore and westfall. |
What is the status on this? |
It's going to be merged after the holidays. |
I updated the MMAP version so the core will complain when old files are used |
Thank you very much for the amazing fix, @MikaMauger ! |
Yes its looking good so far :) |
…hcore#13705) Co-authored-by: jackpoz <giacomopoz@gmail.com>
This reverts commit 66e6d33.
Changes Proposed:
Issues Addressed:
Tests Performed:
If you want to see what happens in RecastDemo:
![Capture_decran_2022-11-01_233355](https://user-images.githubusercontent.com/21247853/200117447-b1dc7a81-7847-4d9c-b885-0321fbf4d462.png)
![Capture_decran_2022-11-01_233408](https://user-images.githubusercontent.com/21247853/200117449-36b1b6cd-b1f9-438d-b587-a845c605ab76.png)
How to Test the Changes:
.go xyz -9243.936523 -2453.144531 56.821400
and do range attacks on murlocs from beach when they are in water.go xyz -9250.759766 -1182.086792 67.439095
and do range attacks on murlocs from beach when they are in waterKnown Issues and TODO List:
How to Test AzerothCore PRs
When a PR is ready to be tested, it will be marked as [WAITING TO BE TESTED].
You can help by testing PRs and writing your feedback here on the PR's page on GitHub. Follow the instructions here:
http://www.azerothcore.org/wiki/How-to-test-a-PR
REMEMBER: when testing a PR that changes something generic (i.e. a part of code that handles more than one specific thing), the tester should not only check that the PR does its job (e.g. fixing spell XXX) but especially check that the PR does not cause any regression (i.e. introducing new bugs).
For example: if a PR fixes spell X by changing a part of code that handles spells X, Y, and Z, we should not only test X, but we should test Y and Z as well.