You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed in the findPath function the js will return if the endpoint isn't traversable. I'm interested in a state of affairs where a character might interact with a tile that isn't traversable (say, finding a tree with the purpose of cutting it down and get wood, finding a rock to break it and get stone, etc.). Is there any reason I should avoid removing these lines of code if I'm not concerned about whether the endpoint is walkable?
The text was updated successfully, but these errors were encountered:
I noticed in the findPath function the js will return if the endpoint isn't traversable. I'm interested in a state of affairs where a character might interact with a tile that isn't traversable (say, finding a tree with the purpose of cutting it down and get wood, finding a rock to break it and get stone, etc.). Is there any reason I should avoid removing these lines of code if I'm not concerned about whether the endpoint is walkable?
The text was updated successfully, but these errors were encountered: