-
Notifications
You must be signed in to change notification settings - Fork 491
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
Spell groups and aura exclusivity #2117
base: development
Are you sure you want to change the base?
Spell groups and aura exclusivity #2117
Conversation
The tables were a total mess. 80% of the groups were duplicates, non-functional, or redundant from IsNoStackSpellDueToSpell Documented the changes https://docs.google.com/spreadsheets/d/1Yfx8n_GjYcdyMcj1qWO5Xbc9iLibdKemDxPqtmCvHjg/edit#gid=2142704053
Changed wotlk code to something that makes much more sense for vanilla. Removed some exclusivity rules that should have never been there.
Rejuvenation - rank 1 doesn't override rank 2 but no longer displays "A more powerful spell is active" message like it would without this commit. Same for Renew. I understand that vmangos spell bouncing is incomplete and its probably necessary to edit it this way. On classic a higher potency rejuvenation will give "A more powerful spell is active" if a player with inferior +healing tried to cast it for example. Just a minor thing from my testing. |
In classic is t based on rank or power? Will a rank 5 rejuvenation from a druid with 1000 healing power overwrite a rank 6 rejuvenation from a druid with 0 healing power or will it say "A more powerful spell is active" |
I haven't checked your commit but last time I went through spell groups, there were a few hidden gems like rank 3 int scroll stacking with mage buff which I assume was done on purpose to give someone unfair advantage. Not sure if you combed through the whole thing or just same-chain ranks |
I have tried to comb through everything and not miss even the obscure int buff from a quest in the barrens. |
Please correct me if I'm wrong but for me, this is no longer compatible with the server and causes errors if you run the migration. |
🍰 Pullrequest
Proof
Issues
How2Test
Todo / Checklist