PathFinder status

[LogicParrot]

As for your questions, first let me note that a jump is a different thing than a spider's wallclimb/

From a path-finding perspective, they are the same. Perhaps the variable name I picked was terrible.

and we will need pathfinding for flying mobs, too, so you might want to include that in your analysis.

I did not take that into account. However, the Vanilla ghasts are rather dumb, we probably need primitive path-finding for that.

Assuming we do need A* for flying creatures, it would be actually easier than walking creatures. 3d a* actually works with complete disregard to ground-level, and implementing walking creatures is actually slightly harder because one must restrict the possible paths.

Also note that blocks in MC aren't just solid / non-solid, there are doors, trapdoors, fences, fencegates, halfslabs, stairs, soulsand, water and other special cases that will need some thinking about.

Yet they can all be summed up to "traversable" and "non-traversable", correct?

As for mobs, each entity has its size already defined in cEntity::GetWidth() and cEntity::GetHeight(); the entities use an axis-aligned bounding box with the same dimension in X and Z. The entity position is anchored in the center of the entity's bounding box's bottom side (MidX, LowY, MidZ).

Great

It might be better to get a function that gives you the block's "non-passable bounding box" based on the block's placement. You will need to take into account the non-integral coordinates used.

Why is that needed?