> For the complete documentation index, see [llms.txt](https://docs.autowall.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autowall.fun/documentation/basic-types.md).

# Basic Types

## Basic Types

### Positions

Anywhere a function takes a screen position (`render.text`, `render.line`, ...), pass either:

```lua
{ 10, 20 }          -- array style, x=1st, y=2nd
{ x = 10, y = 20 }  -- named style
```

Both are accepted interchangeably by every `render.*` function.

### Colors

Two accepted forms everywhere a color is expected — see [Color](/documentation/vars/color.md#passing-colors-to-render):

```lua
{ 1, 1, 1, 1 }        -- 0..1 float array
color(255, 255, 255)  -- 0..255 color() object (see Color)
```

### nil-checking

{% hint style="warning" %}
`entity.get_local_player()` and friends return `nil` when there's no valid player (not in a match, dead, etc.) — always check before using.
{% endhint %}

```lua
local player = entity.get_local_player()
if not player then return end
```

### Vectors

See [Vector](/documentation/vars/vector.md) — `vector(x, y, z)` and everything `entity.get_origin(...)` returns.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.autowall.fun/documentation/basic-types.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.