Made BuildAndSendReportToIngameGameMasters use the LANG_ANTICHEAT_TELEPORT and LANG_ANTICHEAT_IGNORECONTROL chatbox alerts when the report type are teleport or ignore control respectively. This ensure that every teleport alerts shows what was the coordinates diffs.
Remove a duplicate teleport alert.
Remove a duplicate ignore control alert.
Remove a duplicate Z-Axis alert.
Issues Addressed:
Closes none. I wanted to always have the coordinates differences whenever someone got detected from teleports.
SOURCE:
Tests Performed:
Doing .mod speed 50 and running in a straight line without GM mode will wrongly trigger the teleport detection.
How to Test the Changes:
1.
Known 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:
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.
Changes Proposed:
BuildAndSendReportToIngameGameMasters
use theLANG_ANTICHEAT_TELEPORT
andLANG_ANTICHEAT_IGNORECONTROL
chatbox alerts when the report type are teleport or ignore control respectively. This ensure that every teleport alerts shows what was the coordinates diffs.Issues Addressed:
SOURCE:
Tests Performed:
.mod speed 50
and running in a straight line without GM mode will wrongly trigger the teleport detection.How to Test the Changes:
1.
Known 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.