From a6ccb2028fa41ad88becb9c826a91b3aa490ee2b Mon Sep 17 00:00:00 2001 From: Bituvo Date: Sun, 21 Apr 2024 10:01:15 -0400 Subject: [PATCH] Use inline codeblocks --- doc/lua_api.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/lua_api.md b/doc/lua_api.md index e2b1e2c7d..de8cfee65 100644 --- a/doc/lua_api.md +++ b/doc/lua_api.md @@ -7695,11 +7695,11 @@ child will follow movement and rotation of that bone. * `add_velocity(vel)` * Changes velocity by adding to the current velocity. * `vel` is a vector, e.g. `{x=0.0, y=2.3, z=1.0}` - * In comparison to using get_velocity, adding the velocity and then using - set_velocity, add_velocity is supposed to avoid synchronization problems. - Additionally, players also do not support set_velocity. + * In comparison to using `get_velocity`, adding the velocity and then using + `set_velocity`, `add_velocity` is supposed to avoid synchronization problems. + Additionally, players also do not support `set_velocity`. * If object is a player: - * Does not apply during free_move. + * Does not apply during `free_move`. * Note that since the player speed is normalized at each move step, increasing e.g. Y velocity beyond what would usually be achieved (see: physics overrides) will cause existing X/Z velocity to be reduced.