BugFix for when the path changes but the coroutine runs until the next yield statement, causing an error to throw when the pathIndex on line 62 is bigger than what the new path's turnBoundaries length. Checking with a hash means that at least most of the time this error doesn't come to pass, and is not resource intensive whatsoever on the method. The possibilities of having two paths with the same hash is something like 4.2 billion as is the number of int, so there is an eventual chance of collision. A more surefire method would probably be to add some kind of pathID to the Path class and check against that, but I'm not invested enough to figure that out yet. :)
BugFix for when the path changes but the coroutine runs until the next yield statement, causing an error to throw when the pathIndex on line 62 is bigger than what the new path's turnBoundaries length. Checking with a hash means that at least most of the time this error doesn't come to pass, and is not resource intensive whatsoever on the method. The possibilities of having two paths with the same hash is something like 4.2 billion as is the number of int, so there is an eventual chance of collision. A more surefire method would probably be to add some kind of pathID to the Path class and check against that, but I'm not invested enough to figure that out yet. :)