Tom

Added

Unfortunately it seems like its not supported by OSBot's walking, perhaps @Patrickcould add it in a future update

Try bring a games necklace with you, OSBot may not know the pathing to / from there. So it may bank but not know the way back either

Hmm, what location are you in? Perhaps if you extend the logger at the bottom of the client it can provide me some info

Added

Added

There is no dialogue indicating that you saved, next time you run the script you can click load and it will load it back in

GitHub https://github.com/Tomhoogstra/OSTracker If you found this repository useful, please consider giving it a star! About In late 2019, OSTracker 1.0 was released which was a client-server implementation that strived to collect user data for scripters with ease. There were a few problems with this type of implementation, and most of them were performance related and mostly poor ways of communication between the client and the database. Today I am happy to release OSTracker 2.0, which transitions from this Client-Server approach to a RESTful API which allows for much easier and less intensive data submission and tracking. OSTracker 2.0 API is built on Laravel, a PHP framework that specialises in the development of web applications. 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) Upcoming Data retrieval end points that will allow you to filter certain users, scripts, skills, items, and more. Client-side installation Integration with your OSBot script is relatively simple. Simply copy the contents of the 'client' directory in this repo into your scripts code base. In your scripts onStart, you should initialise OSTracker like so. private Tracker tracker; @Override public void onStart(){ try { tracker = new Tracker(getBot(), getName(), "BASE_API_URL", "YOUR_TOKEN") .setUpdateInterval(30) // Defaults to an hour .start(); tracker.getSessionTracker().setVersion(getVersion()); } catch (Exception e) { if (tracker != null) { tracker.stop(); } e.printStackTrace(); } } And end the tracker in your scripts onExit like so @Override public void onExit(){ if(tracker != null){ tracker.stop(); } } Your token will be created when deploying the Laravel API to your server, or it will be provided to you if you are choosing to integrate with somebody else's API. From here, OSTracker will automatically handle experience, loot, and script runtime tracking, and by default will submit this data to the API once per hour. Data will also be submitted when the script is stopped. API installation Don't fancy setting all this up? I can host your data for you for $3 USD per month. Post-installation instructions / API endpoints

Assuming this is your first script on OSBot, if so, well done.

Added Sorry to hear

Its weird because the door opening code is already there for when it starts to run to level 30 wilderness, does the door shut as you start walking or something?

Added

New version is now live by the way

Added

Some of the images in the interface are from imgur I'll give you another trial, join my script support discord, invite is in my signature. I'd love to get to the bottom of these issues

Interesting, was there anything other than the teleport items in your inventory at this point? E.g. 1 bone

Lookin into this now. For the glory bug, make sure the glory is in your inventory when you START the script, and it will set your bank location for the rest of it. You may find that instead of banking in lumbridge though, it will walk all the way to edgeville. (not 100% certain on this one). If dying is happening frequently for you I would recommend just not using a glory at all. It is best when you have the respawn location set to edgeville (which costs 5m) Edit: I've submitted a fix for the bot getting stuck at bank as well, it may take up to 24 hours to get approved though. (Version 1.25, you can see the version in the logger when you start the script) Also slightly increased the delay for unnoting, let me know if it helps in the future

should

Added

Added your trial, refresh script selector

Thanks, It would be good if you could copy and paste the logger output here, it should explain what it is getting stuck on. (logger can be accessed top right of OSBot client)

When it gets stuck, can you elaborate on what its doing? is it trying to do a certain thing

Added

Added

I'll take a look