> For the complete documentation index, see [llms.txt](https://levno-710.gitbook.io/prometheus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://levno-710.gitbook.io/prometheus/getting-started/the-config-object.md).

# The Config Object

{% hint style="info" %}
**Legacy mirror:** Prometheus documentation has moved to [**https://prometheus-lua.github.io/Prometheus/docs/**](https://prometheus-lua.github.io/Prometheus/docs/).\
This GitBook remains online for existing links/search results and may not always reflect the latest changes.
{% endhint %}

Prometheus takes a configuration objetct. In this object there can be many properties applied.\
The following table provides an overview:

| Property      | type    | possible values                              | default           |
| ------------- | ------- | -------------------------------------------- | ----------------- |
| LuaVersion    | string  | "Lua51", "LuaU"                              | "Lua51"           |
| PrettyPrint   | boolean | true, false                                  | false             |
| VarNamePrefix | string  | any                                          | ""                |
| NameGenerator | string  | "Mangled", "MangledShuffled", "Il", "Number" | "MangledShuffled" |
| Seed          | number  | any                                          | 0                 |
| Steps         | table   | StepConfig\[]                                | {}                |

As this table shows, all properties in the config object are optional as they have a default value.

As an example, here is the code for the minify preset:

```lua
{
        -- The default LuaVersion is Lua51
        LuaVersion = "Lua51";
        -- For minifying no VarNamePrefix is applied
        VarNamePrefix = "";
        -- Name Generator for Variables
        NameGenerator = "MangledShuffled";
        -- No pretty printing
        PrettyPrint = false;
        -- Seed is generated based on current time
        Seed = 0;
        -- No obfuscation steps
        Steps = {
        
        }
    };
```

### Steps

The most important property is the Steps property. This property must be a table of so called Step Configs. A Step in Prometheus describes a single transformation applied to your script by the Prometheus obfuscation pipeline. A StepConfiguration consists of the Name of the Step as well as settings for the step. All Steps will later be applied in the order they are defined. A single Step can be defined twice and will then be applied twice.

```lua
-- Obfuscation steps
Steps = {
    {
        -- This obfuscation step puts all constants into an array at the beginning of the code
        Name = "ConstantArray";
        Settings = {
            -- Apply to Strings only
            StringsOnly = true;
            -- Apply to all Constants, 0.5 would only affect 50% of strings
            Treshold    = 1;
        }
    },
}
```

Under [Steps](https://github.com/Levno710/Prometheus/blob/develop/doc/getting-started/broken-reference/README.md), you can find all current Steps, their names as well as the possible options.


---

# 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://levno-710.gitbook.io/prometheus/getting-started/the-config-object.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.