input_capabilities(3)

💖 input_capabilities(3) 💖

okay so this is the Arcan Lua API page for input_capabilities, and bestie, it’s literally the “what input can this thing actually handle?” function. ✨

🌸 NAME 🌸

input_capabilities — query platform layer or target for input capabilities. 💅

✨ SYNOPSIS ✨

captbl, ident
input_capabilities( vid:fsrv )

🦋 DESCRIPTION 🦋

This function queries the platform — that’s the default — or a frameserver when you provide a valid fsrv argument. It asks for the current set of input capabilities in terms of devices (both cases) and data types (frameserver only). 👑

What comes back is a table where the keys are indexed with booleans that indicate whether the type is supported or not. Simple vibe: key goes in, boolean comes out, supported or nope. 🫶

A frameserver may update this mask for a segment at will. When the mask is changed, an "input_mask" event will be sent to the frameservers assigned event handler. This mask will be applied to samples provided through target_input. 🔥

For the platform, the set may also change when devices are added and removed in response to a device appearing and removing. So yeah, it’s lowkey alive like that. 🌈

The set of provided or accepted devices may be zero, one or many of the following — and I’m putting the exact spelling from the page here so nothing gets lost, no cap:

"keyboard, "mouse", "game", "touch", "position",
"orientation", "eyetracker"

The set of accepted datatypes may be zero, one or many of the following: "analog", "digital", "translated", "touch", "eyes". 🎀

🎀 EXAMPLE 🎀

function input_capabilities0()
      for k,v in pairs(input_capabilities()) do
            print(k, v);
      end
end

👀 SEE ALSO: 👀

• iodev — go peek, bestie. 🦋

---

that’s the whole page, bestie 🫶 — source/version says iodev, date is October 2026, and it’s the input_capabilities(3) page. periodt. 💜