3D Mud Client

When the mud tells the mud client that the state of the mud has changed (eg cloud cover has increased), the mud client doesnt pop the new cloud cover straight into the sky. Instead there is a gradual transition from the current cloud cover to the new cloud cover. Thus there are two states. The state shown to the user in the mud client and the state as specified on the mud. The mud client will usually lerp to the mud state at a speed that is often configurable in the config file.

An example is in the mob element where the attributes 'movespeedbydist' (speed proportional to how far must travel), 'movespeedbyroomradius' (speed propertional to room radius) and 'movespeedbyconst' (speed is a constant) can be used to specify how fast a monster will move to the position specified by the mud. For example how fast will a dog move 0.1 east of the room centre after the mud sends the 3dtag {odog,prx0.1}.

For lerping of a player to a position specified by the mud there is the 'positionlerp' attribute in the movement element. For example this attributes specifies how fast the player will move 0.1 east of the room centre after being punched (eg {uprx0.1}). If positionlerp is high then a player will move more quickly 0.1 east of the room centre.

The speed at which a player faces the direction specified by the mud can be set in the 'directionlerp' attribute of the movement element. During a tutorial the mud might force a player to look in a certain direction (eg {ufe}). A higher 'directionlerp' value will make the player turn that direction faster.