NodePath creation

Update: I changed nothing, it still shows as the same version, and it now magically works, and you are a coding god and I am but a peasant. Why does it work now? Hell if i know. How does it work? Thats a you problem! Either way, it works with zero lag which is exactly what I needed to buy Pro for. Thanks for taking my money :slight_smile:

Please advise on how to delete script-created codes and re-scan the area to kill connections?
(Get nodes in bounds → delete bounds → scan bounds + buffer area)

Either store nodes you created by code somewhere calculating for someway for nodes outside of the default bounds

I am unsure if you can destroy graph nodes even tho i see that there is a destroy() method that says it needs to be done from the graph directly instead.

You can get those nodes as well using graph.GetNodesInRegion(Bounds b);

Incase your missing a few connections you can go through all of the connections for each node like this
var connections = new List();
node.GetConnections(connections.Add);

At worst case can set walkability to false for those

In the current version you can only make them unwalkable.

In the next update, it will be possible to use pointGraph.RemoveNode for this.

1 Like