I don't know if it is just me or what but i threw the wizzy script up against a bunch of dummies and watched it's overall behavior and noticed that sometimes it goes to cast the spell by queueing it but then when the current spell being cast finished it doesnt cast the queued spell like its going too fast and didnt get the spell in in time. this really messes things up by casting frigid gift without ice spears and not casting in correct casting order? has anyone else been experiencing this? or is it just me? What could be casusing this? I tried messing around with the script and the only way i could get it to actually cast every spell in order as intended was to add wait 10 before each spell cast but by god does that slow the casting down tremendously.
EQ2 Bot Wizard Script issues
- Thread starter Herculezz
- Start date
Well i have noticed that like on long casting spells like fusion or ice comet it queues a bunch of spells before the casting is complete you can literally sit there and watch it queue the next spells in the queue list until the casting is complete. It seems that it doesnt wait until the current spell being casted is complete before it moves to the next spell and even the next spell. I have tried this both in the guild hall and in KJ training wall and same results nearly every single time and i have ran over 100 tests.
if there would be a way for the script to cast - queue next spell - wait until the queued spell starts casting - que next spell it would seem to fix this, is the script capable of that?
My average ping is around 200
my fps seems to be capped at 50, not sure if this is eq2 or innerspace that does this.
if there would be a way for the script to cast - queue next spell - wait until the queued spell starts casting - que next spell it would seem to fix this, is the script capable of that?
My average ping is around 200
my fps seems to be capped at 50, not sure if this is eq2 or innerspace that does this.
Last edited:
Ok i went into innerspace and took off the FPS limiter and now i get 80 FPS but still same results. Mainly the issue is when casting really fast spells or really slow spells.
When casting fast casting spells it queues the next spell but for some reason spell finishes it doesnt cast the queue spell instead casts the next spell in the combat routine.
on slow casting spells like Ice Comet for example it will que the next spell in the routine Rays and then a second later queue Ball of fire then 1s later queue up thunderclap when it is still casting Ice Comet hence rays and ball of fire are casted out of order and then it will come back too ball of fire because of the priority casting but still does not cast spells in correct order because of this.
it would be nice if we could do it like this lol
if ${spellsused}<=${spellthreshold} && ${Me.Ability[${SpellType[505]}].IsReady}
{
call CastSpellRange 505 0 0 0 ${KillTarget}
wait(505.iscasting)
spellsused:Inc
}
or something like that but i am sure that a variable to see if a particular spell is casting is not implemented and even if it was i am sure its not coded to work in a wait command lol.
When casting fast casting spells it queues the next spell but for some reason spell finishes it doesnt cast the queue spell instead casts the next spell in the combat routine.
on slow casting spells like Ice Comet for example it will que the next spell in the routine Rays and then a second later queue Ball of fire then 1s later queue up thunderclap when it is still casting Ice Comet hence rays and ball of fire are casted out of order and then it will come back too ball of fire because of the priority casting but still does not cast spells in correct order because of this.
it would be nice if we could do it like this lol
if ${spellsused}<=${spellthreshold} && ${Me.Ability[${SpellType[505]}].IsReady}
{
call CastSpellRange 505 0 0 0 ${KillTarget}
wait(505.iscasting)
spellsused:Inc
}
or something like that but i am sure that a variable to see if a particular spell is casting is not implemented and even if it was i am sure its not coded to work in a wait command lol.
Last edited:
ok i made a video of what it is doing. Notice when casting ice comet it doesnt do like when casting fusion and say blah blah queued waiting for previous blah blah to finish casting. Instead it tries queueing a bunch of spells over and over.
go here to get the AVI file
http://www.megaupload.com/?d=F4X18KL1
go here to get the AVI file
http://www.megaupload.com/?d=F4X18KL1
mistrornge
Active Member
Sounds like the same problem the warden was having when it was casting buffs. It would cast one, cue the next, but cast another before the second one started. I will start watching a bit closer on them to if this happens on other bots as well.
yes i remember that and that is basically what it is doing. BTW the guardian script still does that with buffing.
but
i did figure out how to get it to wait until the casting is complete before casting the next spell by using
while ${Me.CastingSpell}
{
wait 2
}
after each spell cast
but this takes away from priority casting by waiting after each spell and going in direct order rather than casting the more important spells when they are up.
The only logical way I can think of fixing this and having both work would be either
1 - a background worker (which i dont think is available in this scripting language then again i dont know much about it)
or
2 - using a command that will restart from a set point at the beggining of the combat routine similiar to a goto command. does isxeq2 have that feature in it?
Ok it worked and seems to be working quite a bit better. On training wall it seems to give me 1-1.5k more dps I am sure this number would increase tremendously over a longer fight as well. Also it does not skip spells and casts in order of priority casting the spells according to TSO DPS Efficiency. I am gonna do some raid testing tonight and if all goes well will post it for people to try out.
hmm thats weird i am using it as we speak with no problems. stronge. anyone else have the same problem? You might try checking your Auto Hunt Range and The MA range if those are too low it wont see the dummy and wont go into combat mode.