-
-
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
[WIP] CF Faction Assign & Leader Instance Faction #21118
base: master
Are you sure you want to change the base?
Conversation
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.
No way, too much repetitive code.
Make it a function and just call the function
Currently, |
There is again a lot of code repetition. I would recommend, like Kitzunu, to create function and call that instead. |
...er/scripts/Northrend/CrusadersColiseum/TrialOfTheChampion/instance_trial_of_the_champion.cpp
Outdated
Show resolved
Hide resolved
@@ -280,8 +285,13 @@ class instance_trial_of_the_champion : public InstanceMapScript | |||
{ | |||
if (TeamIdInInstance == TEAM_NEUTRAL) | |||
{ | |||
if (Player* gleader = ObjectAccessor::FindPlayer(player->GetGroup()->GetLeaderGUID())) | |||
TeamIdInInstance = Player::TeamIdForRace(gleader->getRace()); | |||
if (Group* group = player->GetGroup()) |
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.
Why are you not creating a function for that ?
WIP
Changes Proposed:
This PR proposes changes to:
Issues Addressed:
mod-cfpve not needed anymore
SOURCE:
The changes have been validated through:
Tests Performed:
This PR has been:
How to Test the Changes:
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.