Does Astar allow you to define custom passability and movement costs setting on the grid? For example, can I mark the cell at (x, y) as impassable or assign a higher traversal cost for the cell at (x1, y1) from the code? And then rescan grid by calling some function?
Can I avoid completely colliders and rather use code based approach?
I’m pretty sure you’re looking for the ITraversalProvider interface, documented here? You can use this to check for if something can be traversed and it’s associated cost. This interface is actually getting an update in an upcoming path, by the way. Not in a way that will make any of this discussion change, but just an important note .