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

# Commands and Permissions

IslandHologram provides one command:

```
/isholo <migrate|reload|toggle>
```

## Commands

| Command           | Permission         | Who should use it | Description                                                                                                                |
| ----------------- | ------------------ | ----------------- | -------------------------------------------------------------------------------------------------------------------------- |
| `/isholo migrate` | `hologram.migrate` | Administrators    | Registers all existing SuperiorSkyblock2 islands in the IslandHologram database.                                           |
| `/isholo reload`  | `hologram.reload`  | Administrators    | Reloads the plugin configuration, despawns active holograms, switches provider if needed, and re-registers stored islands. |
| `/isholo toggle`  | `hologram.toggle`  | Island owners     | Enables or disables the player's own island hologram.                                                                      |

## Permissions

| Permission         | Default | Description                       |
| ------------------ | ------- | --------------------------------- |
| `hologram.use`     | `true`  | Allows using `/isholo`.           |
| `hologram.migrate` | `op`    | Allows running `/isholo migrate`. |
| `hologram.reload`  | `op`    | Allows running `/isholo reload`.  |
| `hologram.toggle`  | `true`  | Allows running `/isholo toggle`.  |

## Permission Plugin Example

Example permissions for administrators:

```
hologram.use
hologram.migrate
hologram.reload
hologram.toggle
```

Example permissions for normal players:

```
hologram.use
hologram.toggle
```

## Migration Workflow

Use `/isholo migrate` after installing IslandHologram on a server that already has islands.

{% stepper %}
{% step %}

## Install IslandHologram.

Install IslandHologram.
{% endstep %}

{% step %}

## Start the server.

Start the server.
{% endstep %}

{% step %}

## Confirm there are no startup errors.

Confirm there are no startup errors.
{% endstep %}

{% step %}

## Run `/isholo migrate` as an administrator.

Run `/isholo migrate` as an administrator.
{% endstep %}

{% step %}

## Wait for the migration complete message.

Wait for the migration complete message.
{% endstep %}

{% step %}

## Visit an island and confirm the hologram appears within spawn-radius.

Visit an island and confirm the hologram appears within spawn-radius.
{% endstep %}
{% endstepper %}

If a player sees `Your island hologram is not registered yet`, run `/isholo migrate`.

## Toggle Behavior

Only the island owner can use `/isholo toggle` for their island.

When disabled:

* the hologram is despawned if it is currently visible;
* the disabled state is saved to SQLite;
* the hologram remains disabled across restarts.

When enabled:

* the disabled flag is removed;
* the hologram spawns again when a player is within `proximity.spawn-radius`.


---

# 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://advion.gitbook.io/advion-docs/commands-and-permissions-1.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.