Klumpat / e3-macro-builds

Automatically exported from code.google.com/p/e3-macro-builds
0 stars 0 forks source link

Swap doesn't work, Feral Swipe/Bestial Alignment #37

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
So, I downloaded the latest version of the E3.mac.

My shadowknight can't use his Cloak of Icy Shadows clicky:

Self Buff#1=Cloak of Icy Shadows/item
Self Buff#2=Irestone Band of Rage/item
Self Buff#3=Cloak of Retribution/item
Self Buff#4=Cloak of Luclin/gem8
Self Buff#5=Black Shroud/gem8
Self Buff#6=Call of Darkness/gem8
Self Buff#7=Banshee Aura/gem8

All the other self buffs work. I tried the cloak in several places (ie, Self 
Buff#1, 5, 7, etcetera). My bard can use his Cloak of Icy Shadows. When I 
remove the /item from the Cloak of Icy Shadows, the macro can successfully 
identify the Cloak of Icy Shadows as an item. Also, it seems that putting the 
Cloak of Icy Shadows anywhere in the list stops the later self-buffs from 
occurring. 

My Shadowknight also can't seem to get the swap feature working
Buff=Ancient Prismatic Lance/mainhand
Twohander=Diamond-Tipped War Javelin/mainhand
Shield=Bloodstone Sword/mainhand,Blackstone Buckler/Offhand

and hotkeys;
/swap Buff
/swap Twohander
/swap Shield

The error message is Error: Ini entry: [Buff] was not found.

Had the same swap problem on all my characters.

My Beastlord has bestial alignment and fera swipe in the alt section:
[Abilities]
Ability#1=Kick/ability
Ability#2=Feral Swipe/alt
Ability#3=Bestial Alignment/alt

I get the error:
ERROR: @[Ability#2] - I do not have ranks in [Feral Swipe]. Flagging 
[Ability#2] as BAD_ENTRY.

The interesting thing is if I leave the /alt out, it figures out to identify 
the feral swipe/bestial alignment as AA's, and tells me I have spent AA's on 
them...at which point it decides I haven't spent AA's on them :P This error 
occurs for Bestial Alignment as well.

Also, the donate link included in the macro (http://goo.gl/BhnWv) doesn't work.

I miss you K-dog.

-Mike

Original issue reported on code.google.com by Michael....@gmail.com on 22 Feb 2013 at 9:30

GoogleCodeExporter commented 8 years ago
These should all be fixed in v5.0 and later.  Please let me know if there are 
any more issues.

Original comment by iKillpeq@gmail.com on 29 Jul 2013 at 8:22