valid_vid(3)

πŸ“¦
version 0.7.1 Β· 2 versions
, in nixos 26.05

🌸 NAME 🌸

OKAY SO bestie, valid_vid is literally the β€œcheck if vid matches a valid object or not” function, and it also accepts NULL/BADID arguments. This is the valid_vid(3) page from the Arcan Lua API, and the way that it handles your bad IDs? Iconic. πŸ’…

✨ SYNOPSIS ✨

true or false
valid_vid( vid, type )

It gives you true or false, no cap. ✨

πŸ’… DESCRIPTION πŸ’…

Here’s the design tea: the engine uses a numerical type to reference the internal engine type for most visible entities. Because of that, a number of situations arise where you might need to test if a specific numeric value maps to a corresponding engine object before calling some functions that require a valid VID β€” or even a valid VID that is also connected to a frameserver or other secondary processing types. It’s giving β€œvibe check before you commit,” and honestly? Obsessed. πŸ¦‹

πŸŽ€ NOTES πŸŽ€

  • 1 β€” Possible values for type are TYPE_FRAMESERVER and TYPE_ 3 DOBJECT . requirement

So yeah, those are the possible type values and that’s the requirement, fr fr. Periodt. πŸŽ€

πŸ¦‹ EXAMPLE πŸ¦‹

Look at this little example, bestie:

       function valid_vid0()
             a = fill_surface(32, 32, 255, 0, 0, 0);
             print(valid_vid(a));
             print(valid_vid(NULL));
             print(valid_vid(BADID));
       end

It prints the result for a, then for NULL, then for BADID β€” so you can see the true/false check in action. 🫢


mwah πŸ’‹ β€” this page comes from vidsys, dated October 2026, and it’s the valid_vid(3) manual page. Bye bestie, go check those VIDs 🫢✨

πŸ“¦ where this page comes from