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

# First Setup

## 1. Activate your license

AtomCombat will not start without a valid license. Get one through the Aeros Discord bot with `/license claim`, then set it in `config.yml`:

```yaml
license:
  key: 'PULSE-XXXX-XXXX-XXXX'
```

* The licensing service address and re-check interval are built into the plugin — you only need to set `key`.
* The license is re-checked every hour while the server runs. If it becomes invalid (revoked, expired, bound to a different server IP, or issued for a different product), AtomCombat disables itself and logs the reason.
* If your license is bound to the wrong IP, use `/license reset-ip` on Discord (subject to a cooldown).

## 2. Pick a language

```yaml
language: es
```

This selects which file under `plugins/AtomCombat/languages/` is used for every player-facing message. AtomCombat ships `en.yml` and `es.yml`. See [Languages](/atomcombat/getting-started/language.md) to add your own wording or a new language.

## 3. Choose your storage

By default AtomCombat stores bounties and stats in plain YAML files — zero setup required. If you run a network or a busy server, see [Storage](/atomcombat/getting-started/storage.md) to switch to SQLite or MySQL.

## 4. Enable the modules you want

Every feature is a module you can turn on or off in `config.yml` under `modules:`. See [Modules](/atomcombat/getting-started/modules.md) for what each one does. All modules are enabled by default except `announcements`.

## 5. Verify everything

Run `/atomcombat debug` in-game (requires `atomcombat.admin`, granted to server operators by default) to see your license status and which soft-dependencies (Vault, LuckPerms, WorldGuard, PlaceholderAPI, PulsePrison, Discord) were detected.


---

# 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://mode-development.gitbook.io/atomcombat/getting-started/first-setup.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.