SRL Archive - SRL Archives

The current one:

function CloseBank: Boolean;
var
  i, Timer, Points: Integer;
begin
  if BankScreen then
  begin
    MarkTime(Timer);
    repeat
      Mouse(485, 41, 4, 4, True);
      for i := 0 to 30 do
      begin
        Wait(100);
        Points := CountColorTolerance(2070783, 177, 30, 337, 52, 5);
        if(Points < 170)then
        begin
          Result := True;
          Break;
        end;
      end;
    until(Points < 170)or(TimeFromMark(Timer) > 8000)
  end;
end;

I know its not a big deal or anything because it uses randomness in the clicking, but CloseBank uses coord clicking, I know the X button is in the same spot every time but I'm sure theres a different method that would be more anti-ban.

For different methods maybe a DTM, or Bitmap, or MouseBox?

Sorry if I'm totally wrong and coord clicking would be ok in this situation (I see how it could be because the square is sorta small).


MouseBox's x1, y1, x2, y2:

MouseBox(478, 34, 493, 48, 1);

For a failsafe maybe add isuptext for these as well?

Or maybe at least increase the randomness of the mouse to like 8, 8 or something.

Again, sorry if it doesn't really matter.

Dtm or Bmp isnt needed becouse the X is in the same spot everytime. MouseBox could be fine.

Also, is it just me or are the coordinates for it off anyways? (in the Mouse coords in the current CloseBank) (using SCAR 3.15b)

MouseBox clicks in a random spot in the box.. like a human :)

Yeah, who said they didn't know what MouseBox does?

If it works, tell me and I'll put it in :)

Yeah, I replaced the

Mouse(485, 41, 4, 4, True);

with

 MouseBox(478, 34, 493, 48, 1); 

I tested it about 20 times and it worked every time.

Look at the 4, 4:

Mouse(485, 41, *4, *4, True);

The click will not always be in the same spot because of those two numbers.

From: IP-Drowner
Look at the 4, 4:

Mouse(485, 41, *4, *4, True);

The click will not always be in the same spot because of those two numbers.

it won't be in the same spot. but 4 pixels is not much at all..or 3..whatever, but for something used like that, the most randomness is the best, as long as it works

From: Iron man
Yeah, who said they didn't know what MouseBox does?

why have a dtm when you could only do mousebox?

From: Zytex!
why have a dtm when you could only do mousebox?

Thats why I suggested MouseBox as well.

Why have all that goblydegook when I could just write:

procedure CloseBank;
begin
  Mouse(485, 41, 5, 5, True);
end;

Seriously people… You've become *too* paranoid. I think they'll start looking for things that are too random instead of things that are always the same.

Just make a bitmap of it - if FindBitmap then MMouse(x,y,5,5); if IsUpText('lose') then begin GetMousePos(x,y); Mouse(x,y,1,1,True) else WriteLn('Hy fails!');

Still too complicated………….

Srsly, wtf, mate.

How is MouseBox too complicated?

Its not, its just all the other stuff you have with it… instead of your lines, I'd use:

function CloseBank: Boolean;
begin
  Result := True;
  if BankScreen then
    MouseBox({...});
  Wait(200);
  if BankScreen then
    Result := False;
end;

Seeeeee…..?

Are you talking about this?

function CloseBank: Boolean;
var
  i, Timer, Points: Integer;
begin
  if BankScreen then
  begin
    MarkTime(Timer);
    repeat
      Mouse(485, 41, 4, 4, True);
      for i := 0 to 30 do
      begin
        Wait(100);
        Points := CountColorTolerance(2070783, 177, 30, 337, 52, 5);
        if(Points < 170)then
        begin
          Result := True;
          Break;
        end;
      end;
    until(Points < 170)or(TimeFromMark(Timer) > 8000)
  end;
end;

'Cause I never made that, its in the current SRL.
Or am I being stupid and not realizing what your talking about?

My idea was just to replace the Mouse with MouseBox.

Ooooh. I thought you made that to replace the current one…

Well, uhm… Mine is just way shorter.