I'm having the same issues as Tux. It ping pongs between targets, doesn't buff, spazzes on the action bar, etc. I intend to look at the source tomorrow or friday to see what's up.
It could be just that. Any developer worth his salt would log exceptions that occurred during runtime. They MIGHT be logging these error cases and forwarding certain ones to GMs so they can immediately respond to take a report. Of course it's speculation, but it is indeed possible. That or it was pure coincedence.Quote:
ok something weird,not necessarly related to evobot but still ill tell u what happened see if you can come up with answers.
ive been using ALBOT since it came out pretty much, never been caught, no gms /w me,no bans,not even somone pking me thinking im a bot. so alls good.
then i see evobot,looks amazing, lookis like it would do somethings other bots didnt, suce as targeting a number of mobs, allowing pets and some other coll looking things.
i got 1 version and had problems getting it working, so i came here,posted and then downloaded the newest version.
now here comes the strange part, i set it all up without pets (i forgot by now i could usepets on my ele after albot for so long) press start on evo. w00t it buffs,targets,attacks,awesome!! so i got back to tweak the settings in evo, rememberd i have pets, set them up. started evo. again buffs worked, pets worked, it starts to target.... but then targets my pet and actually casts of a few skills on it. now before i get the chance to pause eve or turn it off a GM is next to me... WTF... he/she /w me are u ok?? i think fuck port to town.. GM still there so i log out.
now why after using albot on several account which i still have have i never seen a gm or been reported. and thn evo shoots my pet and a gm shows.
(btw i was in an area where there was not 1 single person around, no one was there to see me)
im not saying its to do with evo,maybe it was, maybe when u shoot your own pet it summons a gm because obv thats a wird thing to do. i dont know, suggestions or comments welcome. :)
Func SwitchBarOn($ times) For = 1 To ($ times - 1) ControlSend(, "", "", "`") Sleep(10) Next EndFunc ;==>SwitchBarOn Func SwitchBarOf($ times) For = 1 To ($ times - 1) ControlSend(, "", "", "^`") Sleep(10) Next EndFunc ;==>SwitchBarOf
$ switchbar = SwitchBarOn.....
Func Buff($ Bar, $ Key)
...
If GUICtrlRead($ lensuse) = 1 Then
ControlSend($ Title, "", "", "{d}")
= SwitchBarOn(GUICtrlRead($ lensbar))
ControlSend($ Title, "", "", "{" & GUICtrlRead($ lenskey) & "}")
$ switchbar = SwitchBarOf(GUICtrlRead($ lensbar))
EndIf
...
EndFunc ;==>Buff
Func SwitchBarOn($ times)
For = 1 To ($ times - 1)
ControlSend($ Title, "", "", "{^}")
Sleep(10)
Next
Return ("1")
EndFunc ;==>SwitchBarOn
Func SwitchBarOf($ times)
For = 0 To (4 - $ times)
ControlSend($ Title, "", "", "{^}")
Sleep(10)
Next
Return ("0")
EndFunc ;==>SwitchBarOf
Ok. I just changed the code because buffing wasn't working for me at all and I noticed a few others say the same thing. Basically it would just switch the bar very fast back and forth.Quote:
If u watch the function Buff, u will see, what is used for $ times...Code:Func Buff($ Bar, $ Key) ... If GUICtrlRead($ lensuse) = 1 Then ControlSend($ Title, "", "", "{d}") = SwitchBarOn(GUICtrlRead($ lensbar)) ControlSend($ Title, "", "", "{" & GUICtrlRead($ lenskey) & "}") $ switchbar = SwitchBarOf(GUICtrlRead($ lensbar)) EndIf ... EndFunc ;==>Buff Func SwitchBarOn($ times) For = 1 To ($ times - 1) ControlSend($ Title, "", "", "{^}") Sleep(10) Next Return ("1") EndFunc ;==>SwitchBarOn Func SwitchBarOf($ times) For = 0 To (4 - $ times) ControlSend($ Title, "", "", "{^}") Sleep(10) Next Return ("0") EndFunc ;==>SwitchBarOf
it's the count for that bar, where u've put ur lens stones first.
to switch lens stones on, i used -1 as i whish to let it switch one time up, to reach bar #2.
this is declared in the function calling itself SwitchBarOn(GUICtrlRead($ lensbar)) where guictrlread gets the numb u have to put into the declared field.
to switch them off again, i used then 4- what simply means the complete cycle -1 to return to the origin bar.
the controlsend of '{^}' is here for me the part to let the bar switch, the code '´' toggles it only as long as u keep that key pressed.
if u have to use it, just replace it, if that works. ;)
oh and it's not the same code as u will get if u send '^{}' which then means as u told, the Ctrl key.
the return command doesn't matters but i had more ideas in the beginning to implement using it...there is no usage for that string collecting the code that function returns, so no problem, maybe u got a need for that, if not, i don't see a problem. ;)
It's just like u got the Pause key on ur keyboard but u don't ever used it, maybe u will have a need for it later...