- Joined
- Aug 26, 2015
- RedCents
- 420¢
Ran into a new issue with the latest MQ2 Compile.
Previously I had no issue with the following working:
After the latest patch and a few compiles I started getting the following error:
Removed the .Length from the argument and got the following error after /melee load:
Checked the Mothership's Wiki page for me.aura
Changed my Down to the following, replacing .Length with .ID:
Did another /melee load and finally no more error msg. Clicked my aura off and MQ2Melee cast my Aura without issue and no further error once loaded.
For what its worth I believe I remember something about this from the past, however it does not make sense for why the .Length was still working for me on this Down until now.
If anyone else is having this same issue, I'm hoping this will help them understand why it's happening and how to fix it.
Regards,
~TheFiddler~
Previously I had no issue with the following working:
Rich (BB code):
Downshit2=/if (${Spell[Champion's Aura].Stacks[1]} && !${Me.Aura[Champion's Aura].Length} && ${Me.PctEndurance}>2) /doability "Champion's Aura"
After the latest patch and a few compiles I started getting the following error:
No such 'auratype' member 'Length'
Removed the .Length from the argument and got the following error after /melee load:
The "non-numeric" being "Champion's Aura" since I took the .Length off the argument.Failed to parse /if condition '(TRUE && !Champion's Aura && 100>2)', non-numeric encountered
Checked the Mothership's Wiki page for me.aura
Changed my Down to the following, replacing .Length with .ID:
Rich (BB code):
Downshit2=/if (${Spell[Champion's Aura].Stacks[1]} && !${Me.Aura[Champion's Aura].ID} && ${Me.PctEndurance}>2) /doability "Champion's Aura"
Did another /melee load and finally no more error msg. Clicked my aura off and MQ2Melee cast my Aura without issue and no further error once loaded.
For what its worth I believe I remember something about this from the past, however it does not make sense for why the .Length was still working for me on this Down until now.
If anyone else is having this same issue, I'm hoping this will help them understand why it's happening and how to fix it.
Regards,
~TheFiddler~

