Use inline codeblocks

This commit is contained in:
Bituvo 2024-04-21 10:01:15 -04:00
parent fafcf86977
commit a6ccb2028f
1 changed files with 4 additions and 4 deletions

View File

@ -7695,11 +7695,11 @@ child will follow movement and rotation of that bone.
* `add_velocity(vel)` * `add_velocity(vel)`
* Changes velocity by adding to the current velocity. * Changes velocity by adding to the current velocity.
* `vel` is a vector, e.g. `{x=0.0, y=2.3, z=1.0}` * `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 * In comparison to using `get_velocity`, adding the velocity and then using
set_velocity, add_velocity is supposed to avoid synchronization problems. `set_velocity`, `add_velocity` is supposed to avoid synchronization problems.
Additionally, players also do not support set_velocity. Additionally, players also do not support `set_velocity`.
* If object is a player: * 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, * Note that since the player speed is normalized at each move step,
increasing e.g. Y velocity beyond what would usually be achieved increasing e.g. Y velocity beyond what would usually be achieved
(see: physics overrides) will cause existing X/Z velocity to be reduced. (see: physics overrides) will cause existing X/Z velocity to be reduced.