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

# commands permissions

The main command is:

```
/sg
```

## Commands

| Command                  | Description                                                                              | Permission    |
| ------------------------ | ---------------------------------------------------------------------------------------- | ------------- |
| `/sg reload`             | Reload StarGenerator config, tables, recipes, groups, vanilla recipes, and runtime data. | `sg.reload`   |
| `/sg get <table-id>`     | Give the player a table item.                                                            | `sg.get`      |
| `/sg opengui <table-id>` | Open a table GUI directly. Mainly useful for testing.                                    | `sg.opengui`  |
| `/sg saveitem <name>`    | Save the item in the player's main hand for recipe/config use.                           | `sg.saveitem` |
| `/sg starteditor`        | Start or refresh the local WebUI editor and print a tokenized link.                      | `sg.craftweb` |
| `/sg stopeditor`         | Stop the WebUI editor.                                                                   | `sg.craftweb` |

## Permissions

| Permission       | Default | Description                                                                           |
| ---------------- | ------- | ------------------------------------------------------------------------------------- |
| `sg.admin`       | `op`    | Grants all StarGenerator admin permissions.                                           |
| `sg.table.admin` | `op`    | Bypasses table owner protection.                                                      |
| `sg.table.place` | `true`  | Allows placing StarGenerator table entities.                                          |
| `sg.table.open`  | `true`  | Allows opening table entities when owner rules allow it.                              |
| `sg.table.break` | `op`    | Allows breaking unowned StarGenerator table entities.                                 |
| `sg.get`         | `op`    | Allows `/sg get`.                                                                     |
| `sg.reload`      | `op`    | Allows `/sg reload`.                                                                  |
| `sg.opengui`     | `op`    | Allows `/sg opengui`.                                                                 |
| `sg.saveitem`    | `op`    | Allows `/sg saveitem`.                                                                |
| `sg.craftweb`    | `op`    | Allows starting and stopping the WebUI editor.                                        |
| `sg.recipe.give` | `op`    | Allows the recipe GUI shortcut that gives recipe ingredients with shift double-click. |

## Saved Items

`/sg saveitem <name>` stores the held item so it can be used by recipes and tables.

Example:

```
/sg saveitem custom_fuel
```

Use saved items when exact item metadata matters, such as custom names, lore, custom model data, or provider-specific NBT.


---

# 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:

```
GET https://star-generator.gitbook.io/star-generator-docs/getting-started/commands-permissions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.