Tom

Hi Guys, noticed there is currently an issue with the looting feature that may cause clients to slow down and become unusable. Please try the latest dev version in the mean time, as I will be investigating this issue when I get home from work.

The new version is live now, so it should submit that error directly to me.

Those red outlines shouldnt be there when the script starts, can you try disabling the area selection (F2) once you start. The area will still be in place, just not visible. Theres another issue in this case where if the log gets spammed enough, not enough detail is given about the error. If you could do the exact same thing as soon as the error starts in the log it'd help a lot. If not, the next version has some advanced data tracking and will actually submit the error directly to me.

Hmm, perhaps it was in combat so it couldnt hop. I've got a new world hopper coming out that should hopefully be quicker

Please check the log, and show your settings. I was using this just before and it was fine

No new reports, so should be good to go Added

Apologies, for whatever reason OSBot stopped notifying me of new posts on this thread. I'm going to identify and fix this now

Hey I think it might be Mirror mode being broken since the last update? [INFO][11/02 09:58:52 AM]: Updated injection hooks for client revision : 185! [DEBUG][Bot #1][11/02 09:58:52 AM]: Initializing mirror client bot... Confirming with other scripters atm

All good. Only thing I can think of right now since there isnt an error would be ram / cpu usage for some reason. Guess ill have to run it for longer on my end

You mentioned you cant make any inputs, just confirming that you are aware OSBot will disable the inputs once a script has started, and you can re-enable them using this button:

Go ahead and close, thats really werird

So before you start the script, at the top right of the OSBot client, click open logger. This will open a seperate window that you can leave open somewhere else, so that when your client freezes, you can take a screenshot of that window. It will give me a good indication of whats going on.

that worked, thanks. If you leave the logger open that would help a lot as well

About OSTracker is a Client-Server implementation designed to track important data from people using your scripts. It has been designed in a way that allows multiple clients (scripts & users) to upload and store data to one server which runs standalone from OSBot and utilises MySQL 8. OSTracker is allowed on the SDN. Tracked Data (per user) Experience gained for all skills Items Received, Lost, or Spent (e.g. arrows and runes) Time ran Error logs (if setup) Future Data Script configurations Requirements For the server, you will need the following Java JRE 8+ (Download) MySQL Server 8 (Download) Ability to build the jar using maven A server to run OSTracker on OSTracker-Server code (Download) For the client, you will need the following A script The OSTracker client code within your script OSTracker-Client code (Download) Installation MySQL Server The MySQL 8 Server is the place all the user data is stored, and is required by OSTracker to function. MySQL Server should ideally be installed on the same server that the OSTracker server will run on, however that is not a requirement and it will work remotely with the correct setup on your end. If you are using a Linux based operating system, I would recommend looking up specific instructions for setting up MySQL Server. If you are using Windows, you can see the instructions below. OSTracker Server To run the OSTracker server, you will need a Windows/Linux-based server to run it on. Depending on your users, having a server is ideal as it will allow you to track data 24/7. Implementing the Server is quite easy using the instructions below. OSTracker Client The client implementation goes directly into your script, specifically into the onStart and onExit(), but you will need the entire OSTracker Client project source within your script. Instructions: Accessing the data There is no easy way to explain this, but you will at least need some experience with SQL to reliably view your data in the most accurate and effective way. Once you have connected to your MySQL Server, whether its through terminal or a third party software such as MySQL Workbench, you gain access to powerful queries that will allow you to view the tracked data in all sorts of ways. I have included some example queries below. Viewing all items received by all players in the last 24 hours SELECT username, itemname, status, sum(amount) AS cnt from `osbot-client`.`users` inner join `osbot-client`.`scriptitems` on `osbot-client`.`users`.id = `osbot-client`.`scriptitems`.user inner join `osbot-client`.`items` on `osbot-client`.`items`.id = `osbot-client`.`scriptitems`.item inner join `osbot-client`.`itemstatus` on `osbot-client`.`scriptitems`.itemStatus = `osbot-client`.`itemstatus`.id where status = "Received" and date > date_sub(date, INTERVAL 1 DAY) group by status, itemName having cnt > 1; Viewing Total Time Ran for all users in milliseconds SELECT username, sum(duration) from `osbot-client`.`runtimes` inner join `osbot-client`.`users` on `osbot-client`.`users`.id = `osbot-client`.`runtimes`.user group by username; Viewing Total Experience Gained for each user for a specific skill SELECT username, skillName, exp from `osbot-client`.`experiencegained` inner join `osbot-client`.`users` on `osbot-client`.`users`.id = `osbot-client`.`experiencegained`.user inner join `osbot-client`.`skills` on `osbot-client`.`skills`.id = `osbot-client`.`experiencegained`.skill WHERE skillName = "STRENGTH" group by username; Advanced Error Tracking It's possible to track and upload things such as Stacktraces which allows scripters to get ahead of issues quickly before users even report it, see the example below. In your onLoop, you could have something like the following try { // Logic Loop } catch (Exception e) { if (tracker != null) { StringWriter sw = new StringWriter(); PrintWriter pw = new PrintWriter(sw); e.printStackTrace(pw); tracker.getSessionTracker().getSession().addLog(sw.toString().replaceAll("\r", "").replaceAll("\n", "")); tracker.getSessionTracker().getSession().setVersion(getVersion()); } }

Ok, its affecting more than one person. What i meant by the above comment is to open the logger before you start the script, and you would still be able to see the output without clicking into it. I'll check it out myself, thx. I've been running for 20 minutes now and the client seems fine, could you please supply me with your config? It will be located in C:\Users\<your user>\OSBot\Data\OSFighter\config

Could u upload the config to pastebin pls, its located at C:\Users\User\OSBot\Data\osMiner\config I think ive submitted a fix in 1.27, it seems the areas I had defined were overlapping

Hey, doesnt sound good. There are a few options here that would help me diagnose the issue. If you open the logger before you start the script, it should have an error that you could screenshot when it freezes up. Alternatively, you can open OSBot in command prompt or powershell, even if the bot crashes, the error should be visible there. The command is java -jar "path/to/osbotfile.jar" -debug 5005

Yeah that shouldn't be happening. I'll look now. Just to confirm, you are selecting Extended Mining Guild as the location in the script as well, right? Added

The deposit box in port sarim? Or am i mistaken

Added

Could you have a look at the logger for me? May have indication of why its erroring

Fixed on my end, pending release

Yeah something is cooked, I'm off work in 2 hours or so and will go there myself Thanks

Could you have a look at the log (top right of bot client) for me, it may be full of errors I can use to assist.

The adamant is pending release, the webwalking issue seems OSBot related, I can't see why it would be happening