I thought this sounded like a pretty good idea.
It would be the basic wait command, bundled with anti-random checking and anti-idle. I've already made an anti-idle include but it wouldn't run anything other than the include because of the waiting! I thought, if we based it from how long the script actually waits, then the user wouldn't need to worry about auto-logouts.
The script would also check for randoms at regular intervals (keeping lag in mind) during the waiting, I also happen to think my anti-idle has more potential than benlands just because benland has only used the mouse. My version will change the camera angle, wait a little, and change it back.
I will definately be putting this together for my next script but does anyone else like the idea? Maybe someone knows how to jockey the regular wait command?
To give you a sample of what I mean:
It would obviously be a lot more complex than that.Code:procedure wait2 (var timetowait : integer); var totalwaittime : Integer; randcounter : Integer; idlecounter : Integer; begin repeat wait(1); totalwaittime:= totalwaittime + 1; randcounter:= randcounter + 1; idlecounter:= idlecounter + 1; if (randcounter = 100) then begin randcounter:= 0; Antirandoms; end; if (idlecounter = 5000) then begin idlecounter:= 0; RandomMovement; end; until (totalwaittime = timetowait) end;






Reply With Quote

.
)

I'm still going to use mine but I was just checking if it'd be useful. Btw, what do you mean too many waits? I was only aware of benlands 






