So without degrading this wonderful conversation to "Management made the decision to release! Omg it's not the devs! They's wonderfuls!" that existed in EQ1.... when can we expect EQ2 hacks?

EQ2 is a steaming pile of poo that deserves any hacks.... sorry, just my opinion!

It makes you read instructions, and it makes other people ridecule you prior to performing the former.

Legion: Edit mq2main.cpp, edit the line that says

#define DBG_SPEW
to
// #define DBG_SPEW

Recompile. I believe this is still an occasional known issue, but it fixed that same problem for me.

Sure bob but even you have to admit "sn" as a "spells" command doesn't actually describe itself fully. I would admit also that I'd like to have some sort of descriptive as to what every command does without having to analyze the code.

All the following is much much smoother now. I would really have to work through it with a fine toothed comb to find significant flaw.

Just wanted to say again ... kudos!

All the recent || inserts fixed my loads. I imagine removing the spaces would as well, but this seems simpler.

Ditto. I can get beyond that by removing the versioning lines put on the top but then there's a problem with the include on the advpath.inc (checking versions and executing if the file exists, regardless if it is included)

No matter how good you are, no matter how good your script might or might not be, there is a difference between helping and being a total jackass. You're the kind of person who would advocate putting tacks on the ground, just to tell people that they should've been watching where they step. I don't ...

The yaulp thing is on by default, and it's a copy of the "other" genbot, so I don't blame your code at all. It's just a nuisance, something that really shouldn't be on by default. The logic is ... if you're a cleric, and if your mana is under 100, mem yaulp and use it. Well, that happens w...

Had a chance to test newest code (up to last post) on two separate machines. Very improved operation with find fast. Damn near flawless (see below, minor thing) Some occasional looping behaviour without find fast. I'm unclear on the + and - usage. It would seem that a parameter has been removed from...

Ok, I'll test out the actual movement parts on a speedier machine before I offer critique of it, I understand how that could screw up processing. I have been twoboxing on one machine lately, so I agree, it's most likely the problem. I would recommend a flag for "moving after zoning" though...

Hopefully I'll test the casting/combat stuff soon... I turned off the fast fast flag. I remember now why I had that on, and I'll try to describe in the best way possible. Here's my line: /call InitAPFVars 0 15 50 I want my bot to be range 50 from me, basically, or if within that, not moving. I can i...

Can't thank you enough. But I'm a nitpicker, and I find bugs well, I guess... 1. If follower zones faster than the leader, follower targets an object, moves slightly, then never recovers and continues following, even if leader zones in later. 2. If leader zones faster than follower, no problems. 3. ...

I'm an idiot, and you're right, the range stuff is in the ini. I always assumed (ass-u-me) that the range logic worked more along the "I'll inch forward if I'm getting -your target is too far away- messages" mixed with the "I'll strafe behind if I'm not" logic. Forgive my newbnes...

It did accept a nice variance, don't get me wrong. I'd like to hack a bit at the code and see if it could be improved slightly; I haven't looked at the positioning code for the botcombat things. Most of the more obvious oddities about positioning scripts have been a few things.... "exact-ness&q...