Not quite fixed

Unity Courses Talk
,
#1

In case anyone is following the video verbatim, note that when Ben “fixed” the error around 11m30s, he inadvertently swapped the order of adding the path element and getting the next waypoint, which means the final block in the path (right by the player’s base) is not actually added to the path.

So this:

    previous = previous.exploredFrom;
    SetAsPath(previous);

Should be this:

    SetAsPath(previous);
    previous = previous.exploredFrom;

Maybe this gets fixed later.

#2

Correction: I forgot that the end waypoint is added explicitly before the loop, so it’s actually the last non-end waypoint that is missing, hence the skipped waypoint just before the last one.

Anyway, I see that this bug is discovered and fixed in video 153 :slight_smile:

Privacy & Terms