Skip to content
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

SSC: Remove Boss-Requirements from Vashj (2.4.0) #721

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

insunaa
Copy link
Contributor

@insunaa insunaa commented Jan 14, 2025

🍰 Pullrequest

This PR removes the requirement to kill all bosses in SSC prior to attempting Lady Vashj, as per Patchnotes of 2.4.0

Proof

How2Test

  • Go to Lady Vashj's bridge console. Click on it immediately

Todo / Checklist

  • Maybe gate the "removal" behind PRENERF macro, to ensure both types of behaviour can be observed if desired.

@killerwife
Copy link
Contributor

PRENERF_2_3

@insunaa
Copy link
Contributor Author

insunaa commented Jan 14, 2025

Yeah, I know. I'll probably rework it as I said in ToDo

@insunaa insunaa marked this pull request as ready for review January 14, 2025 08:25
@cpevors
Copy link

cpevors commented Jan 14, 2025

Can confirm -- I have tested both the 2.4 and pre-2.4 behaviour. This commit seems to accomplish both, and the raid instance is working as intended.

@insunaa
Copy link
Contributor Author

insunaa commented Jan 14, 2025

Actually having just tested the bug report I couldn't actually reproduce it even without these fixes applied. Everything just worked. Some more investigation is needed, I'll return this to a draft PR.

Edit: It seems this commit added these flags that shouldn't be there: cmangos/tbc-db@b6797db#diff-cd31318aa943f6fee873d89faf5767814629694f399bc33627931c25ee8edcb6R996

@insunaa insunaa marked this pull request as draft January 14, 2025 13:12
@cpevors
Copy link

cpevors commented Jan 15, 2025

This commit did restore the correct behaviour. cmangos/tbc-db@8d940e4

@insunaa insunaa marked this pull request as ready for review January 15, 2025 07:25
@insunaa
Copy link
Contributor Author

insunaa commented Jan 15, 2025

The PR is still valid as it now also allows pre-2.4.0 behaviour if enabled. The appropriate flags still need to be investigated, as the flags applied by the DB change did include GO_FLAG_LOCKED for all objects involved, which we don't currently use in DB.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants