VP_EVENT_TERRAIN_NODE
Revision as of 04:18, 26 August 2013 by Roy Curtis (talk | contribs) (Created page with "{{sdk event page|terrain_node|Received for each node sent by the server after a {{sdk function|terrain_query}} call. |attributes= {{sdk attribute row|int |TERRAIN_TILE_X ...")
Event set and handler snippet
vp_event_set(instance, VP_EVENT_TERRAIN_NODE, event_terrain_node);
void event_terrain_node(VPInstance instance) { }
Received for each node sent by the server after a vp_terrain_query()
call.
Attributes
Attribute | Usage | |
---|---|---|
VP_TERRAIN_TILE_X | X of terrain tile node belongs to | |
VP_TERRAIN_TILE_Z | Z of terrain tile node belongs to | |
VP_TERRAIN_NODE_X | Node's X position relative to tile | |
VP_TERRAIN_NODE_Z | Node's Z position relative to tile | |
VP_TERRAIN_NODE_REVISION | Sent data's revision number | |
VP_TERRAIN_NODE_DATA | Node's terrain data |
Behavior
- Only nodes with a revision higher than what was provided to the
vp_terrain_query()
call will be sent - It should be expected that, at most, 16 nodes (where a tile is a 4 by 4 block of nodes) are sent per
vp_terrain_query()
call
Examples
- This event has no usage examples; please add at least one to this page