Crate fmc_client_api

Crate fmc_client_api 

Source

Modules§

math
prelude

Macros§

register_plugin

Structs§

Friction
KeyboardKey
SurfaceFriction

Enums§

Key
TODO: The client can map keys, is it best to handle this only host side? Eventually the wasm should handle the interfaces which means it needs complete access to the keyboard anyways.

Traits§

Plugin

Functions§

delta_time
get_block
Get the id of a block in the world map
get_block_aabb
Get the aabb of the block
get_block_friction
Get the friction of a block
get_block_name
Get the name of a block
get_camera_transform
get_model_aabb
Get the aabb a model
get_models
Get the models inside the aabb defined by min and max
get_player_transform
keyboard_input
log
set_camera_transform
set_player_transform