> For the complete documentation index, see [llms.txt](https://lua2.fatality.win/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lua2.fatality.win/api/instances/gui/control/controltype.md).

# ControlType

This enum determines the current control's type.

{% hint style="success" %}
You can only construct types that are listed below in the navigation, and only if those have a constructor.
{% endhint %}

## DEFAULT <a href="#default" id="default"></a>

[<kbd><mark style="background-color:purple;">**Field**<mark style="background-color:purple;"></kbd>](#user-content-fn-1)[^1]

Default control. You are very unlikely to ever stumble upon this type.

***

## BUTTON <a href="#button" id="button"></a>

[<kbd><mark style="background-color:purple;">**Field**<mark style="background-color:purple;"></kbd>](#user-content-fn-1)[^1]

Button control.

***

## CHECKBOX <a href="#checkbox" id="checkbox"></a>

[<kbd><mark style="background-color:purple;">**Field**<mark style="background-color:purple;"></kbd>](#user-content-fn-1)[^1]

Checkbox control.

***

## CHILD\_TAB <a href="#child-tab" id="child-tab"></a>

[<kbd><mark style="background-color:purple;">**Field**<mark style="background-color:purple;"></kbd>](#user-content-fn-1)[^1]

Child tab control. Only possible to find within `tab_layout` controls.

***

## COLOR\_PICKER <a href="#color-picker" id="color-picker"></a>

[<kbd><mark style="background-color:purple;">**Field**<mark style="background-color:purple;"></kbd>](#user-content-fn-1)[^1]

Color picker control.

***

## COMBO\_BOX <a href="#combo-box" id="combo-box"></a>

[<kbd><mark style="background-color:purple;">**Field**<mark style="background-color:purple;"></kbd>](#user-content-fn-1)[^1]

Combo box control.

***

## CONTROL\_CONTAINER <a href="#control-container" id="control-container"></a>

[<kbd><mark style="background-color:purple;">**Field**<mark style="background-color:purple;"></kbd>](#user-content-fn-1)[^1]

Default control with a container. You are very unlikely to ever stumble upon this type.

***

## GROUP <a href="#group" id="group"></a>

[<kbd><mark style="background-color:purple;">**Field**<mark style="background-color:purple;"></kbd>](#user-content-fn-1)[^1]

Groupbox control.

***

## HOTKEY <a href="#hotkey" id="hotkey"></a>

[<kbd><mark style="background-color:purple;">**Field**<mark style="background-color:purple;"></kbd>](#user-content-fn-1)[^1]

Hotkey input control.

***

## HSV\_SLIDER <a href="#hsv-slider" id="hsv-slider"></a>

[<kbd><mark style="background-color:purple;">**Field**<mark style="background-color:purple;"></kbd>](#user-content-fn-1)[^1]

HSB slider (Saturation/Brightness box, Hue slider and Opacity slider).

***

## LABEL <a href="#label" id="label"></a>

[<kbd><mark style="background-color:purple;">**Field**<mark style="background-color:purple;"></kbd>](#user-content-fn-1)[^1]

Label control.

***

## LAYOUT <a href="#layout" id="layout"></a>

[<kbd><mark style="background-color:purple;">**Field**<mark style="background-color:purple;"></kbd>](#user-content-fn-1)[^1]

Layout control.

***

## LIST <a href="#list" id="list"></a>

[<kbd><mark style="background-color:purple;">**Field**<mark style="background-color:purple;"></kbd>](#user-content-fn-1)[^1]

Listbox control.

***

## LOADING <a href="#loading" id="loading"></a>

[<kbd><mark style="background-color:purple;">**Field**<mark style="background-color:purple;"></kbd>](#user-content-fn-1)[^1]

Loading spinner.

***

## NOTIFICATION\_CONTROL <a href="#notification-control" id="notification-control"></a>

[<kbd><mark style="background-color:purple;">**Field**<mark style="background-color:purple;"></kbd>](#user-content-fn-1)[^1]

Notification item control. One of the types in the core UI framework, never actually used within Fatality.

***

## POPUP <a href="#popup" id="popup"></a>

[<kbd><mark style="background-color:purple;">**Field**<mark style="background-color:purple;"></kbd>](#user-content-fn-1)[^1]

Basic popup window.

***

## SELECTABLE <a href="#selectable" id="selectable"></a>

[<kbd><mark style="background-color:purple;">**Field**<mark style="background-color:purple;"></kbd>](#user-content-fn-1)[^1]

Basic selectable item.

***

## SLIDER <a href="#slider" id="slider"></a>

[<kbd><mark style="background-color:purple;">**Field**<mark style="background-color:purple;"></kbd>](#user-content-fn-1)[^1]

Slider item. This type doesn't tell the internal value type used.

***

## SPACER <a href="#spacer" id="spacer"></a>

[<kbd><mark style="background-color:purple;">**Field**<mark style="background-color:purple;"></kbd>](#user-content-fn-1)[^1]

Spacer control.

***

## TAB <a href="#tab" id="tab"></a>

[<kbd><mark style="background-color:purple;">**Field**<mark style="background-color:purple;"></kbd>](#user-content-fn-1)[^1]

Horizontal or vertical tab.

***

## TABS\_LAYOUT <a href="#tabs-layout" id="tabs-layout"></a>

[<kbd><mark style="background-color:purple;">**Field**<mark style="background-color:purple;"></kbd>](#user-content-fn-1)[^1]

A variant of `layout` that is used specifically to operate tabs.

***

## WEAPON\_TABS\_LAYOUT <a href="#weapon-tabs-layout" id="weapon-tabs-layout"></a>

[<kbd><mark style="background-color:purple;">**Field**<mark style="background-color:purple;"></kbd>](#user-content-fn-1)[^1]

A variant of `layout` that is used specifically to operate weapon tabs.

***

## TEXT\_INPUT <a href="#text-input" id="text-input"></a>

[<kbd><mark style="background-color:purple;">**Field**<mark style="background-color:purple;"></kbd>](#user-content-fn-1)[^1]

Text input control.

***

## TOGGLE\_BUTTON <a href="#toggle-button" id="toggle-button"></a>

[<kbd><mark style="background-color:purple;">**Field**<mark style="background-color:purple;"></kbd>](#user-content-fn-1)[^1]

A variant of button that looks like button, but works like a checkbox.

***

## WINDOW <a href="#window" id="window"></a>

[<kbd><mark style="background-color:purple;">**Field**<mark style="background-color:purple;"></kbd>](#user-content-fn-1)[^1]

Basic window control.

***

## WIDGET <a href="#widget" id="widget"></a>

[<kbd><mark style="background-color:purple;">**Field**<mark style="background-color:purple;"></kbd>](#user-content-fn-1)[^1]

Basic widget control.

***

## SETTINGS <a href="#settings" id="settings"></a>

[<kbd><mark style="background-color:purple;">**Field**<mark style="background-color:purple;"></kbd>](#user-content-fn-1)[^1]

Settings control.

***

## IMAGE <a href="#image" id="image"></a>

[<kbd><mark style="background-color:purple;">**Field**<mark style="background-color:purple;"></kbd>](#user-content-fn-1)[^1]

Image control.

***

## LUA <a href="#settings" id="settings"></a>

[<kbd><mark style="background-color:purple;">**Field**<mark style="background-color:purple;"></kbd>](#user-content-fn-1)[^1]

Lua control.

***

## LUA\_CONTAINER <a href="#settings" id="settings"></a>

[<kbd><mark style="background-color:purple;">**Field**<mark style="background-color:purple;"></kbd>](#user-content-fn-1)[^1]

Lua container control.

***

[^1]: This field is a regular field that must be accessed using a dot (.)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://lua2.fatality.win/api/instances/gui/control/controltype.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.