PathFinder status

[LogicParrot]

The interface looks good, only I'd expect it to be used as a value type rather than a reference type, so no new.

Updated the usage example.

---

Better wrap vector<Vector3d>* with a path class, the user might be interested in knowing path length, etc.

---

is querying cWorld for blocks expensive? should I cache the state of blocks inside the pathFinder? (Whether they're solid or not)