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

# Common Issues

<details>

<summary>The Admin panel won't open / shows empty</summary>

Confirm the player actually has permission — see [Admin Panel](broken://pages/88eda51354c0dbf8794ad23d5d06ab36ca8be7a0) for both ways to grant access (framework group or ACE). Double-check the group name you granted matches one listed in `Config.Admin.allowedGroups`.

</details>

<details>

<summary>"My Faction" / "Statistics" / "History" tabs are always empty</summary>

Two possible causes:

1. **The player has no gang/job** in your framework.
2. **No capture has happened yet.** These tabs are built entirely from real capture history — if no territory has ever changed hands, there's nothing to show yet. This is expected, not a bug.

</details>

<details>

<summary>Capture rewards (money/items/XP) aren't being delivered</summary>

Rewards require a small hook in your own scripts to actually add the money/items to the player — see [Integration](broken://pages/3b6d8b07152a7ec46ebbec7df238eae8120403f2) for the events to listen for and a working example. This is intentional: it keeps the resource compatible with any economy or inventory system instead of assuming one.

</details>

<details>

<summary>Recent changes disappear after a restart</summary>

Territory state saves automatically both periodically and immediately after every capture/admin action. If you still see data loss, confirm `Config.Persistence.enabled = true` in `config/config.lua` and that your database connection is working.

</details>

<details>

<summary>A territory defined in config/territories.lua can't be deleted from the tablet</summary>

This is expected — only territories created via the Admin panel can be deleted at runtime. To remove a territory defined in the config file, edit `config/territories.lua` directly and restart the resource.

</details>

<details>

<summary>Can I rename this resource's folder?</summary>

No — the tablet interface is built to communicate specifically with `ld_territories`. Renaming the folder will break the in-game tablet. If you need a different resource name for your setup, contact support.

</details>

<details>

<summary>How do I add a new language?</summary>

{% stepper %}
{% step %}

## Create the locale file

Create `config/locales/<code>.lua`, copying the structure of `en.lua`/`pt.lua`.
{% endstep %}

{% step %}

## Set the locale

Set `Config.Locale = '<code>'` in `config/config.lua`.
{% endstep %}
{% endstepper %}

</details>

<details>

<summary>How do I integrate a faction/identity system that isn't gang/job?</summary>

Set `Config.Identity.provider = 'custom'` and implement `Config.Identity.custom.GetPlayerGroup(source)` returning `{ type, name, label }`. See [Configuration](broken://pages/b227a0a2464be2c081b9614df303d209dcd27749) for details.

</details>


---

# 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.lostdev.store/territories/common-issues.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.