NodeLink2 jump calculations

[tealtxgr]

Interesting case So, I’ll answer your brainstorming solutions to the best of my ability but if none of these work out let me know!

@bjjkdci

Can I know which NodeLink2s the unit has on its calculated path and run the calculations while the unit is en route, block links that wont work, and recalculate the path?

You may get some mileage out of this thread, and this thread linked later in the first.

@bjjkdci

Could I do these calculations as the unit tries to traverse a link, abort if not viable, blacklist the node, and recalculate somehow? What would be a good way to blacklist them? Something similar to BlockManager?

Two options here methinks: Either turn off the NodeLink2 altogether if all your units share the same logic for off-mesh links (as in, your units are all the same in the sense that they can traverse the same links) or tag it appropriately for different units.

@bjjkdci

My simple brute solution would be running a series of tests from the NodeLink2 every time it updates for a range of jump powers so a unit could know if its within an acceptable range. These links can update quite frequently as they are on dynamic moving platforms and each platform will have a minimum of 4 links. So it would be a waste to constantly recalculate these (twice per: a start jump and an end jump) when units aren’t trying to reach them. Then again, I am far away from having performance matter.

I think this is where that logic about making something kinda… good enough is useful. You can maybe only update dynamically when they’re nearby a unit or something. That doesn’t work if your units can traverse the entire map, but you can also just lower the rate of how often it updates and have them be a little tiny bit jank every once in a while.