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.

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(CORE/OPvP): Halaa Mechanics not working properly #15634

Merged
merged 37 commits into from
Jan 14, 2024

Conversation

Valdifer
Copy link
Contributor

@Valdifer Valdifer commented Mar 28, 2023

Halaa mechanics are not working like blizzlike

Closes #14355
Closes chromiecraft/chromiecraft#4642

Co-authored-by: Gultask
Author: Valdifer

Changes Proposed:

  • Rework of Halaa

Issues Addressed:

SOURCE:

Tests Performed:

How to Test the Changes:

  1. .tele halaa
  2. capture it Horde/Alliance
  3. change to opposite faction
  4. try to capture it with guards alive
  5. use roosts
  6. throw a bomb to the guards
  7. kill guards until none is alive
  8. try capture it
  9. kill a player in the area named Halaa to get a mark
  10. kill a player in the area not named Halaa

Known Issues and TODO List:

  • Bombs leave a DOT to guards
  • Alliance Halaa guards shouldn't be ghost model id
  • Halaa message warning no guards
  • Halaa capturable only when there is 0 guards and max points by the Controller Team
  • All dead players can spawn in Halaa when it should be by the Controller Team (Happens only when server is restarted)
  • Guards patrolling waypoints
  • Flags players when interact with Roosts
  • Capture area has to be more small (Not anymore due i don't remember how it was in Vanilla)
  • Halaa mark should be obtained in all Halaa Area

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.

Halaa mechanics are not working like blizzlike

Closes azerothcore#14355
Closes chromiecraft/chromiecraft#4642

Co-authored-by: Gultask
Author: Valdifer
@yehonal-bot yehonal-bot added CORE Related to the core DB related to the SQL database file-cpp Used to trigger the matrix build Script labels Mar 28, 2023
@Valdifer
Copy link
Contributor Author

Valdifer commented Apr 14, 2023

Right now it is working without bugs and AIs are ok

@Valdifer
Copy link
Contributor Author

Valdifer commented Apr 17, 2023

Ok, i found the error of display ID:
image
What should be there? I suppose that should be 18254 but don't know, i'm going to check trinity and mangos DB

@Kitzunu
Copy link
Member

Kitzunu commented Apr 17, 2023

That is sniffed
@Gultask u have any sniffs of it?

@heyitsbench
Copy link
Contributor

Might be the parser or maybe an incomplete sniff, but here's what I could find in a 45854 packet:

(18254, 1, 1.5, 0, 0),
(18255, 1.20000004768371582, 1.80000007152557373, 0, 0),
(18256, 1, 1.5, 1, 0),
(18257, 1, 1.5, 1, 0),

@Gultask
Copy link
Contributor

Gultask commented Apr 17, 2023

Cmangos has it at 0

@Valdifer
Copy link
Contributor Author

Valdifer commented Apr 17, 2023

OregonCore and TrinityCore has the same values as AC (As expected)

EDIT: Well, if we use that sniffed data, we don't get anymore the ghost guard

@Valdifer
Copy link
Contributor Author

I need someone test it and tell me what need to change, it has been done since the last update

@Nyeriah
Copy link
Member

Nyeriah commented Dec 3, 2023

#include CreatureScript.h

@Valdifer
Copy link
Contributor Author

Valdifer commented Dec 3, 2023

#include CreatureScript.h

I deleted because i thought it wasn't necessary :/, older version didn't had it, prolly something changed in an update, well adding it again and lets see

@Valdifer
Copy link
Contributor Author

Anyone? D:

@FrancescoBorzi
Copy link
Contributor

@azerothcore/developers please have a look at this

@Valdifer apologies for the delay and thanks for contributing

@Valdifer
Copy link
Contributor Author

@azerothcore/developers please have a look at this

@Valdifer apologies for the delay and thanks for contributing

Thanks you guys for support me and teach me new things :), i will try to do my best, if something required a review tell me

@elthehablo
Copy link
Contributor

Will test this this weekend

Copy link
Member

@Kitzunu Kitzunu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have made pretty generic reviews, and not pointed out every occurence of things. Go through the entire file and check for issues I mention in my review. Also check https://www.azerothcore.org/wiki/cpp-code-standards

It's way better than the first draft though.

src/server/scripts/OutdoorPvP/OutdoorPvPNA.cpp Outdated Show resolved Hide resolved
src/server/scripts/OutdoorPvP/OutdoorPvPNA.cpp Outdated Show resolved Hide resolved
src/server/scripts/OutdoorPvP/OutdoorPvPNA.cpp Outdated Show resolved Hide resolved
src/server/scripts/OutdoorPvP/OutdoorPvPNA.cpp Outdated Show resolved Hide resolved
src/server/scripts/OutdoorPvP/OutdoorPvPNA.cpp Outdated Show resolved Hide resolved
src/server/scripts/OutdoorPvP/OutdoorPvPNA.h Outdated Show resolved Hide resolved
@Kitzunu
Copy link
Member

Kitzunu commented Jan 3, 2024

@elthehablo how testing going

@elthehablo
Copy link
Contributor

elthehablo commented Jan 3, 2024

Did some tests:

  • Message about Halaa being defenseless seems to work
  • Token is now also obtained outside

However:

  • Upon capturing guards remaining goes to 15/15, then immediately to 0/15 with the message Halaa being defenseless being thrown

This might be an issue from my side, I will check again to ensure I compiled correctly. I don't think it is because the rest is working fine

This means I wasn't able to test the following yet:

  • DOT staying on guards
  • Halaa being capturable when guards are up

@Valdifer
Copy link
Contributor Author

Valdifer commented Jan 5, 2024

Did some tests:

  • Message about Halaa being defenseless seems to work
  • Token is now also obtained outside

However:

  • Upon capturing guards remaining goes to 15/15, then immediately to 0/15 with the message Halaa being defenseless being thrown

This might be an issue from my side, I will check again to ensure I compiled correctly. I don't think it is because the rest is working fine

This means I wasn't able to test the following yet:

  • DOT staying on guards
  • Halaa being capturable when guards are up

For me its working:
image

But thanks to you i found an error when u interact with the roost :)

EDIT: Ok i took a look into the Roosts and the problem is when u have only 6 stacks of bomb (or 7 or 8)
image
you get a message You can't transport more of that item
image

As far i saw is related with PlayerStorage.cpp::CanStoreItem Line 1129

EDIT2: But before this was getting controlled by OPvPCapturePointNA::HandleCustomSpell

@@ -1239,6 +1239,7 @@ enum AcoreStrings
LANG_OPVP_NA_CAPTURE_A = 10026,
LANG_OPVP_NA_LOSE_H = 10027,
LANG_OPVP_NA_LOSE_A = 10028,
LANG_OPVP_NA_DEFENSELESS = 10074,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Surely these aren't necessary? They do exist in broadcast_text.

@Nyeriah Nyeriah dismissed stale reviews from Kitzunu and Nefertumm January 14, 2024 17:00

stale

@Nyeriah Nyeriah merged commit 2c7c3b6 into azerothcore:master Jan 14, 2024
13 checks passed
sudlud added a commit to sudlud/azerothcore-wotlk that referenced this pull request Jan 19, 2024
- follow-up to PR azerothcore#18170 to fix the remaining guid conflicts of PR azerothcore#15634
@sudlud
Copy link
Member

sudlud commented Jan 19, 2024

This PR features pure delete-by-GUID sql statements that would usually never get merged, but it seems that the CI doesn't care.

Merging this PR as-is resulted in GUID conflicts from which half almost went unnoticed.

Can we please try not to repeat something like this - it just hurts to get the own work overwritten like this and then only partially fixed.

@Kitzunu
Copy link
Member

Kitzunu commented Jan 19, 2024

CI can't catch that particular case. But with enough RegEx we could probably improve it.

@sudlud
Copy link
Member

sudlud commented Jan 19, 2024

CI can't catch that particular case. But with enough RegEx we could probably improve it.

At least the CI would have failed if the DELETE-statements would have included the "AND ID IN (...)" condition as the GUIDs were already taken with other IDs, or would it still have passed

Nyeriah pushed a commit that referenced this pull request Jan 20, 2024
- follow-up to PR #18170 to fix the remaining guid conflicts of PR #15634
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CORE Related to the core DB related to the SQL database file-cpp Used to trigger the matrix build Ready to be Reviewed Script Waiting to be Tested
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Halaa Battle Token Range Halaa Battle Token Range Halaa mechanics not working properly Halaa Issues