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
Core/Battleground: Removed _CheckSafePositions, this is handled by areatriggers now. #14570
Conversation
65398f7
to
fe250f3
Compare
👍 |
fe250f3
to
27e0f75
Compare
I see https://github.com/TrinityCore/TrinityCore/pull/14570/files#diff-2d7bc8b5f9669823a0062232320c5d19L313 has been removed, where is it handled in the new code ? |
It's not handled in the new code, I can do it if you want, but I didn't feel like it should, cause on retail it is easy to leave those areatriggers (well, it's easy in Twin Peaks horde or the other one with pandaren mine, goblin mine...). So if you want me to use it, I would like to remove the "(possible expoit)" part :p |
ef14a12
to
3203e3e
Compare
@Golrag: is this PR finished? |
@Carbenium haven't looked at this PR for a long time. Will take a look at it asap |
The title should contain a short description after "Core/Battleground:", something like |
@Golrag Can you bring back the old _CheckSafePositions() checks, but keep the area triggers you've added? While area triggers are more accurate and cleanly handled, there needs to be some sort of fallback because they are also very easily exploitable (e.g. all one would have to do is prevent the client from sending the CMSG_AREATRIGGER opcode and they would never get teleported back, which is easier than it sounds). |
@Takenbacon mh, the purpose of this PR is to replace the current implementation with a more blizzlike one. But tbh, I don't know what happens on retail when you get out of the starting zone without triggering CMSG_AREATRIGGER |
This branch has conflicts that must be resolved |
3203e3e
to
49d487b
Compare
Woops, will have to re-create everything |
Removed _CheckSafePositions, this is handled by areatriggers now.
Any feedback is welcome ! :)
About the areatriggers for starting areas, should I move them to Battleground::HandleAreatrigger or handle them in the specific battlegroundclass ? (Like BattlegroundTP::HandleAreatrigger)
Edit: Updated to 007ab5b
Added missing alterac valley areatriggers
Removed m_StartMaxDist