Rotations

rotations is client.rotations(). An applied rotation is written verbatim into the next movement packet, so the server sees it; the client no longer snaps it to the mouse grid for you, and rotations.quantized(rotation) is what gives you the angle that will actually be sent.

on<PrePlayerTickEvent> {
    val target = combat.target() ?: return@on
    val aim = rotations.quantized(rotations.lookAt(target))
    rotations.apply(aim, RotationOptions.DEFAULT.priority(RotationPriority.NOW))
}

#Reading angles

Every method throws ScriptStateException with no player or world.

#Building one

quantized moves both yaw and pitch onto the mouse step, unwraps the yaw into the player's frame and clamps the pitch to -90..90 degrees. Raycasting the quantised value checks the exact angle you are about to apply.

Rotation itself is on Vectors, boxes, angles; the attack points are on Interaction.

#Applying it

Applied at the next pre-player-tick exactly as given; one call covers one tick. Does nothing while another rotation holds the handler lock, and throws ScriptStateException with no player or world.

#Options

The record is immutable: every setter returns a copy and DEFAULT never changes. The deprecated members are indexed under Things that no longer do anything.

#Order inside a tick

#RotationPriority

Rotations queued in one tick are applied LATER → NORMAL → NOW, so the highest priority is written last.

#Returning the head

Once nothing applies a rotation any more, the handler walks the spoofed head back to the camera with the BackRotation of the last applied options.

#Writing your own

from is where the spoofed head points, to is where the real camera points, tick counts from 0. Your steps are applied verbatim, so quantise them yourself; the handler ends the return once maxTicks is reached.