eq2bot questions

[Pygar]

Working on fixing up a good rogue archtype script and running into a few things that are certainly contributing to poor dps.

Is there good reason why function CastSpellRange contains:

if ${Me.IsMoving}
{
return -1
}

Any arguement for prefixing this check with ispriest or ismage, as combat arts are castable while moving?

 

[Karye]

If the bot is still moving It might not be in the correct posistion to use the combat the combat art, flank, rear, range.....

 

[Pygar]

Key being *might*.

Ideally on a rogue script I would turn on auto attack, fire getbehind(), cast my debuff line while getting to position, possible start my non positionals also before getbehind is finished positioning. Then run thru 'behind' attacks.

Then getinfront() using debuffs and non directionals while moving, rinse and repeat.

I find rogue classes to require significant positioning as mobs move, tank positions, targets switch, things die, etc. The ability to execute directional indiferent arts while positioning I believe will increase scripted rogue dps output.

I can test using my own subset of these same functions in my script file, but was curious if we're adverse to taking the return out for combat art classes, or I guess for hybrids it requires an optional parameter to bypass (maybe an arguement for having it in the class files).

Sorry for thinking outloud

Mainly was curious what the arguement against was. Personally I would like the script to try to execute attacks while positioning. The worst case is they are out of range / position for a bit, but currently dps while positioning is almost null. Any positive increase is a win.