Skip to main content
Script menu elements. Appear in the cheat menu under a tab named after the script.
All element constructors are available on ui, on tab objects, and on group objects. Both tab:group(...) and tab.group(...) work.

Constructors

Element methods

Built-in menu controls: ui.find

Scripts can read and drive the cheat’s own menu controls. The path is the control’s location in the menu, in English, from the root: section, tab, sub-tab (if any), group, popup title / titled popup section (if the control lives in a popup), control name. Matching is case-insensitive.
Copy Path. Turn on Developer Mode in the user popup (click your name at the bottom of the sidebar), then right-click any control: the hotkey popup gets a Copy Path row that copies the exact ui.find(...) call for that control to the clipboard, e.g. ui.find("Aimbot", "Rage", "Main", "Enabled"). Right-clicking the row copies it with single quotes. ui.find works whether the menu is open or closed.

Control reference methods

Value types: toggle → boolean; slider → number (integer for integer sliders); combo → item name (an index is also accepted when setting); multi-combo → table of item names. These raise an error on built-in controls (as in the original API, they only work on elements your script owns): set_name, set_icon, set_items, import ("script does not own this element"), set_tooltip ("cannot change the tooltip of the default menu item"), color_picker / color_set / color_modes, chip ("chips can only be added to entity elements"), get_category / set_category / get_categories ("option is not a color picker").

Extra roots

Input table (custom/widget)

The input argument passed to custom draw callbacks:

Example