Probably the space in your name, thanks for letting me know.

 

Thank you for the clear answer. Maybe a difficult question to answer: Will that bug be patched anytime soon? And will it be announced that it will be fixed? (I really like to bypass the boot.)

Version 2.4.65 Release

-Patched small issue in Worlds class

-Added Client isHumanInputEnabled()

-AutoLogin now re-attempts initially with a quick-login (~20 seconds) if you were disconnected from world hopping

-AutoLogin various improvements

-Boot login flag allows names with spaces. Replace the space in your name with an underscore

 

Version 2.4.65 Release

-Patched small issue in Worlds class

-Added Client isHumanInputEnabled()

-AutoLogin now re-attempts initially with a quick-login (~20 seconds) if you were disconnected from world hopping

-AutoLogin various improvements

-Boot login flag allows names with spaces. Replace the space in your name with an underscore

 

gj m'lord

 

Version 2.4.65 Release

-Patched small issue in Worlds class

-Added Client isHumanInputEnabled()

-AutoLogin now re-attempts initially with a quick-login (~20 seconds) if you were disconnected from world hopping

-AutoLogin various improvements

-Boot login flag allows names with spaces. Replace the space in your name with an underscore

 

 

Works like a charm, thanks!

Maybe a suggestion: Would it be ever possible to bypass the boot screen with like logging directly into your account, so that you don't have to go through to the GUI, but are prompted with the client of RuneScape? (In short words: Skip the Add Bot)

Works like a charm, thanks!

Maybe a suggestion: Would it be ever possible to bypass the boot screen with like logging directly into your account, so that you don't have to go through to the GUI, but are prompted with the client of RuneScape? (In short words: Skip the Add Bot)

 

Yes, I'm working on the system. It will even start up a script for you.

Yes, I'm working on the system. It will even start up a script for you.

 

Simply amazing! I'll wait for it. 

@Alek

 

i know its more for in the suggestion section.

 

but isnt it a option now, to add your current ip/proxy to the client frame? cause now when i start 10 clients i am not sure what client is attached to what proxy.

 

something like this http://osbot.org/forum/topic/91110-ip-display-changer/

@Alek, would freezing (disabling canvas) while script runs to save cpu be a possibility? 

 

@Alek

 

i know its more for in the suggestion section.

 

but isnt it a option now, to add your current ip/proxy to the client frame? cause now when i start 10 clients i am not sure what client is attached to what proxy.

 

something like this http://osbot.org/forum/topic/91110-ip-display-changer/

there is a script for this but the link is down. I agree though being able to see which client is using which proxy would be convenient. 

@Alek, would freezing (disabling canvas) while script runs to save cpu be a possibility? 

 

there is a script for this but the link is down. I agree though being able to see which client is using which proxy would be convenient. 

 

yeay, and i can still use this script in the topic. but it will safe some work

@Alek

 

i know its more for in the suggestion section.

 

but isnt it a option now, to add your current ip/proxy to the client frame? cause now when i start 10 clients i am not sure what client is attached to what proxy.

 

something like this http://osbot.org/forum/topic/91110-ip-display-changer/

 

I'll consider it.

Wicked job dudes

some of my scripts aren't working after update.

Stealth Quester stopping working using this update.

Can someone confirm this?

The bot doing very well before update and now i cant using stealth quester =/

 

[iNFO][06/09 09:31:07 PM]: Started script : Stealth Quester

[ERROR][bot #1][06/09 09:31:07 PM]: Error in bot executor!

java.lang.NoSuchMethodError: org.osbot.rs07.event.WebWalkEvent.prefetchRequirements(Lorg/osbot/rs07/script/MethodProvider;)Lorg/osbot/lpt2;

at api.LPt8.a(hd:171)

at e.Con.m(ic:30)

at api.coN.a(rc:106)

at c.cOn.onLoop(kc:550)

at org.osbot.rs07.event.ScriptExecutor$InternalExecutor.run(do:292)

at java.lang.Thread.run(Unknown Source)

 

Thanks for the update
 

-AutoLogin now re-attempts initially with a quick-login (~20 seconds) if you were disconnected from world hopping
-AutoLogin various improvements

Glad this was finally added

Really nice updates