hmm..more randomness for chooseoption?

[lardmaster]

it seems to me that every one of the commands(there are quite a few) that click on an option from a popup menu click in almost the exact same spot on the text. with power-* scripts, it will always click on the same spot on "Drop", right on the top of the o. this probably triggers account flagging/macro detection. my two suggestions are 1:simplify the popup commands into 2 or 3 of them 2: have the commands click everywere on the text. i tried editing it myself, but for some reason, when i increased the randomness, it would go off to the right sometimes, but never to the left.:eek: now why would this be? also, thanks to all you kind people who made all of these text finding options

[Mutant Squirrle]

lol these are very easily answered 1: because lots of people like there functions in SRL and we don't like to anger people :wink:. 2: Because they werent made that way. It changes but the change isn't noticable enough for you. I was however thinking of making a function that grabs the top left and top right corners of the popup box and then finds individual letters of the option you want clicked.

The reason yours most likely didnt work was because you added to the randomness causing it to move to the right or downward on the 'graph' of the RS client. you could have made a case statement in which in randomly chose to add or subtract, causing it to go from left to right assuming you worked with the x value. lol hope I didnt confuse you if I did leave a message and ask more questions I'll be happy to answer them.

[CamHart]

I personally agree with what he's saying. Isn't the reason SRL is even around to make things more human like? It would still be that persons function/procedure, you just made it random. It's a simple task (i think).

[Sumilion]

Hmm, sounds like a nice little project i could handle, i might look into this sometime ;)

[lardmaster]

i personally didnt mind all the functions :), but i think that if its random only within a 6 by 6 pixel box, that is way more accurate than you average human (think about it, dont you sometimes click on the "iron" part instead of the "drop" part.

mutant squirrel: about your idea of clicking individual letters, if you found a way to get the top left and bottom right co-ords of the text easy, then you could just use mousebox(...), or even gaussianBox(...). and, about adding or subtracting, i editted the Rx and Ry values in the clickmouse, so shouldnt that be in either direction?

EDIT:cool my first post as a DARK WIZARD!,(just realized).

[Mutant Squirrle]

lol uhm... Im not sure if you used my mouse procedure (not in SRL) then it would indeed be both but not using mine no I think SRL's mouse procedures only add to the values (could be wrong don't quote me on that haha)

I just remade my auto fighter (GhostSlayer) and I'm thinking about adding a RightClick option. So I will probably take up this project and post some results here. Other then that who ever said they were going to try. Is very welcomed to try.

[lardmaster]

ok, i kind of understood your first post, but i dont quite get this one. what is your procedure? mousebox is part of SRL and gaussianbox is a procedure i've written that will hopefully be in srl soon. i definatly think that MMOUSE adds and subtracts to values. but thanks for taking up the project!

[tarajunky]

it seems to me that every one of the commands(there are quite a few) that click on an option from a popup menu click in almost the exact same spot on the text. with power-* scripts, it will always click on the same spot on "Drop", right on the top of the o. this probably triggers account flagging/macro detection. my two suggestions are 1:simplify the popup commands into 2 or 3 of them 2: have the commands click everywere on the text. i tried editing it myself, but for some reason, when i increased the randomness, it would go off to the right sometimes, but never to the left.:eek: now why would this be? also, thanks to all you kind people who made all of these text finding options



function ClickTheText(text : String; x1, y1, x2, y2 : Integer; left : Boolean) : Boolean;
var
TextLength, a, b : Integer;
Begin
if(IsTextInAreaEx(x1,y1,x2,y2,a,b,Text,100,UpChars ,False,True,0,1,-1))then
Begin
TextLength := Length(Text);
if(left = true)then
Mouse(a + 2 + random(TextLength*6), b + random(3) + 7,0,0, true)
else
Mouse(a + 2 + random(TextLength*6), b + random(3) + 7,0,0, false);
result:= true;
End else
Begin
if(IsTextInAreaEx(x1,y1,x2,y2,a,b,'Cancel',100,UpC hars,False,True,0,1,-1))then
Begin
TextLength := 6;
Mouse(a + 2 + random(TextLength*6), b + random(3) + 7,0,0, true)
end;
end;
End;

Works great. Don't remember who wrote it.

[lardmaster]

yay, then people just need to adapt that formula to thier procedures!

EDIT:idea! maybe a function for clicking on the line, and not just the area of the text that it is looking for! that would be a great project!

[Mutant Squirrle]

lol look what you use right now in the include is perfectly fine. If it works dont fix it? When we make a new function / procedure you will know lol its understood what you want and im sure someone is making it right now. I have one but its for MY include. Sorry

[I Pick Axes]

ChooseOption is pretty heavily used. That extra lag might be an issue.

[lardmaster]

hmm... i dont see many supports, i might take it up on meself.