• You've discovered RedGuides, an EverQuest multi-boxing and scripting community 🧙‍♀️⚙️. We want you to play several EQ characters at once, come join us and say hello! 👋

  • A TLP without truebox has thawed (Very Vanilla ready)
    Frostreaver

Auto Macros **Old 2017 THREAD**

Status
Not open for further replies.
Re: Auto Macros **MEGA THREAD**

You can either run AutoCleric or KissAssist (not both). From my experience, you get much faster healing and rezzing on AutoCleric and that is important for pet tanking. AutoCleric is also much simpler to get up and running. Kissassist offers far greater flexibility on how you configure your healer. Kissassist also just added conditional spells. Not sure how that will affect healing performance. I have not had a chance to play around with the conditional settings on any class.

Thanks for the reply, I had wondered because the commands were marked as Kiss compatible. Confused me I guess. :) I tried both last night. Autocleric worked great at healing, no complaints. The kissassist worked as well but I need to tweak it as the cleric was a healing beast, ran out of mana really fast.
 
Re: Auto Macros **MEGA THREAD**

still curious how to get autocleric to cast single target RNK 3 on everyone.

I've looked at this and its a major code addition for this feature. The reason is when you cast a group buff... you just cast it once on yourself. When you do single target it gets to be a bit trickier tracking the buffs and if they are up. I've finished coding the next release, and this just didn't make the cut this time, but a lot of the prelimanary ground work was added.
 
Re: Auto Macros **MEGA THREAD**

Any forecast on when the May release will be available? :-) Looking to get the aliases working again.

Thanks!
 
Re: Auto Macros **MEGA THREAD**

Any forecast on when the May release will be available? :-) Looking to get the aliases working again.

Thanks!

I'm about to take a few days off work, the coding is done, about to test and should have it up shortly thereafter.
 
Re: Auto Macros **MEGA THREAD**

Hey Noob,

I'm on the dropbox, and it seems to state that there's a newer autobard.mac up there for testing (newer than the April release). What's the latest one up there?
 
Re: Auto Macros **MEGA THREAD**

Hey Noob,

I'm on the dropbox, and it seems to state that there's a newer autobard.mac up there for testing (newer than the April release). What's the latest one up there?

2.3 v1 is the next Autobard and it will be dropping very very soon, shooting for tonight. As soon as I put the kids down, I'm going to finish my QA on it, and put it on Dropbox. I'm heading out on Vacation this Sunday and will get an updated version done before then. Thank you all for the patience.
 
Re: Auto Macros **MEGA THREAD**

auto war fixed yet? the mez thing annoyed me enough to go back to ka where it doesnt grab agro on all mobs as they come in
 
Re: Auto Macros **MEGA THREAD**

auto war fixed yet? the mez thing annoyed me enough to go back to ka where it doesnt grab agro on all mobs as they come in

Thank you for the reminder, I am adding this to the release. I redid the engaging and named prioritization, but will also add that the warrior will break mez when not engaged and mobs in camp.
 
Re: Auto Macros **MEGA THREAD**

Ok, all those issues should be addressed now and Preliminary Quality Assurance is done and uploaded to Dropbox. Let me know if you all see any issues.
 
Re: Auto Macros **MEGA THREAD**

Lol, and I downloaded them earlier so I'll have to grab them again!


Sent from my iPad using Tapatalk
 
Re: Auto Macros **MEGA THREAD**

question: my cleric wont res other toons in raid, only the ones he in group with, can that be fixed?
 
Re: Auto Macros **MEGA THREAD**

Hello. I am looking to make autocleric stop casting Aura of the Zealot over and over and over again. How can I disable this spell?
 
Re: Auto Macros **MEGA THREAD**

Mr. Noobhaxor sir, i have a warrior that follows my druid around and beats things up for him, and autowarrior works wonderfully for that

i have noticed though, when he is on /chaseon, and we are fighthing things, i might reppsition my druid a bit, and often i get more than 20-25 feet from the warrior, he will try and run to me, facing me and runs to me, then turns back to fight the monsters, then runs to me, turns back etc.

i was wondeirng if its possible to get a fix where his leash might either be turned off during combat or maybe set at 75 or even 100, and if so have a 2nd command to call him to us, then reengange the enemy when he is within 15, instead of the turning and running back and turning and running back.

is if combat, stop leash

if called, pause combat, and move to 20feet from caller, then continue combat.

new bind could be /frontandcenter!
 
Re: Auto Macros **MEGA THREAD**

Love the autowarrior mac but can I make some suggestions?
You have shield break / shield topple to only fire when the warrior is below 70% hp, it isn't a defensive skill its our largest burst damage in EOK, ought to be firing constantly by default I think
Pain Doesn't Hurt is set to fire only when we drop below 30% hp, maybe a better bet to make it fire at that threshold or when theres > 3 or 4 mobs in camp - since it shaves 4500+ off each incoming hit its most effective in multi mob tanking.
Theres a weird type of rapid fire tab targetting that seems to be happening in the current zip file build sometimes (especially when a named comes into camp with 1-2 regular mobs already in camp - it seems to lose its sense of priorities fighting everything at once.
It never uses rampage/banestrike at all. Rampage I can understand for fear of mezz breaks but maybe a way to toggle it on?
Warlord's Fury would be a great self buff for it to maintain at beginning of combat , flat 25% increase to all aggro that lasts for a few minutes, and is a short cooldown.

Other than that its pretty solid - I editted the code to reproduce some of those effects, have it doing around 80-90k DPS but would be nice to see standard
 
Re: Auto Macros **MEGA THREAD**

Mr. Noobhaxor sir, i have a warrior that follows my druid around and beats things up for him, and autowarrior works wonderfully for that

i have noticed though, when he is on /chaseon, and we are fighthing things, i might reppsition my druid a bit, and often i get more than 20-25 feet from the warrior, he will try and run to me, facing me and runs to me, then turns back to fight the monsters, then runs to me, turns back etc.

i was wondeirng if its possible to get a fix where his leash might either be turned off during combat or maybe set at 75 or even 100, and if so have a 2nd command to call him to us, then reengange the enemy when he is within 15, instead of the turning and running back and turning and running back.

is if combat, stop leash

if called, pause combat, and move to 20feet from caller, then continue combat.

new bind could be /frontandcenter!

Thank you for the report, I've successfully replicated this and it will be fixed in next update.

Love the autowarrior mac but can I make some suggestions?
You have shield break / shield topple to only fire when the warrior is below 70% hp, it isn't a defensive skill its our largest burst damage in EOK, ought to be firing constantly by default I think
Pain Doesn't Hurt is set to fire only when we drop below 30% hp, maybe a better bet to make it fire at that threshold or when theres > 3 or 4 mobs in camp - since it shaves 4500+ off each incoming hit its most effective in multi mob tanking.
Theres a weird type of rapid fire tab targetting that seems to be happening in the current zip file build sometimes (especially when a named comes into camp with 1-2 regular mobs already in camp - it seems to lose its sense of priorities fighting everything at once.
It never uses rampage/banestrike at all. Rampage I can understand for fear of mezz breaks but maybe a way to toggle it on?
Warlord's Fury would be a great self buff for it to maintain at beginning of combat , flat 25% increase to all aggro that lasts for a few minutes, and is a short cooldown.

Other than that its pretty solid - I editted the code to reproduce some of those effects, have it doing around 80-90k DPS but would be nice to see standard

Shield Break, actually does have a defensive recourse effect on top of the slashing bonus (1: Mitigate Melee Damage by 40%, 29145 total)
Pain doesn't hurt - I'll add this condition as that makes a lot of sense.
Tab targeting - I'm going to add a delay to target switching, so you don't see the rapid fire switching. (This was part of the named prioritization update)
Warlord's Fury - I honestly never even used this ability. I'll make sure its added on next update.

Thank you so much for the suggestions, I have nevered Main'd a warrior and just created one early this year because EoK wasn't merc friendly at all. So any suggestions on how to play a warrior are welcomed ;)
 
Re: Auto Macros **MEGA THREAD**

Shield topple line is why my warrior is outparsing the wizard still lol. I did a 2 hour preliminary parse after the warrior 2hander nerf, and im still seeing about 89k dps from war, granted the parse wasn't long enough. Before the nerf, warrior sustained was 98k dps, after nerf seems to be 88k dps although my parse just wasn't long enough.

No durational offensive discs on both parses.

Making sure you spam shield topple is critical, hope it doesn't get nerfed. With Breather, you should be able to spam it forever.
 
Re: Auto Macros **MEGA THREAD**

Thanks for fixing the tank targeting in 3.3. My downshit curing is working again. Appreciate the new version work!
 
Re: Auto Macros **MEGA THREAD**

Thank you for the report, I've successfully replicated this and it will be fixed in next update.



Shield Break, actually does have a defensive recourse effect on top of the slashing bonus (1: Mitigate Melee Damage by 40%, 29145 total)
Pain doesn't hurt - I'll add this condition as that makes a lot of sense.
Tab targeting - I'm going to add a delay to target switching, so you don't see the rapid fire switching. (This was part of the named prioritization update)
Warlord's Fury - I honestly never even used this ability. I'll make sure its added on next update.

Thank you so much for the suggestions, I have nevered Main'd a warrior and just created one early this year because EoK wasn't merc friendly at all. So any suggestions on how to play a warrior are welcomed ;)

Np's I main a warrior as my guild's MT and pretty much the only character I play right now.

A couple other easy changes I don't see in your code would be :
Maintain Blade Guardian as a buff (AA that increases parry rate automatically if your health dips too low, lasts as long as brace for impact does)
Add Resplendent Glory (AA)triggering when you use Warlord's Tenacity - since increasing your HP pool makes sense to increase healing received by 15% - lasts roughly same time as Warlord's Tenacity
Ditto for Hold the Line - does same thing can be used in any Last Stand worthy scenario.
Add the Insult disc as standard rotation since its our only other "brace" against damage just like Shield Break, and is cheap to use 3: Absorb Melee Damage: 50%, Total: 9028 ----Generates nearly 11k Hate at rank 2 --melee range
Currently never uses Warlord's Bravery AA - reduces incoming dmg by around 15-18% per swing for 40-50 swings, sub 10 minute refresh, can stack that in with Tenacity if you like.
Doesn't use AA Taunt - Ageless Enemity which should take priority over say Cyclone Roar and Tormenting Shout since it 1) Locks a target to you regardless of how far ahead someone is on aggro+generates hate 2) Is 0 endurance to use
So I would write the logic something like try Blast of anger, try ageless enemity, try warlords grasp, then start using our endurance based taunts.

I'd put a reasonable health threshold to trigger Fortitude disc at as well currently it looks like its setup just to blow fort if 3 or more mobs are in camp or a named - which might not be needed which also creates a bit of a problem since you're also stacking in Flash of Anger (parry all frontal attacks and Dicho which is a flat HP increase by 25% and reduces some incoming dmg and boosts aggro)

You end up with a weird overlap where you're both parrying all frontal attacks, having NPC's have a 100% miss rate on you anyways, and gaining 25% hp while you can't even be hit for 2-4 ticks (12-24seconds) anyways. So a lot of those discs are going to waste. Some kinda logic to stagger them would be ideal.

Even so your aggro pickup logic is insanely fast and pretty reliable, I've helped people level a few alts now where I told them its their job to pull and I would just wreck trains of mobs pretty much. Really well done with some more optimizations should make it much more survivable and hopefully sip alittle less endurance/healer mana

PS: Shield Break is a must have as long as theres endurance for it! (220k-470k hits and DOUBLE HITS for the same dmg so far I've recorded with it)
PSS: Still maybe some love for rampage? :D
 
Re: Auto Macros **MEGA THREAD**

Yeah, but you'll need to wait till the next patch as it interrupts melody atm, but when they patch it, it won't anymore!
 
Re: Auto Macros **MEGA THREAD**

Oh wow that looks fantastic, So you can twist like 6 songs with that?

Yup, I think some would argue seven if you don't mind some dropping periodically. Right now it routinely messes with melody/twist, but since autobard doesn't use those abilities it might be okay. And in any case, some of those melody/twist issues are being corrected on test right now and being pushed to live during next regular patch.
 
Re: Auto Macros **MEGA THREAD**

Yup, I think some would argue seven if you don't mind some dropping periodically. Right now it routinely messes with melody/twist, but since autobard doesn't use those abilities it might be okay. And in any case, some of those melody/twist issues are being corrected on test right now and being pushed to live during next regular patch.

Well I need to log back in and get my ass back to farming this piece. It sounds fantastic. In my experience, when they mess up melody it works even better with /cast (no artificial delays) I remember exploiting this for the drunk cure song.
 
Re: Auto Macros **MEGA THREAD**

The bard sword is really the newest "must have" bard clicky I've seen in a really long time. I'd argue the last one was the Songblade (or the newer one who's name I forget... lol... 30 min clicky haste + attack buff).
 
Re: Auto Macros **MEGA THREAD**

i dont know if its just me.. and it probably is.

i use the autowar macro alot, basically my main tank, and its excellent at that, sometimes though, i need it not to tank, but just to smack thigns up as a dpsing warrior, i know thats not the best scenario for a warrior, but sometimes things just work out that way.

what i would like to see is a toggle or a switch /tank or some sort
that toggles between tank aggro mode, and just sstraight up dps mode.

i have no clue hw to play warrior, i am just letting auto bot run it so thats why i think that would be neat.
 
Re: Auto Macros **MEGA THREAD**

I've looked at this and its a major code addition for this feature. The reason is when you cast a group buff... you just cast it once on yourself. When you do single target it gets to be a bit trickier tracking the buffs and if they are up. I've finished coding the next release, and this just didn't make the cut this time, but a lot of the prelimanary ground work was added.
It's the same with the next higher level single target buff I assume. At least on the tank it would be great to have.

- - - Updated - - -

Autocleric doesn't react to /chasedistance. It always keps the same distance.
 
Re: Auto Macros **MEGA THREAD**

Having an issue with autowarrior, I'm driving the tank and pulling with him. The issue is when fighting near an npc the tank keeps switching targets to the npc to try and attack them. I tried putting the mobs on the kiss ignore list but it doesn't work.
 
Re: Auto Macros **MEGA THREAD**

It's the same with the next higher level single target buff I assume. At least on the tank it would be great to have.

- - - Updated - - -

Autocleric doesn't react to /chasedistance. It always keps the same distance.

That's because it doesn't use chase.

I asked noobhaxor about this, this was his reply
The chase functionality works fundamentally different than KissAssist, even though it's the same command. My version uses a plugin called MQ2AdvPath which in turn uses the command /afollow from it. This actually creates a path behind the toon your are chasing so you can do this in tunnels, cliffs, etc. and the toon should follow perfectly. In the past most macros used stick which always followed the toons in a direct line. This one doesn't do that. It tries to follow the path at 20 units and currently can't be adjusted.


After finding this out, I've since started using afollow myself. Works well,your characters follow your path precisely rather than going from current position to yours in a straight line (means yor characters won't get caught on stuff) just need to make a in game macro with this :
/Bca //target assistname
/bca //afollow
/pause 5, /bct clericname //mac
AutoCleric.mac
/bct bardname //mac AutoBard.mac

Basically tells all your characters to use afollow to follow your assist, including the cleric/bard
Waits half a second then will start the auto macros for the bard/cleric.
 
Re: Auto Macros **MEGA THREAD**

Having an issue with autowarrior, I'm driving the tank and pulling with him. The issue is when fighting near an npc the tank keeps switching targets to the npc to try and attack them. I tried putting the mobs on the kiss ignore list but it doesn't work.

I don't have an ignore list, as I don't support afk killing. That said, the warrior should only engage those on XTarget, unless the mob get aggro'd from an AE, such as Area Taunt or Rampage.
 
Re: Auto Macros **MEGA THREAD**

I don't have an ignore list, as I don't support afk killing. That said, the warrior should only engage those on XTarget, unless the mob get aggro'd from an AE, such as Area Taunt or Rampage.

hmm strange then cause they are actually un-attackable quest npc's and they are not populating on the Xtarget window at all. If it was using kiss I would say they are within the camp radius so it's trying to agro them. Maybe because I have mq2melee active as well and need to unload it?
 
Re: Auto Macros **MEGA THREAD**

hmm

reading the previous post

do we need to turn off mq2melee for any of the macros? or is it used? id prefer to have it off so i know there is one thing fighting and not 2.
 
Re: Auto Macros **MEGA THREAD**

I always recommend turning it off, just to make sure that it doesn't have any conflicting conditions. Holyshits/Downshits can easily conflict with what the macros do, as it should utilize all your skills by default.

Turn off melee to test: (MQ2Melee Command)
Rich (BB code):
/melee off
 
Re: Auto Macros **MEGA THREAD**

cool thanks mr noobhaxor sir captain awesome pants!

- - - Updated - - -

the problem other have noticed when figthing near quests npc or mercharnts, like in argath i have noticed a couple times too now, specially one incident i remembered, in a dungeon where my autobot tank would target a named on another level in another area.


Rich (BB code):
/if (${badaggro}==0&&${Spawn[Named npc radius 100].ID}&&${Spawn[Named npc radius 100].ID}!=${Target.ID}&&!${Target.Named}) {
	/varset autotargetid ${Spawn[Named npc radius 100].ID}

i believe this is the culprit.un

it picks up a named, which alot of quest npcs, traders, bankers etc count as since thats the way mq2 check for named and they get fed into the checkaggro sub.

for testing the thing go to the relocated aliens in argath, there is a small ramp down to a named mechanic, not a proper named but he just has named, and another mechanic also pickedup.

fight on or near that ramp by pulling a buncha relocated aliens and you will see the problem.


is there anyway of checkin of the named being on our xtarget list before setting him as autotarget?

like for i 1 to xtarget if named.id equal xtarget varset autotargetid.

- - - Updated - - -

Rich (BB code):
 else /if (${badaggro}==0&&${Spawn[Named npc radius 100].ID}&&${Spawn[Named npc radius 100].ID}!=${Target.ID}&&!${Target.Named}) {
	/for i 1 to ${Me.XTarget}
		/if (${Me.XTarget[${i}].ID} == ${Spawn[Named npc radius 100].ID}) {
		/varset autotargetid ${Spawn[Named npc radius 100].ID}
		}
	/next i		}

tested out this code, initial test seemed to work near mabus in the valley. so gonna run with that for a bit and let oyu know what happens.

aight i am confident as such this work, dont know yet how it will work with an actual named on xtarget but it should work.

- - - Updated - - -

tested with a named 2 other mobs that wandered past and got suckered into fighting me, worked like intended.
 
Re: Auto Macros **MEGA THREAD**

cool thanks mr noobhaxor sir captain awesome pants!

- - - Updated - - -

the problem other have noticed when figthing near quests npc or mercharnts, like in argath i have noticed a couple times too now, specially one incident i remembered, in a dungeon where my autobot tank would target a named on another level in another area.


Rich (BB code):
/if (${badaggro}==0&&${Spawn[Named npc radius 100].ID}&&${Spawn[Named npc radius 100].ID}!=${Target.ID}&&!${Target.Named}) {
	/varset autotargetid ${Spawn[Named npc radius 100].ID}

i believe this is the culprit.un

it picks up a named, which alot of quest npcs, traders, bankers etc count as since thats the way mq2 check for named and they get fed into the checkaggro sub.

for testing the thing go to the relocated aliens in argath, there is a small ramp down to a named mechanic, not a proper named but he just has named, and another mechanic also pickedup.

fight on or near that ramp by pulling a buncha relocated aliens and you will see the problem.


is there anyway of checkin of the named being on our xtarget list before setting him as autotarget?

like for i 1 to xtarget if named.id equal xtarget varset autotargetid.

- - - Updated - - -

Rich (BB code):
 else /if (${badaggro}==0&&${Spawn[Named npc radius 100].ID}&&${Spawn[Named npc radius 100].ID}!=${Target.ID}&&!${Target.Named}) {
	/for i 1 to ${Me.XTarget}
		/if (${Me.XTarget[${i}].ID} == ${Spawn[Named npc radius 100].ID}) {
		/varset autotargetid ${Spawn[Named npc radius 100].ID}
		}
	/next i		}

tested out this code, initial test seemed to work near mabus in the valley. so gonna run with that for a bit and let oyu know what happens.

aight i am confident as such this work, dont know yet how it will work with an actual named on xtarget but it should work.

- - - Updated - - -

tested with a named 2 other mobs that wandered past and got suckered into fighting me, worked like intended.


Great spot! I'll incorporate this in the macro. I already do an XTarget call for checking aggro, I missed the check when I did named prioritization. Thanks for pointing this out.
 
Re: Auto Macros **MEGA THREAD**

Great spot! I'll incorporate this in the macro. I already do an XTarget call for checking aggro, I missed the check when I did named prioritization. Thanks for pointing this out.

Yep that was it. Put the new code in and working without a hitch. Thanks kaen01 and Noobhaxor
 
Re: Auto Macros **MEGA THREAD**

mr noobhaxor sir, when you get the chance could you take a look at the togglevariable sub i believe its not working as intended, as i cant camphere or returntocamp etc.


Rich (BB code):
        /if (${Defined[${Command}]}) {
            /declare OnOff local
            /if (${Command2.NotEqual[NULL]}) {

                /if (${Select[${Command2},0,off]}) {
                    /varset ${Command} 0
                    /varset OnOff Off
                } else /if (${Select[${Command2},1,on]}) {
                    /varset ${Command} 1
                    /varset OnOff On
                }
|this is what kissassist had (${${Command}}) this is what autosubs had(${Command2.NotEqual[0]}) works with the kissassist thing, but not with the autosubs one.
            } else /if (${${Command}}) {
                /varset ${Command} 0
                /varset OnOff Off
            } else 
                /varset ${Command} 1
                /varset OnOff On
            }
 
Re: Auto Macros **MEGA THREAD**

mr noobhaxor sir, when you get the chance could you take a look at the togglevariable sub i believe its not working as intended, as i cant camphere or returntocamp etc.


Rich (BB code):
        /if (${Defined[${Command}]}) {
            /declare OnOff local
            /if (${Command2.NotEqual[NULL]}) {

                /if (${Select[${Command2},0,off]}) {
                    /varset ${Command} 0
                    /varset OnOff Off
                } else /if (${Select[${Command2},1,on]}) {
                    /varset ${Command} 1
                    /varset OnOff On
                }
|this is what kissassist had (${${Command}}) this is what autosubs had(${Command2.NotEqual[0]}) works with the kissassist thing, but not with the autosubs one.
            } else /if (${${Command}}) {
                /varset ${Command} 0
                /varset OnOff Off
            } else 
                /varset ${Command} 1
                /varset OnOff On
            }
I'm seeing this as well. I'll recode this, it was taking the commands from Kiss. I'll trim this down and make it work properly.
 
implement /chasedistance

Please add the /chasedistance command for KA compatibility. In some places the right chasedistance makes all the difference between ok following and getting stuck almost everywhere.
 
Auto Macros **Old 2017 THREAD**
Status
Not open for further replies.

Users who are viewing this thread

Back
Top
Cart