Jump to content
Frequently Asked Questions
  • Are you not able to open the client? Try following our getting started guide
  • Still not working? Try downloading and running JarFix
  • Help! My bot doesn't do anything! Enable fresh start in client settings and restart the client
  • How to purchase with PayPal/OSRS/Crypto gold? You can purchase vouchers from other users
  • Try asking for help in the chatbox
  • One ID many nodes. Bug or design?


    Recommended Posts

    I've noticed that it's possible to end up with multiple AbstractWebNode sharing the same node ID. This causes some interesting side effects.

    For example, tearing down custom nodes with clearCustomNodes() can also delete standard nodes without warning. A client restart is required to restore the original web.

    It happens when a node is added too close to an existing node (specifically less than 5 tiles).  I've implemented a proximity check as a workaround.

    Is this a bug or by design? Couldn't find any reference in the docs.


    Link to comment
    Share on other sites

    • 2 weeks later...
    On 4/3/2020 at 10:55 AM, yetanotherbot said:

    Thanks Nezz! Appreciate it.

    If it doesn't reproduce easily let me know and I'll put together a code sample.

    I'm going to add in some synchronization checks on the add/remove methods, maybe there's just a problem concurrency.

    It'll be in the next release, though I'm not sure when that release is going to be at the moment.

    Link to comment
    Share on other sites

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now
    • Create New...

    Important Information

    We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.