> For the complete documentation index, see [llms.txt](https://docs.flatredball.com/flatredball/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flatredball.com/flatredball/glue-reference/variables/glue-reference-variable-order.md).

# Variable Order

### Introduction

Variables in Glue are not automatically ordered alphabetically. The reason for this is because the order that variables appear in Glue impacts the order that they are set in Glue's generated code. Instead, variables can be reordered through the "Move" commands when right-clicking on a variable in Glue:

![MoveCommandsRightclick.png](https://951240982-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_fye9Ufg3vzJxwX5Hk%2Fuploads%2Fgit-blob-401d40e18ba4e60e1207854ef1959312171b2d64%2Fmigrated_media-MoveCommandsRightclick.png?alt=media)

### When does order matter

The order of variables does not matter in most cases; however, it can matter in some. For example consider an object that contains an object that is an Entire Scene. In this situation one Sprite in the entire Scene has a special purpose and will at times be visible when the entire Scene is invisible, or will be invisible when the entire scene is visible. To accomplish this, you would need two tunneled variables - one that tunnels into the Scene's Visibility, one that tunnels into the the Sprite's visibility. However, setting the Scene's Visible property is just a shortcut way of setting the visibility of all objects. Therefore, the special Sprite (which is part of the Scene) must have its Visible property set **after** the Scene's Visible property is set.


---

# 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://docs.flatredball.com/flatredball/glue-reference/variables/glue-reference-variable-order.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.