conditions for common aura mechanics
bloerwald opened this issue · 2 comments
Not sure how feasible, but maybe one would like to have conditions for other states than weather as well, to avoid listing many auras in scripts. Drawback is that this list would be manually assembled and not available via API, thus needs per-patch updates. Relevant would be those with common mechanics most likely, here for 9.0.1.35213. Note that underground/flying abilities of course also have untargetable
.
BattlePetAbilityID | BattlePetStateLuaName |
---|---|
410 | Mechanic_IsBleeding |
491 | Mechanic_IsBleeding |
462 | Mechanic_IsBlind |
257 | Mechanic_IsBlind |
954 | Mechanic_IsBlind |
1014 | Mechanic_IsBlind |
1048 | Mechanic_IsBlind |
385 | Mechanic_IsBomb |
635 | Mechanic_IsBomb |
637 | Mechanic_IsBomb |
1071 | Mechanic_IsBomb |
1081 | Mechanic_IsBomb |
171 | Mechanic_IsBurning |
177 | Mechanic_IsBurning |
500 | Mechanic_IsBurning |
502 | Mechanic_IsBurning |
900 | Mechanic_IsBurning |
1042 | Mechanic_IsBurning |
1889 | Mechanic_IsBurning |
1918 | Mechanic_IsBurning |
546 | Mechanic_IsChilled |
721 | Mechanic_IsChilled |
415 | Mechanic_IsChilled |
785 | Mechanic_IsChilled |
787 | Mechanic_IsChilled |
848 | Mechanic_IsChilled |
205 | Mechanic_IsChilled |
341 | Mechanic_IsFlying |
737 | Mechanic_IsFlying |
322 | Mechanic_IsFlying |
839 | Mechanic_IsFlying |
852 | Mechanic_IsFlying |
2339 | Mechanic_IsFlying |
261 | Mechanic_IsInvisible |
822 | Mechanic_IsInvisible |
565 | Mechanic_IsInvisible |
294 | Mechanic_IsObject |
328 | Mechanic_IsObject |
329 | Mechanic_IsObject |
671 | Mechanic_IsObject |
711 | Mechanic_IsObject |
326 | Mechanic_IsObject |
480 | Mechanic_IsObject |
464 | Mechanic_IsObject |
434 | Mechanic_IsObject |
438 | Mechanic_IsObject |
443 | Mechanic_IsObject |
333 | Mechanic_IsObject |
747 | Mechanic_IsObject |
720 | Mechanic_IsObject |
810 | Mechanic_IsObject |
189 | Mechanic_IsObject |
819 | Mechanic_IsObject |
175 | Mechanic_IsObject |
635 | Mechanic_IsObject |
385 | Mechanic_IsObject |
332 | Mechanic_IsObject |
827 | Mechanic_IsObject |
1001 | Mechanic_IsObject |
1058 | Mechanic_IsObject |
1081 | Mechanic_IsObject |
1355 | Mechanic_IsObject |
2088 | Mechanic_IsObject |
2103 | Mechanic_IsObject |
2299 | Mechanic_IsObject |
151 | Mechanic_IsPoisoned |
271 | Mechanic_IsPoisoned |
358 | Mechanic_IsPoisoned |
379 | Mechanic_IsPoisoned |
397 | Mechanic_IsPoisoned |
633 | Mechanic_IsPoisoned |
368 | Mechanic_IsPoisoned |
664 | Mechanic_IsPoisoned |
781 | Mechanic_IsPoisoned |
1048 | Mechanic_IsPoisoned |
1961 | Mechanic_IsPoisoned |
2290 | Mechanic_IsPoisoned |
2350 | Mechanic_IsPoisoned |
734 | Mechanic_IsStunned |
174 | Mechanic_IsStunned |
927 | Mechanic_IsStunned |
1030 | Mechanic_IsStunned |
498 | Mechanic_IsStunned |
1348 | Mechanic_IsStunned |
1593 | Mechanic_IsStunned |
1671 | Mechanic_IsStunned |
2061 | Mechanic_IsStunned |
2211 | Mechanic_IsStunned |
331 | Mechanic_IsUnderground |
829 | Mechanic_IsUnderground |
830 | Mechanic_IsUnderground |
340 | Mechanic_IsUnderground |
565 | Mechanic_IsUnderground |
326 | Mechanic_IsWall |
480 | Mechanic_IsWall |
464 | Mechanic_IsWall |
434 | Mechanic_IsWall |
443 | Mechanic_IsWall |
381 | Mechanic_IsWebbed |
338 | Mechanic_IsWebbed |
924 | resilient |
284 | unkillable |
242 | unkillable |
725 | unkillable |
341 | untargettable |
737 | untargettable |
331 | untargettable |
261 | untargettable |
829 | untargettable |
830 | untargettable |
565 | untargettable |
340 | untargettable |
839 | untargettable |
852 | untargettable |
1358 | untargettable |
2339 | untargettable |
List is made by SELECT BattlePetAbilityID, LuaName AS BattlePetStateLuaName FROM BattlePetAbilityState, BattlePetState WHERE BattlePetAbilityState.BattlePetStateID = BattlePetState.ID AND (BattlePetState.LuaName LIKE "Mechanic_%" OR …)
(-equivalent in LibreOffice).
Sorry, that SQL is not actually what I ran. wow.tools/dbc allows you to download dbs as csv, which in this case I then joined as per that query to produce the table.
There are db2-to-sql converters iirc, but I don’t use them, so I can’t link or describe them, sorry. I can try to find a link for you if needed.
Either way, I’m not sure if this is a good idea: it does require quite frequent updates, and I doubt people really write that generic scripts. This was mostly a result of that weather issue and looking at other effects but weather.
Then again, this information is visible to the battle api at least, but I have not checked if you can get them from the UI api.