What's New?

• Section offsets now support expressions
  • Example: ==Section:TopLeft, x + 5, x + 3==
  • Don't ask why your hud's position would change on your x coords... but.
  • For real though, it's intended use are values created with get/set variables
• Added Event Variables!
  • {on_join} - Is true for the first frame after joining a world
  • {on_load} - Is true for the first frame after the profile is (re)loaded
  • List var on_chat_message / on_chat_msg
    • Contains chat message received between last frame and now.
    • Same child vars as chat_messages
• New icon variable: {crosshair:<texture_path>}
  • Acts just like {icon:<texture_path>}, but renders how the crosshair renders
• Variables related to the freezing (staying in powdered snow):
  • {is_frozen} , {is_freezing} , {frozen_per} / {frozen_percentage} , {frozen_ticks}
• Is on fire: {on_fire}
• Attack Cooldown: {attack_cooldown}
• Added child variables for items related to cooldowns:
  • {i:cooldown} , {i:max_cooldown} , {i:cooling_down} , {i:cooldown_percentage} / {i:cooldown_per}
• Facing variables:
  • Added variables that display 8 directions instead of 4: {facing8} and {facing8_short}
    • north, northeast, east, southeast, south, southwest, west, northwest
  • {facing} and {facing_short} are now alias of {facing4} and {facing4_short}
• Velocity Variables have been overhauled
  • {velocity} is now an alias of {velocity_xyz}
  • You can now have any combination of XYZ (Ex: {velocity_x} and {velocity_xy})
  • Adding _kph to the end still works (Ex: {velocity_x_kph})
  • You can now also end it with _mph for miles per hour! (Ex: {velocity_x_mph})
  • You can now set a "smoothing" value from 0-19
    • A value below 0 will act as 0, and a value above 19 will act as 19. This also supports expressions!
    • Ex: {velocity_xz[4]}. This will compare the positions between now and 5 ticks ago to calculate the velocity)
    • Before, to make it more readable, it only updated every 5th render tick. However it's been a common request for it to update every tick. In v4, -freq# / -v# was added, which limits how fast a variable updates on the hud. Despite this sounding like it would be a good substitute for the old system, it is not, as it loses the "smoothing" that updating the actual change in distance would have