-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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(Scripts/ScarletMonastery): improvement ScarletMonastery #17558
base: master
Are you sure you want to change the base?
fix(Scripts/ScarletMonastery): improvement ScarletMonastery #17558
Conversation
I really can't find where there are extra spaces 😒😒😒😒😒😒 |
src/server/scripts/EasternKingdoms/ScarletMonastery/instance_scarlet_monastery.cpp
Outdated
Show resolved
Hide resolved
src/server/scripts/EasternKingdoms/ScarletMonastery/instance_scarlet_monastery.cpp
Outdated
Show resolved
Hide resolved
… library's creatures friendly
Do not use range search to change factions
src/server/scripts/EasternKingdoms/ScarletMonastery/instance_scarlet_monastery.cpp
Outdated
Show resolved
Hide resolved
src/server/scripts/EasternKingdoms/ScarletMonastery/instance_scarlet_monastery.cpp
Outdated
Show resolved
Hide resolved
src/server/scripts/EasternKingdoms/ScarletMonastery/instance_scarlet_monastery.cpp
Outdated
Show resolved
Hide resolved
src/server/scripts/EasternKingdoms/ScarletMonastery/instance_scarlet_monastery.cpp
Outdated
Show resolved
Hide resolved
src/server/scripts/EasternKingdoms/ScarletMonastery/instance_scarlet_monastery.cpp
Outdated
Show resolved
Hide resolved
??I'm cleaning up a branch that has been merged. Too many branches in TortoiseGit
i can't see which ones have been merged
获取Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: sudlud ***@***.***>
Sent: Monday, April 1, 2024 9:33:09 PM
To: azerothcore/azerothcore-wotlk ***@***.***>
Cc: daobashun ***@***.***>; State change ***@***.***>
Subject: Re: [azerothcore/azerothcore-wotlk] fix(Scripts/ScarletMonastery): improvement ScarletMonastery (PR #17558)
Why did you close all your PRs?
―
Reply to this email directly, view it on GitHub<#17558 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALXKHRYKQYU7NXSXVNUCEU3Y3FOZLAVCNFSM6AAAAAA6KS22BSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRZG43DMMJUGU>.
You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|
Ah ok because you deleted 4 branches of PRs that were not merged yet |
…to Scarlet_Monastery_improvement
@fangshun2004 this looks fun to test.
|
Can you please address the codestyle CI issues |
can you please respond to the last comment of @alecsci, also there are merge conflicts to be resolved if the PR is ready to be tested |
…to Scarlet_Monastery_improvement # Conflicts: # src/server/scripts/EasternKingdoms/ScarletMonastery/instance_scarlet_monastery.cpp
…04/azerothcore-wotlk into Scarlet_Monastery_improvement
It's been fixed in #15218, as described at the beginning Go there and see what's fixed I don't want to type in a whole bunch of text |
Hi @fangshun2004,
These proposed fixes looks like are part of the existing master changes. Can you please update the PR description to what you actually propose to improve with this PR ? |
Does this still need to be tested. If yes, what or how does it need to tested. |
Hi @TheSCREWEDSoftware, I suggest to test it again, but we have to clarify the proposed changes. @fangshun2004 can you please can edit the PR description to tell us what you exactly want to fix, so we know what to test. There aren't that many changes, so I don't expect a wall of text ? I make a lot of assumptions in my previous test #17558 (comment) |
If only next to Mograine's corpse would reduce Whitemane's health to less than 50%. The difference is not discerning. The difference can only be seen by pulling Whitemane far away from the corpse All emoji in creature_text are now 0, and there is emoji data in the analyzed conversation data. And there's also a lack of dialogue to shout at the player to welcome. So I'm going to revise creature_text.
|
To put it simply, it's a matter of adding some details. The player is hypnotized and will have to wait some time to release the resurrection. The player is not hypnotized and will soon be unleashed resurrection. After resurrection, there should be some small interactions between bosses |
@fangshun2004 confirm if what's on the video here is the expected result of this PR |
Sorry, I can't access everything on YouTube😥😥 |
Can you elaborate?
|
Changes Proposed:
4 . Added the emote(salute) of Whitemane's creature after resurrecting Mograine(growl).
5. After resurrecting Mograine, Whitemayne dies, the player quits the fight or dies, and Mograine does not respawn Pick up Mograine's items without a shot
Out of combat should be respawning rather than waiting for the mob to move back to the spawn point
6. Whitemane's HOLY_SMITE spells should be cast at ranged (not moving) whenever possible, and will only attempt to move to melee range if the spell is unusable (behind a building, etc.).
7. Whitemane has less than 50% HP and is released DEEP_SLEEP after the spell should be moved to Mograine's side before using Resurrection (if the player does not have a DEEP_SLEEP debuff after moving to Mograine, the resurrection will be released immediately, and if there is a debuff, it will wait for 5 seconds before it is released)
8. When Mograine has dot damage and triggers the first death, the dot damage number can still appear on Mograine, and does not remove all Aura
This PR proposes changes to:
Issues Addressed:
Corrupted Ashbringer effect seems inconsistent. #14478
SOURCE:
The changes have been validated through:
#15218
Tests Performed:
This PR has been:
How to Test the Changes:
Tests Ashbringer
.additem 22691
..level 60
or.character level 60
..additem 22691
..instance unbind all
..tele smcath
.Test combat
.level 80
or.character level 80
.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.