yetanotherbot 4 Share Posted April 3, 2020 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. Thanks Link to comment Share on other sites More sharing options...
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
Already have an account? Sign in here.Sign In Now