New BlockTracer classes

[xoft]

No, all the functions in cBlockTracer::cCallbacks are available to Lua:

/** Called on each block encountered along the path, including the first block (path start)
When this callback returns true, the tracing is aborted.
*/
bool OnNextBlock(int a_BlockX, int a_BlockY, int a_BlockZ, BLOCKTYPE a_BlockType, NIBBLETYPE a_BlockMeta);

/** Called on each block encountered along the path, including the first block (path start), if chunk data is not loaded
When this callback returns true, the tracing is aborted.
*/
bool OnNextBlockNoData(int a_BlockX, int a_BlockY, int a_BlockZ);

/** Called when the path goes out of world, either below (a_BlockY < 0) or above (a_BlockY >= cChunkDef::Height)
The coords specify the exact point at which the path exited the world.
If this callback returns true, the tracing is aborted.
Note that some paths can go out of the world and come back again (parabola),
in such a case this callback is followed by OnIntoWorld() and further OnNextBlock() calls
*/
bool OnOutOfWorld(double a_BlockX, double a_BlockY, double a_BlockZ);

/** Called when the path goes into the world, from either below (a_BlockY < 0) or above (a_BlockY >= cChunkDef::Height)
The coords specify the exact point at which the path entered the world.
If this callback returns true, the tracing is aborted.
Note that some paths can go out of the world and come back again (parabola),
in such a case this callback is followed by further OnNextBlock() calls
*/
bool OnIntoWorld(double a_BlockX, double a_BlockY, double a_BlockZ);

/** Called when the path is sure not to hit any more blocks.
Note that for some shapes this might never happen (line with constant Y)
*/
void OnNoMoreHits(void);

/** Called when the block tracing walks into a chunk that is not allocated.
This usually means that the tracing is aborted.
*/
void OnNoChunk(void);

---

Care to document all this in the wiki?
Note: There will be a cParabolaBlockTracer later on that will use the same callbacks, but for a parabolic path, so it will be useful to document the callbacks separately