max_current_image_order(3)

📦
version 0.7.1 · 2 versions
, in nixos 26.05

okay bestie, buckle up for the manual page for max_current_image_order(3) — it's giving “where is the highest order value at?” energy, and honestly? iconic. 💅

💖 NAME 💖

max_current_image_order — find the highest ordervalue in use in the current context. No cap, that's the whole mission. ✨

✨ SYNOPSIS ✨

orderval
max_current_image_order( rtgt )

🌸 DESCRIPTION 🌸

So basically it scans a specific rendertarget — and yeah, the default is worldid — for the highest drawing order value that's currently being used. 🌈

Heads up, bestie: the range 65531..65535 is explicitly ignored. That's on purpose, so you can do relative operations like order_image(a, max_current_image_order() + 1); without objects used as overlays, cursors, or similar special targets interfering. Periodt. 💀

🎀 EXAMPLE 🎀

function max_current_image_order0()
      print(max_current_image_order());
      a = fill_surface(32, 32, 0, 0, 0);
      order_image(a, 65500);
      print(max_current_image_order());
      order_image(a, 65535);
      print(max_current_image_order());
end

🦋 SEE ALSO 🦋

shoutout to the image manual, October 2026 — that's the source/version and date, and she ate. 🫶💖

📦 where this page comes from