rogue.mac - AutoRogue v. 2.0l 5-1-2004

Cunning · Post by **Cunning** » Sun May 02, 2004 9:56 pm

No it still goofs up when mobs are walled. I never figured out a good fix for that. I made some slight tweaks to getbehind a couple revs ago so it wasn't so jerky (expecially when a mob was being kited, you'd face back and forth missing the mob a lot).

MikeDVB · Post by **MikeDVB** » Tue May 04, 2004 2:46 am

I guess you could have it try to get behind for like 3 seconds, and if it can't make it settle for being beside. You can get beside any walled mob just not behind.

And have it try periodically

or if it detects it's walled have it reduce the distance to target to like 3 or something, so unless it's perfectly walled it will still fight. But just for that 1 fight

Cunning · Post by **Cunning** » Tue May 04, 2004 1:18 pm

The problem is getting a consensus. Is it better to keep attacking the mob if getbehind fails or not? Well, that all depends on the mob of course. Some riposte a lot harder than others... Also, when should the check happen to try using getbehind again? On a new fight? During the fight at a certain HpPct?

My thought is that if a mob is walled I'm going to fail out the getbehind calls for that mob (i.e. I'm not going to call getbehind anymore till that thing is dead). If you want I will implement that. Let's get a consensus.

Wink- · Post by **Wink-** » Tue May 04, 2004 1:56 pm

My thought on the walled mobs issue would be to have it stop trying to get behind after a certain point and just attack in range and try to get behind after a certain time intervals, say 5 seconds. Since the rogue stops fighting if his health is low anyways this might help out a ton for non raid mobs.

ucfusion · Post by **ucfusion** » Wed May 05, 2004 3:09 am

nope i still run into walls... i just have to be careful where i use it... PoE is perfect for this script and i can literally let it run for hours...

crisdan · Post by **crisdan** » Wed May 05, 2004 9:52 am

Maybe you could just add a passable parameter that would turn getbehind off (i.e. a flag that when you start the macro) so when you actually start the macro you could stop this as being an issue. For example hunting in nadox the other night, the walls were everywhere so just being able to turn this feature off would have been perfect.

stm69 · Post by **stm69** » Thu May 06, 2004 12:54 pm

Imho cunning, any dps is better than none, ripos aside. That and the rogue running into the wall looks kinda stupid/suspicious to other people watching. I'd personally prefer the rogue continue frontal attacks when a mob is walled, until mob is dead.

illus1on · Post by **illus1on** » Fri May 07, 2004 11:08 pm

Had a quick question...

When the macro zones, maybe it's just my client.... However, when zoning the macro ends, of corse. But what I noticed is that my Deadly Precision discipline was greyed out and not available for 47 Minutes? It's a 5 min disc.

Smitty · Post by **Smitty** » Sat May 08, 2004 1:34 am

what might have happened is it used one of the other discs on that same timer.. forgot which timer that is but it might be duelist timer.

So I would check to see what discs were used.

123456ix · Post by **123456ix** » Sat May 08, 2004 2:42 pm

Great macro, thanks for making it! One thing that i noticed when i was 3 boxing war, cleric, rogue. Is that if the tank died the rogue would return to the anchor point or person to follow. Is there a toggle or is it possible to have him continue attacking?

Blazza · Post by **Blazza** » Wed May 12, 2004 11:19 am

Just wondering, before I go an do something that has already been done, anybody fix the running into walls problems yet? a sort of breakout where we finaly give up on geting behind mob for x ammount of time if it fails over and over?

Cunning · Post by **Cunning** » Thu May 13, 2004 12:14 pm

It's being worked.

ucfusion · Post by **ucfusion** » Thu May 13, 2004 2:18 pm

real quick question if anyone had had there macro break with the latest installment of MQ2... I may have missed the memo somewhere so please be kind. But my rogue macro is breaking at the define for enrage at the begining it seems... It works for my friend though that converted it for a monk.

ucfusion · Post by **ucfusion** » Thu May 13, 2004 3:32 pm

ok ill flame my own ass on this one didnt even notice the announcement on the top of the page... /bonkself

But I still dont understand how to change the macro to make it work... You been able to fix it Cunning ?

SimpleMynd_01 · Post by **SimpleMynd_01** » Thu May 13, 2004 3:37 pm

A quick ghetto fix is just to add #*# at the beginning and end of each event.

Code: Select all

#Event Enraged "has become ENRAGED"

become...

Code: Select all

#Event Enraged "#*#has become ENRAGED#*#"

That should get ya up and running again.

-SimpleMynd

rogue.mac - AutoRogue v. 2.0l 5-1-2004

Update