Changes

! width="4050" | ''0B1 / B2''! width="4050" | ''0B3 / B4''! width="4080" | ''X''! width="4080" | ''Y''! width="4080" | ''ZI''! width="4080" | ''HSteps''

* '''const Bit[4]''' ''B3'': Bank to retrieve Z-coordinatetriangle ID, or zero if specifying ''Z'' as a literal value.

* '''const Short''' ''ZI'': Z-coordinate Triangle ID of the target to jump to, or lower byte specifying address if ''B3'' is non-zero.* '''const UShort''' ''HSteps'': Height of the Steps in jump. Must be non-zero if a literal value. Alternatively, lower byte specifies address if ''B4'' is non-zero.

Causes the character to jump to the specified pointand triangle ID, with the jump curve peaking at a height which is increased by using a larger value for the '''H''' argument. In addition, the larger the number, the longer the jump will take to complete. A "normal" value is around 0x15, 0x01 is fast and instantaneous; the argument must not be zero or the game will crash. Whilst this is an unsigned two-byte number, a large value (beyond around 0x60) will not only cause a vast jump height, but also cause the screen to scroll erratically (the larger the number, the more erratic). Main update function go through all entity with JUMP state and if stage is 0 it calculates final Z point according to triangle id. It sets current coords as start coords. The main thing this function does is set B coefficient for later calculation.It defines as follows: B = (Z_final - Z_start) / steps - steps * 1.45; Then it set current step to 0 and stage to 1. On next update other part of function works. It's calculate real position.First it increment current step number. Then it calculate X and Y. They change linear so nothing interesting here. Then here we go... Z calculation: Z_current = - step^2 * 1.45 + step * B + Z_start; If current substep equal number of steps then we set current triangle to final triangle and set stage to 2. Which finilize routine on next opcode call.