-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Add new hook OnPlayerQueueRandomDungeon() and revert (now unnecessary) PR #8196
Add new hook OnPlayerQueueRandomDungeon() and revert (now unnecessary) PR #8196
Conversation
@@ -841,6 +841,9 @@ class PlayerScript : public ScriptObject | |||
// Called when a player is added to battleground | |||
virtual void OnAddToBattleground(Player* /*player*/, Battleground* /*bg*/) { } | |||
|
|||
// Called when a player queues a Random Dungeon using the RDF (Random Dungeon Finder) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need new style info
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sorry I missed this, I'll address this in another PR
@nolt not sure if you noticed but in the module it mentions about the client limitation. Even though it displays the random tbc or wotlk dungeons, if you actually queue up it will only place you into the dungeons for the enabled expansion. I ran tests and queued up several times and looks to be working as expected. I only ever got put into a dungeon for the expansion that was enabled. |
Changes Proposed:
OnPlayerQueueRandomDungeon()
Tests Performed:
How to Test the Changes:
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.