Jump to content

OSBot 2.1.10


Laz

Recommended Posts

Hello OSBoticans, I managed to improve the way mouse positions are picked and how the bot randomizes its movements. It's still a work in progress but it's great improvement from the previous releases' random spazzing on complex objects. Additionally some built-in painters have been modified aesthetically.

 

Here's the download: http://osbot.org/osbot2_beta/OSBot-packed-2.1.10.jar

API: http://osbot.org/osbot2_api/

API (.zip): http://osbot.org/osbot2_api/Docs.zip

 

Thanks,

Sincerely Laz and the OSBot Team.

 

P.S.: The official OSBot2 Repository will be opening soon!

  • Like 4
Link to comment

Cool.
 
Can you look into what causes these? It's the main errors I get which requires client restart.

[ERROR][05/31 11:48:31 PM]: Uncaught exception!
java.lang.NullPointerException
	at org.osbot.rs07.event.ScriptExecutor.stop(zm:180)
	at org.osbot.rs07.event.ScriptExecutor.stop(zm:137)
	at org.osbot.Lpt7.run(fn:881)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
ERROR][05/30 08:31:31 PM]: Uncaught exception!
java.lang.IllegalMonitorStateException
	at java.util.concurrent.locks.ReentrantLock$Sync.tryRelease(Unknown Source)
[ERROR][05/30 08:31:31 PM]: Uncaught exception!
java.lang.IllegalMonitorStateException
	at java.util.concurrent.locks.ReentrantLock$Sync.tryRelease(Unknown Source)
	at java.util.concurrent.locks.AbstractQueuedSynchronizer.release(Unknown Source)
	at java.util.concurrent.locks.ReentrantLock.unlock(Unknown Source)
	at java.util.concurrent.LinkedBlockingQueue.take(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor.getTask(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)

2.1.10 Takes ages to load a tab and with 80% cpu usage while its doing so.

Normal cpu usage has gone up to 70%. One tab, one script.

Edited by Th3
  • Like 1
Link to comment

Im not trying to be rude but:

I really liked the 2.1.3 release because my cpu use was crazy low also not much npe, monitor bugs, Can you explain me why you keep releasing kinda fucked up things? I mean its damn good you fix things like equipment but I'd rather have stable bot than equipment info.

Can you guys focus more on osbot stability than api features? I know i;ve been fucking around api but atm stable bot is most important thing for devs.

 

 

Stack obfuscaion much.

Java, sweet java... Fixed with 8.

"C:\Program Files\Java\jdk1.7.0_60\bin\java" -Didea.launcher.port=7535 "-Didea.launcher.bin.path=C:\Program Files (x86)\JetBrains\IntelliJ IDEA 13.1.3\bin" -Dfile.encoding=UTF-8 -classpath "C:\Program Files\Java\jdk1.7.0_60\lib\ant-javafx.jar;C:\Program Files\Java\jdk1.7.0_60\lib\dt.jar;C:\Program Files\Java\jdk1.7.0_60\lib\javafx-doclet.jar;C:\Program Files\Java\jdk1.7.0_60\lib\javafx-mx.jar;C:\Program Files\Java\jdk1.7.0_60\lib\jconsole.jar;C:\Program Files\Java\jdk1.7.0_60\lib\sa-jdi.jar;C:\Program Files\Java\jdk1.7.0_60\lib\tools.jar;C:\Users\Robert\OSBot\Scripts;C:\Program Files (x86)\JetBrains\IntelliJ IDEA 13.1.3\lib\junit-4.11.jar;C:\Users\Robert\OSBot\jar\OSBot-packed-2.1.10.jar;C:\Program Files (x86)\JetBrains\IntelliJ IDEA 13.1.3\lib\idea_rt.jar" com.intellij.rt.execution.application.AppMain Boot
No proxy authentication!
=============== DEBUG MESSAGE: illegal bytecode sequence - method not verified ================

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  Internal Error (os_windows_x86.cpp:143), pid=8940, tid=6520
#  guarantee(result == EXCEPTION_CONTINUE_EXECUTION) failed: Unexpected result from topLevelExceptionFilter
#
# JRE version: Java(TM) SE Runtime Environment (7.0_60-b19) (build 1.7.0_60-b19)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.60-b09 mixed mode windows-amd64 compressed oops)
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Users\Robert\Dropbox\Projects\OSBotScripting2\hs_err_pid8940.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.sun.com/bugreport/crash.jsp
#

Process finished with exit code 1

Edited by PolishCivil
  • Like 2
Link to comment

 

Im not trying to be rude but:

I really liked the 2.1.3 release because my cpu use was crazy low also not much npe, monitor bugs, Can you explain me why you keep releasing kinda fucked up things? I mean its damn good you fix things like equipment but I'd rather have stable bot than equipment info.

Can you guys focus more on osbot stability than api features? I know i;ve been fucking around api but atm stable bot is most important thing for devs.

 

 

Stack obfuscaion much.

"C:\Program Files\Java\jdk1.7.0_60\bin\java" -Didea.launcher.port=7535 "-Didea.launcher.bin.path=C:\Program Files (x86)\JetBrains\IntelliJ IDEA 13.1.3\bin" -Dfile.encoding=UTF-8 -classpath "C:\Program Files\Java\jdk1.7.0_60\lib\ant-javafx.jar;C:\Program Files\Java\jdk1.7.0_60\lib\dt.jar;C:\Program Files\Java\jdk1.7.0_60\lib\javafx-doclet.jar;C:\Program Files\Java\jdk1.7.0_60\lib\javafx-mx.jar;C:\Program Files\Java\jdk1.7.0_60\lib\jconsole.jar;C:\Program Files\Java\jdk1.7.0_60\lib\sa-jdi.jar;C:\Program Files\Java\jdk1.7.0_60\lib\tools.jar;C:\Users\Robert\OSBot\Scripts;C:\Program Files (x86)\JetBrains\IntelliJ IDEA 13.1.3\lib\junit-4.11.jar;C:\Users\Robert\OSBot\jar\OSBot-packed-2.1.10.jar;C:\Program Files (x86)\JetBrains\IntelliJ IDEA 13.1.3\lib\idea_rt.jar" com.intellij.rt.execution.application.AppMain Boot
No proxy authentication!
=============== DEBUG MESSAGE: illegal bytecode sequence - method not verified ================

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  Internal Error (os_windows_x86.cpp:143), pid=8940, tid=6520
#  guarantee(result == EXCEPTION_CONTINUE_EXECUTION) failed: Unexpected result from topLevelExceptionFilter
#
# JRE version: Java(TM) SE Runtime Environment (7.0_60-b19) (build 1.7.0_60-b19)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.60-b09 mixed mode windows-amd64 compressed oops)
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Users\Robert\Dropbox\Projects\OSBotScripting2\hs_err_pid8940.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.sun.com/bugreport/crash.jsp
#

Process finished with exit code 1

I love how you always speak your mind so freely :)

  • Like 3
Link to comment
Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...