View Full Version : AA Question
Midgett
08-14-2015, 03:09 PM
I have been evaluating the newer clients since the AA revamp. I noticed the max AA for my druid's Mastery of the Past has a different max AA going from Underfoot to RoF. 15-Underfoot, 21-RoF.
Where do you set your max rank for each AA now? I thought under the new system, it figured it up using the aa_ranks table. 
Is Altadv_vars still used in the new system, or is it more of a user reference for identifying AA ids?
Thanks!
demonstar55
08-14-2015, 05:12 PM
Max AA is calculated when your toon loads up (different per client)
No, it's mostly there for reference until it gets removed (ex. if you somehow missed the AA capture we can get the data from the old table still).
Midgett
08-16-2015, 03:28 AM
Thanks for the info! :)
I tried a little experiment to see if I understand the new AA schema. 
I took my druid's "Silent Casting" AA and tried moving it to a range not used in aa_ranks (60,000). I made the changes as follows:
aa_ability:
id-->494
name-->Silent Casting
first_rank_id-->1409
aa_ranks:
id                expansion           prev_id          next_id
1409                10                   -1              1410
1410                10                  1409             1411
1411                10                  1410             1412
1412                10                  1411             60000
60000               10                  1412              -1
So, the outcome should have been the same as leaving the 60000 as 1413. But when I go to train in the AA, the AA drops off the list as soon as it reaches the 4th rank.
I have broken rules I'm not aware of, obviously. 
Thanks for the help!
BTW...I'm using Underfoot.
Midgett
08-19-2015, 01:35 PM
Just wanted to post a follow up for anyone interested in Custom AAs.
The problem is I used a Rank ID greater than 49998. If you use Rank IDs higher, the max AA will be calculated correctly. The problem is the Rank
with the ID greater than 49998 will cause the AA to get dropped from the AA window once you reach it.
I've only tested this with UF and RoF. It appears to be a client limitation.
Earlier rules still apply, you have to modify dbstr_us.txt, and you have to be mindful of future AAs that get added to the DB.
Thanks, Demonstar55, for the earlier reply! :)
vBulletin® v3.8.11, Copyright ©2000-2025, vBulletin Solutions Inc.