SRL Archive - RS3 Help

http://puu.sh/5WFfc.png
Every time I press play for a script, I get this bunch of code.

From: Wu-Tang Clan
http://puu.sh/5WFfc.png
Every time I press play for a script, I get this bunch of code.

What's the script? (Do you have anything after setupSRL?)

From: BMWxi
What's the script? (Do you have anything after setupSRL?)

program new;
{$Define SMART}
{$Include srl-6/srl.simba}
{$I SPS/SPS-RS3.Simba}

function RopeSwing: Boolean;
var
  i, h: Integer;
  TPA: TPointArray;
  ATPA: T2DPointArray;
  t: TTimeMarker;
begin
  if (not isLoggedIn) then
    Exit;

  //FindColorsTolerance(TPA, 6192020, IntToBox(mainscreen.playerpoint.x - 140, mainscreen.playerpoint.y, mainscreen.playerpoint.x + 110, mainscreen.y2), 5, ColorSetting(2, 0.12, 0.31));
  FindColorsTolerance(TPA, 206894, IntToBox(mainscreen.playerpoint.x - 140, mainscreen.playerpoint.y - 70, mainscreen.playerpoint.x + 200, mainscreen.y2), 5, ColorSetting(2, 0.2, 0.2));
  if (Length(TPA) < 1) then
  begin
    Exit;
  end;

  ATPA := TPA.ToATPA(5, 40);
  SortATPAFromMidPoint(ATPA, Point(randomRange(mainscreen.playerpoint.x - 100, mainscreen.playerpoint.x + 100), mainscreen.playerpoint.y));

  h := High(ATPA);

  for i := 0 to h do
  //writeln(length(atpa[i]));
  begin
    if (Length(ATPA[i]) < 50) then
      Continue;

    Mouse(ATPA[i][random(High(ATPA[i]))], MOUSE_MOVE, MOUSE_HUMAN);
    if IsMouseOverText(['wing', '-on', 'Swin', 'Rope', 'Swing'], 300) then
    begin
      if (not DidClick(false)) then
      begin
        t.Start;
          if (t.getTime > 6000) then
            WriteLn('No good');
        Wait(RandomRange(1000, 1300));
        Exit(True);
      end;
    end else
      begin
        if i > 3 then
          Exit;
        Wait(RandomRange(20,50));
      end;
  end;
end;

function LogBalance: Boolean;
var
  i, h: Integer;
  TPA: TPointArray;
  ATPA: T2DPointArray;
  t: TTimeMarker;
begin
  //FindColorsTolerance(TPA, 6192020, IntToBox(mainscreen.playerpoint.x - 140, mainscreen.playerpoint.y, mainscreen.playerpoint.x + 110, mainscreen.y2), 5, ColorSetting(2, 0.12, 0.31));
  FindColorsTolerance(TPA, 8885937, IntToBox(mainscreen.playerpoint.x - 140, mainscreen.playerpoint.y - 70, mainscreen.playerpoint.x + 200, mainscreen.y2), 7, ColorSetting(2, 0.2, 0.8));
  if (Length(TPA) < 1) then
  begin
    WriteLn('lol');
    Exit;
  end;

  ATPA := TPA.ToATPA(10, 20);
  SortATPAFromMidPoint(ATPA, Point(randomRange(mainscreen.playerpoint.x - 100, mainscreen.playerpoint.x + 100), mainscreen.playerpoint.y));

  h := High(ATPA);

  for i := 0 to h do
  //writeln(length(atpa[i]));
  begin
    if (Length(ATPA[i]) < 50) then
      Continue;

    Mouse(ATPA[i][random(High(ATPA[i]))], MOUSE_MOVE, MOUSE_HUMAN);
    if IsMouseOverText(['alance', 'log', 'alk', 'ross', '-across'], 300) then
    begin
      if (not DidClick(false)) then
      begin
        t.Start;
          if (t.getTime > 6000) then
            WriteLn('No good');
        Wait(RandomRange(1000, 1300));
        Exit(True);
      end;
    end else
      begin
        if i > 3 then
          Exit;
        Wait(RandomRange(20,50));
      end;
  end;
end;

begin
  SetupSRL;
  LogBalance;
  //RopeSwing; 
end.

EDIT: This is mostly Sjoe's code, I am pretty much using it to make a Barbarian Agility script

SRL-6's way of spamming the user with unnecessary debug information by default.

Just disable it or put ClearDebug; right after SetupSRL;.

From: Brandon
SRL-6's way of spamming the user with unnecessary debug information by default.

Just disable it or put ClearDebug; right after SetupSRL;.

What makes you think its unnecessary? :(

From: Olly
What makes you think its unnecessary? :(

Only thing the user needs to know there is that SRL is setup and Smart is being spawned.
I doubt the average user even knows how SMART's pairing mechanism works and they probably don't care at all. They just want to know that SMART is spawned and works.

How many free clients found, paired to existing client, attempting to pair, successfully spawned from old client..

None of these are things the user should know. These are all intermediate steps to two possible outcomes that the user needs to know:
Success & Failure.

Where a button was found on screen is none of the user's concerns. It may be a developer concern and for that a developer should:
a - do their own debugging.
b - turn on debugging if available.

For these reasons, IDE's have debug and release options and options to strip symbols from release builds. I'm not trying to project my views on everyone, but I'm just saying it how I personally see it. Not sure if the same logic would apply to others, but that is a lot of debugging that bombards the user who just wants to start a script and know that it works. In the above code, all that debugging is happening before the script even gets to its main entry point. This is the pre-setup.

I presume this is why OP made this thread. He probably wants to get rid of it or disable somehow.

From: Brandon

How many free clients found, paired to existing client, attempting to pair, successfully spawned from old client..

None of these are things the user should know.

Actually once it was very useful for me to know what how many clients it found, and the details on what it tried to to and successfully did. On my other PC I was trying to find out why Simba was refusing to pair to any of the available clients and insisted on making a new one, but then couldn't pair with the new one. From the debug I figured that Simba was having trouble finding the temp SMART files that it uses to pair.

Without the debug all I would have been able to tell was that Simba kept spawning SMARTs.

I think that adding something like srlDebug:= false wouldn't be a bad idea, but I disagree that the information isn't useful to users.

uh, there is and always have been..

disableSRLLog := true;

From: Olly
uh, there is and always have been..

disableSRLLog := true;

Should probably be turn off by default. People rarely need that sort of information.

From: Brandon

Only thing the user needs to know there is that SRL is setup and Smart is being spawned.
I doubt the average user even knows how SMART's pairing mechanism works and they probably don't care at all. They just want to know that SMART is spawned and works.

How many free clients found, paired to existing client, attempting to pair, successfully spawned from old client..

None of these are things the user should know. These are all intermediate steps to two possible outcomes that the user needs to know:
Success & Failure.

Where a button was found on screen is none of the user's concerns. It may be a developer concern and for that a developer should:
a - do their own debugging.
b - turn on debugging if available.

For these reasons, IDE's have debug and release options and options to strip symbols from release builds. I'm not trying to project my views on everyone, but I'm just saying it how I personally see it. Not sure if the same logic would apply to others, but that is a lot of debugging that bombards the user who just wants to start a script and know that it works. In the above code, all that debugging is happening before the script even gets to its main entry point. This is the pre-setup.

I presume this is why OP made this thread. He probably wants to get rid of it or disable somehow.

No, I get this little bit of code whenever I press try to test my balancelog function. The it compiles, spits it out, and then executes. Nothing on SMART happens. All the other functions are identicle but only balancelog gives me grief.

i have this issue too but it only appears when i dont use smart..

From: Wu-Tang Clan
No, I get this little bit of code whenever I press try to test my balancelog function. The it compiles, spits it out, and then executes. Nothing on SMART happens. All the other functions are identicle but only balancelog gives me grief.

Well if you are only testing one function and nothing happens after setupsrl… it sounds like there is something up with that function b/c the debug is saying setupsrl worked fine