SRL Archive - SRL Archives

OffSetMouse;


Dynamite

2010-03-18 18:19:28

{*******************************************************************************
procedure OffSetMouse(mX, mY : Integer);
By: The Man and Nava2
Description: Offsets the mouse by the amount set by user
*******************************************************************************}
procedure OffSetMouse(mX, mY: Integer);
var
tX, tY: Integer;
begin
getMousePos(tX, tY);
MMouse(tX - mX, tY - mY, mX * 2, mY * 2);
end;

Wanted

2010-03-18 18:50:45

What's the point of this again?

Bionicle

2010-03-18 19:07:54

From: IceFire908
What's the point of this again?


moves the mouse e.g. (2, 3) would move it 2 points negative on the x axis and 3 on the y axis.(i think, i didn't really look at it for much more then about five seconds)

E: whats the point of the random? wouldn't it be better to let the user set it themselves?

Mr. Doctor

2010-03-18 19:30:57

Isn't the randomness in mouse just like this? I don't see the occasion on when you should use this.

Bionicle

2010-03-18 19:36:54

From: Mr. Doctor
Isn't the randomness in mouse just like this? I don't see the occasion on when you should use this.


No, randomness goes in any direction (i think) this you get to choose which way

Mr. Doctor

2010-03-18 19:41:27


Mouse(mousex, mousey, ranx, rany: Integer; left: Boolean);

The ranx moves it along the x-axis, rany moves it along the y-axis.
I presume that mX, mY are also the same thing. Correct me if I am wrong.

Camaro'

2010-03-18 19:54:52

From: Mr. Doctor

Mouse(mousex, mousey, ranx, rany: Integer; left: Boolean);

The ranx moves it along the x-axis, rany moves it along the y-axis.
I presume that mX, mY are also the same thing. Correct me if I am wrong.

I believe that is true.

There is no need for this function

Mouse(x-5,y+3, 5, 5, true);

mixster

2010-03-18 20:00:43

It's supposed to be part of an antiban of some kind where you move the mouse, click, then move slightly afterwards.

Without that background, it just seems like move the mouse within a box bounded by the params from current position, which it does do (note that M/Mouse still only add positive random amounts or 0 unless it was changed, where as this also does negative).

P.S. I don't like it

i luffs yeww

2010-03-18 20:44:44

Yeah, this was in another thread. And in that thread, I still said that this isn't necessary at all for antiban, because, from what we know from the sawse, Jagex doesn't monitor mouse movements; only mouse clicks. >_>

g0tp0t

2010-03-18 21:05:47

Jagex must be able to see mouse movements because its a java applet, which has to know where your mouse is in order to display things like UpText and tooltips. They are fighting hard against macroing and I see no reason for them to refrain from monitoring mouse movements, as that is probably there greatest chance at catching us.

When you click legitimately you tend to move the mouse and stop a little, i can see this as a nice feature that saves you a few lines of code. There are more worthless functions and procedures in SRL than this, FindObjectCustom being a good example, when i say that function, all it does is call FindObjectEx and input the exact same parameters.

Wanted

2010-03-18 21:50:47

From: i luffs yeww
Yeah, this was in another thread. And in that thread, I still said that this isn't necessary at all for antiban, because, from what we know from the sawse, Jagex doesn't monitor mouse movements; only mouse clicks. >_>


Where did you read that?

There is sufficient source code that says otherwise.

This isn't necessary for numerous reasons, that's not one of them.

Bionicle

2010-03-18 21:51:38

From: IceFire908
Where did you read that?

There is sufficient source code that says otherwise.

This isn't necessary for numerous reasons, that's not one of them.


Waaait was that that one thread with that guy who said he was from jagex who everyone thought was trollin'?

Wanted

2010-03-18 21:57:49

From: bionicle1800
Waaait was that that one thread with that guy who said he was from jagex who everyone thought was trollin'?


No.

Bionicle

2010-03-18 21:58:58

From: IceFire908
No.


I'm talking about what he is saying he read, not you :p

Wanted

2010-03-18 22:09:47

From: bionicle1800
I'm talking about what he is saying he read, not you :p


The troll said they record mouse movements as well…

i luffs yeww

2010-03-19 00:20:40

From: The Claw
Apparantly, the mouse movement and click data is kept for 60 seconds then deleted, and is only saved if someone reports you for macroing. Then that 60-second snapshot is looked over by jmods, and if you appear to be botting, youre banned. So if you make loops with randomness and longer than 60 seconds, you shouldnt get banned


iono.

weequ

2010-03-19 00:59:28

I think if you want to do it correctly it should be like:
getMousePos(tX, tY);
MMouse(tX - mX, tY - mY, (mX * 2)+1, (mY * 2)+1);
Thats becouse if you put like random(9) the maximium result would be 8 etc..

Stevee

2010-03-19 08:57:03

I should get some credz for the idea :c.

[/noob]

Daniel

2010-03-21 06:22:26

PickupMouse anybody?

Sabzi

2010-03-21 07:00:37

[QUOTE=Dan's The Man;696169]PickupMouse anybody?[/QUOTE]

Dang, PWND!
I can't believe I forgot about that.

i luffs yeww

2010-03-21 07:06:32

I think PickupMouse isn't the same idea as this, though?

Dynamite

2010-03-21 08:24:22

[QUOTE=Dan's The Man;696169]PickupMouse anybody?[/QUOTE]

[QUOTE=Sabzi;696172]Dang, PWND!
I can't believe I forgot about that.

From: i luffs yeww
I think PickupMouse isn't the same idea as this, though?


This ^

OffSetMouse is for this:

So you move your mouse to the target, and Click WHILE you are moving, so you over do it a bit.

Sabzi

2010-03-21 08:48:40

Only difference I can see that there is a wait in PickupMouse and it's more random as the user can't set it.
I can't understand what are you saying about "while you click" …

procedure OffSetMouse(mX, mY: Integer);
var
tX, tY: Integer;
begin
getMousePos(tX, tY); //it's not clicking
MMouse(tX - mX, tY - mY, mX * 2, mY * 2); //only moves the mouse away from previous mouse position(no clicking?)
end;

Personally I don't want to see a procedure like this in the include. It's way too simple.
Moving the mouse a bit away seems easily doable in scripts. Not to mention PickupMouse pretty much does that already.

Stevee

2010-03-21 09:38:45

You ever hear of KISS, Sabzi?

Keep it simple, stupid.

Lots of things in SRL/SCAR are based on simple things, yet when put together, make not-so-simple useful things.

And yes, that's just an acronym. No insults.

Blumblebee

2010-03-21 09:45:40

From: Stevee
You ever hear of KISS, Sabzi?

Keep it simple, stupid.

Lots of things in SRL/SCAR are based on simple things, yet when put together, make not-so-simple useful things.

And yes, that's just an acronym. No insults.


with this said, SRL is a compilation of useful functions and procedures that are (/can be) normally called during runtime of a script. A 2 line procedure that doesn't provide much of a function never mind can be added to a personal script with ease should not be put into an include. Sabzi is correct in the sense, if you can easily do it yourself then there is no need for it to be in the include.

Sabzi

2010-03-21 10:05:47

Just for the record I like the idea itself of moving the mouse away a human-like way.
But that should be something more like Tha Man said. Moving the mouse a little while the button is still down(mouse button). Not much, just as humans do.

@Blumblebee: Good to hear somebody thinks I am correct. Doesn't happen much :p.

i luffs yeww

2010-03-21 13:56:57

The argument that it's too simple isn't really valid, in my opinion. :/ Sorry, but tons of functions in SRL are just simple one line things..


procedure TypeSend(Text: string);
begin
TypeSendEx(Text, True);
end;

:) And many are just Result := something;. I don't think this should be commited because it doesn't make much sense to me, but the fact that it's too simple isn't really an argument.

Blumblebee

2010-03-21 21:39:35

From: Sabzi

@Blumblebee: Good to hear somebody thinks I am correct. Doesn't happen much :p.


:)

From: i luffs yeww
The argument that it's too simple isn't really valid, in my opinion. :/ Sorry, but tons of functions in SRL are just simple one line things..


procedure TypeSend(Text: string);
begin
TypeSendEx(Text, True);
end;

:) And many are just Result := something;. I don't think this should be commited because it doesn't make much sense to me, but the fact that it's too simple isn't really an argument.


you do realize typesend is there because it's simply taking the parameters out of typesend to make it more user-friendly, please take a look at TypeSendEx and tell me it's too simple.

i luffs yeww

2010-03-21 21:44:40

I know. I'm just saying that this is similar to the Result := Whatever; functions.

Blumblebee

2010-03-21 21:46:50

From: i luffs yeww
I know. I'm just saying that this is similar to the Result := Whatever; functions.


not really. It's modifying an already working function to add a random parameter, not take parameters away.

besides: typesend = useful, this = useless and can be added by a scripter without the increase of any lines really :/

i luffs yeww

2010-03-21 21:50:36

Blargh. Haha okay. I don't agree with this being different than single line functions. Here's an example..


{*******************************************************************************
Function DidRedClick: boolean;
By: Rasta Magician
Description: Checks for the Red X after a Click, Times out after 500 ms
*******************************************************************************}
Function DidRedClick: Boolean;
begin
Result := DidClick(true, 1000);
end;

{*******************************************************************************
Function DidYellowClick: Boolean;
By: Rasta Magician
Description: Checks for the Yellow X after a Click, Times out after 500 ms
*******************************************************************************}
Function DidYellowClick: Boolean;
begin
Result := DidClick(false, 1000);
end;

I just see no reason at all for those. And I see no reason for this because I don't feel it useful in the slightest. Except to show off your "ub3r 1337 scr33ptin skillzzzzZzzZZzzxz" to your friends. :/

Blumblebee

2010-03-21 21:51:45

From: i luffs yeww
Blargh. Haha okay. I don't agree with this being different than single line functions. Here's an example..


{*******************************************************************************
Function DidRedClick: boolean;
By: Rasta Magician
Description: Checks for the Red X after a Click, Times out after 500 ms
*******************************************************************************}
Function DidRedClick: Boolean;
begin
Result := DidClick(true, 1000);
end;

{*******************************************************************************
Function DidYellowClick: Boolean;
By: Rasta Magician
Description: Checks for the Yellow X after a Click, Times out after 500 ms
*******************************************************************************}
Function DidYellowClick: Boolean;
begin
Result := DidClick(false, 1000);
end;

I just see no reason at all for those. And I see no reason for this because I don't feel it useful in the slightest. Except to show off your "ub3r 1337 scr33ptin skillzzzzZzzZZzzxz" to your friends. :/


those provide understanding, this does not. Your mixing up your concepts still :p The title is simply so that people don't have to go to the include continually to know if red is true or false etc. This is adding a *2 and -randomness to mmouse… (I love being difficult)

i luffs yeww

2010-03-21 22:03:16

x] Yeah, this is fun. <3

And I agree with you, this is pointless. But the reason I think it's pointless isn't because it's "too simple." Because this is just Anti-ban. Everyone who uses anti-ban just uses straight functions/procedures from SRL. If this were like.. a one line way to find any TPA and nobody would ever have to do anything, then it'd make things too simple. Ya know? :)