rogue.mac - AutoRogue v. 2.0j *New Parm Rdy* (4/25/2004)

Cunning · Post by **Cunning** » Fri Apr 16, 2004 12:50 pm

I left some test code in there that was preventing attack and causing that null message you were getting. I updated the code on the first message. Please try it out and let me know if you see any problems.

Though it doesn't look like much changed in the version number, a lot changed in the code implementation. Before, the following sample code snippet would work:

Code: Select all

/sendkey down up
/delay 10
/sendkey down up

This would continue to press the up key. However:

Code: Select all

/keypress up hold | same as /sendkey down up, presses/holds up key
/delay 10
/keypress up hold

Would only press up for one second. The subsequent call to /keypress up hold actually turns off the first /keypress up hold. If you remember the movement code in 1.9 you'll see why this is an issue. I think I've routed out the bugs associated with this but I need some help testing.

Thanks.

dam1337 · Post by **dam1337** » Fri Apr 16, 2004 2:24 pm

seems like newest release is crashing after the wait loop right as the attack loop goes in.. not quite sure what is causing it but can varify it crashed 4 times in a row.

ucfusion · Post by **ucfusion** » Fri Apr 16, 2004 2:40 pm

yep its crashed twice in a row for me too... right as it goes to attack... it also seems very slow going through the loop. It takes a couple of seconds for it to realize that a target has been selected...

anyone notice this happening with other macros...

Cunning · Post by **Cunning** » Fri Apr 16, 2004 5:30 pm

What is the crash message?

dam1337 · Post by **dam1337** » Fri Apr 16, 2004 5:39 pm

crashes EQ to desktop... not getting error in game.. completely crashes entire game upon attack loop

ml2517 · Post by **ml2517** » Fri Apr 16, 2004 6:15 pm

Guys, as stated elsewhere:

Try to A: turn #turbo down. If that doesn't work try B: Put /delay 1 in each of the major loops. Personally I prefer B:

Cunning · Post by **Cunning** » Fri Apr 16, 2004 6:23 pm

MacroQuest was updated yesterday (4/15) due to a crash bug that was found (this was a day after the patchday MacroQuest came out on 4/14). It also corrected the issues with /keypress (which I use extensively now since /sendkey is being depreciated). Do you have the newest version? Check the download's section and make sure.

I was running my debug rogue.mac yesterday evening without a crash using the newest version of MacroQuest. It was entering the attack loop and echoing what it was supposed to be doing (backstab/evade/disc usage) w/o actually doing it. I did forget to change a couple of things back when I moved the debug code to production, expecially this:

Code: Select all

... |Echos in the beginning of :Attack
/varset attacktarget 0 | If this isn't set to 1, you won't do shit to the mob except getbehind
...
/goto :AttackLoop

In any event, make sure you have a new copy of my rogue.mac code AND a fresh copy of MacroQuest. If you're still having trouble let me know.

I plan to get this macro fixed 100% this weekend. Thanks for all the feedback and support.

Ahroun · Post by **Ahroun** » Fri Apr 16, 2004 6:56 pm

Cunning check your in box

Cunning · Post by **Cunning** » Fri Apr 16, 2004 7:00 pm

Ahroun check my reply =)

ucfusion · Post by **ucfusion** » Fri Apr 16, 2004 8:13 pm

downloaded latest mq2 still crashed when i ran the autorogue 2.0b

zertful · Post by **zertful** » Fri Apr 16, 2004 8:29 pm

Nice work on this very useful macro Cunning. I'm using a modified version of this script for my beastlord. Is there a way to have the autobehind code detect walls without running face first into a wall if a mob has it's back to the wall, or simply a way to turn off autobehind? I've tried setting the global variable from the console but it doesn't make a difference.

Any plans on modularizing this script for classes other than rogue? I would be happy to contribute!

Thanks,

Zert

Cunning · Post by **Cunning** » Fri Apr 16, 2004 8:29 pm

Bleh...

I can't log in right now to test...

I did remove some legacy variables that are no longer used. There was a /varset to a non-existent array dimension that was null (which should have caused problems before) that was removed.

Grab the new macro code and try it out if you can guys. You might also try turning the #turbo value down. If it doesn't work I will fix this tonight when I'm able to log in (trying to diagnose this from work is a pita).

Cunning · Post by **Cunning** » Sat Apr 17, 2004 3:18 am

Tested the new 2.0c tonight with no visible issues. I need to have it tested somewhere like PoFire tables so I can see how the kiting works. In static camps it seems to be working fine. Let me know if you see anything weird.

Thanks.

Cunning · Post by **Cunning** » Sun Apr 18, 2004 3:40 am

2.0e is out. Sooooo much nicer...

Aside from the bug fixes (I got to test it in a kiting situation, which helped debug a lot of stuff) you can now set @strikedisc to 0 in the custom.inc if you don't want to use it. I also added collision detection when moving to a mob (before the attack loop).

As always, let me know if you have any questions/comments/bugs to report/etc.

Thanks.

Smitty · Post by **Smitty** » Mon Apr 19, 2004 2:19 pm

cunning I sent you a PM..

rogue.mac - AutoRogue v. 2.0j New Parm Rdy (4/25/2004)

Check your MQ version and grab a new copy of my code.