SRL Archive - General Botting Help

is there anything in lape that searches for a specific string of text in the debug window?

something like

if getDebugPrint('desired string')

From: hackingislol133
is there anything in lape that searches for a specific string of text in the debug window?

something like

if getDebugPrint('desired string')

Why would you want to do such a thing?

Debug text has to come from somewhere in your script or an include, so why not find the actual thing rather than the resulting debug text?

From: The Mayor
Why would you want to do such a thing?

If you plan on monitoring Simba's debug from another application or plugin.

From: The Mayor
Why would you want to do such a thing?

You could also make user input from a function like that..

SArr := getDebugLines;
For I:=0 to High(SArr)do
  Case SArr[I] of
    'changeplayer': NextPlayer(True);
    'break': handle_Breaks;
    'twerk_like_miley': handle_Redneck;
  end;

From: Brandon
If you plan on monitoring Simba's debug from another application or plugin.

Yeah, this.

Would be truly awesome to have function DebugText: string; and/or function DebugLines: TStringArray; someday in Simba!

From: Clarity
Debug text has to come from somewhere in your script or an include, so why not find the actual thing rather than the resulting debug text?

The source of the debug comes from smart.srl. I asked about this a while back and was told to not touch smart.srl (ya im still stuck on this)

I have a shell script which I which reruns the script when it fails to login. I originally wanted it to read the debug window itself but I've given up on that. Now it checks for an email and reruns.

I've tried a couple approaches but I couldn't get anything working. so now I'm trying to get the script to send an email based on debug print.

From: Janilabo
Yeah, this.

Would be truly awesome to have function DebugText: string; and/or function DebugLines: TStringArray; someday in Simba!

It's honestly not worth it currently, due to each script sharing the same debug box.

no but you can read text from a bitmap

From: Olly
It's honestly not worth it currently, due to each script sharing the same debug box.

Yeah Olly, I see what you mean.. Although, it still wouldn't hurt to have it right? :)
I mean, it still would be very useful for people, that aren't just running multiple scripts with Simba.

I still don't see why you need to do this. You can tell if your player fails to login within your script itself. You can even get simba to force respawn SMART if this happens.

From: The Mayor
I still don't see why you need to do this. You can tell if your player fails to login within your script itself. You can even get simba to force respawn SMART if this happens.

with if isLoggedIn?

i've tried it and forced the client to respawn when the script fails to input player info. but whenever a new client is spawned, the input box still becomes active too slowly.

additionally, if the script fails to login after the 6 hour limit, then smart.srl terminates the script. I've tried putting a delay into smart.srl as well, but the client only becomes responsive when there's been some interaction with it.

that's why I figured the solution is to have a shell script outside of simba click rerun the script after it terminates.

From: hackingislol133
with if isLoggedIn?

i've tried it and forced the client to respawn when the script fails to input player info. but whenever a new client is spawned, the input box still becomes active too slowly.

additionally, if the script fails to login after the 6 hour limit, then smart.srl terminates the script. I've tried putting a delay into smart.srl as well, but the client only becomes responsive when there's been some interaction with it.

that's why I figured the solution is to have a shell script outside of simba click rerun the script after it terminates.

All can be done with a few simple overrides without modifying the include.