Skip to content
View in the app

A better way to browse. Learn more.

OSBot :: 2007 OSRS Botting

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Ability to destroy webwalking after use

Featured Replies

1. I suggest that we should have an method call in the API to allow for scripts to destroy the web walking and for it to be reinitialized upon a later date (i.e when it is used again or when a new script is started), or simply a method of reducing the client's ram use.


 


2. This will allow scripters to have the freedom of choosing whether they no longer require web-walking in their script and therefore can reduce the client's ram massively, allowing for more efficient scripts to be produced and used on OSBot. It is the scripters responsibility to understand when and when not to use this call, just like any other API call.


 


On a side note, OSBot performs incredibly well in resources, except for the fact the web walker takes a massive amount of ram up, while I understand the necessity for the web walker, it is not required in every script and at all times.


 


I'm not particularly interested in dealing with scripts that incorrectly destroy web walking resources. Simply don't call web walking at any point in your script, and you should be fine. 

 

I'll leave this open for some modest discussion. If you're not a scripter, please don't post in this thread. 

  • Author

I'm not particularly interested in dealing with scripts that incorrectly destroy web walking resources. Simply don't call web walking at any point in your script, and you should be fine. 

 

I'll leave this open for some modest discussion. If you're not a scripter, please don't post in this thread. 

 

The Scripter rank should certify that the person is knowledgeable on how to appropriately and correctly use the API.

 

There are people going to our competitors simply because OsBot is more resource hungry, our client performs well however uses much more memory than other clients. I'm proposing a way to circumvent unwanted memory use, I'm not really in a position to suggest optimizations but this seems to be the apparent solution.

I am not ranked as a scripter, but I do have my fair share of experience writing for many 07rs clients going way back to SCAR/SRL days

 

Quite recently I have realized how much I was able to improve my bot stability ( and resource usage ) by removing all webwalking from my scripts and convert them to static paths. The memory usage dropped from 600+mb to only 250mb per client. However, by doing so I lost the ability of recovering my players position when stuck by using webwalking.

 

As the OP stated it would be nice, if we could have the ability to clean up the webwalking resources once it is no longer in use

 

- Abuse

Guest
This topic is now closed to further replies.

Recently Browsing 0

  • No registered users viewing this page.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.