AI agent field catalogue

Every control in the editor, the table's settings and the /play lobby has an id. An agent reads a control with fields_get and sets it with fields_set, and the change goes through that control's own handler. It is the same path your click takes.

The catalogue below lists every id, grouped by panel. A panel is one area of the screen, such as the Inspector's Rigidbody section or the Preferences dialog. Each panel says how a person opens it. The list comes from the same registry the site uses, so it can't drift from the app.

What is an instance id?#

Some fields belong to one thing, such as one entity or one file. Their id ends with @ and that target. For example, the mass of entity obj_12 is inspector.rigidbody.mass@entity:obj_12. A texture's filter setting is item.texture.sampling.filtering@asset:textures/felt.png.

You don't need to build these by hand. fields_list returns them ready to use. A field that exists only once, like the lobby's search box, has no @ part.

Why does fields_set say not-mounted?#

Most fields exist only while their panel is open, and while its target is selected. A closed field answers not-mounted. Pass autoOpen: true to open the panel for you, or open it first with panel_open.

Values and classes#

Values. Lengths are in feet unless you pass a unit. Colors from a color picker are [r, g, b], each from 0 to 1. A select takes one of its listed options. Every value is checked and never quietly changed to fit. A value out of range is refused, and the error tells you the range.

Classes. Fields and actions carry the same class letters as tools. fields_set refuses a field marked D or H and names the tool to use instead. Through actions_invoke, a D action needs confirm: true, and an H action asks you in the tab first. Actions that need your click explains why.

Families of fields. Some panels make one field per item instead of a fixed list. Engine component properties (component.<type>.<key>), material settings (material.<section>.<key>), room lights, plugin settings (plugin.setting.<key>), script variables (script.var.<name>) and the image editor's dialogs work this way. The panels that carry them show the pattern. The exact keys come from fields_list.

Related#

• AI agent tool reference: every tool, including describe_panel and actions_list.
• Let an agent edit your scene: these ids at work.
• AI agent error codes: what not-mounted, out-of-range and focused-by-user mean.

Panel index#

194 panels, 1070 static fields, 116 derived fields and 823 actions. Each panel's full entry (every field id, kind, unit, target, class and range, and its actions) is on its group's page. The groups are listed first, then every panel.

Field groups#

All panels#

Tab: the kind of DiceyTable tab the panel lives in. Fields counts static and derived fields; per-instance families are listed on the panel.