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

# README

Configure classes, skill trees, quests, leveling, effects, and presentation without making the client authoritative.

This handbook describes **StellarSkills 5.15.0**, Minecraft **1.21.1**, and skills network protocol **20**, checked against the source and packaged defaults on **October 11, 2026**. The server declares Pixelmon `[9.4.0,9.5)` compatibility. The current StellarEngineNoUI client declares `[9.4.1,9.5)`. Match the actual client pack as well as the server; this is not a 9.3.1.6 handbook.

The custom interfaces belong to **StellarEngineNoUI**, whose displayed mod name is StellarEngine. Do not install another StellarEngine or the old standalone skills client alongside it. Client version numbers cover the entire suite; compatibility with these skills screens requires protocol 20, not a matching server/client version number.

## Start here

{% stepper %}
{% step %}

## [Install and check compatibility](/stellarskills-docs/getting-started/installation.md)

{% endstep %}

{% step %}

## [Build your first class, quest, and skill tree](/stellarskills-docs/getting-started/first-server.md)

{% endstep %}

{% step %}

## [Understand configuration files and safe publishing](/stellarskills-docs/configuration/files-and-workflow.md)

{% endstep %}

{% step %}

## [Set levels and skill-point rewards](/stellarskills-docs/leveling.md)

{% endstep %}

{% step %}

## [Create quests and branching stories](/stellarskills-docs/quests.md)

{% endstep %}
{% endstepper %}

## Important boundaries

* The server owns costs, effects, progress, class eligibility, Hero rolls, conflicts, and editor permissions. A modified client cannot publish unauthorized changes.
* `objectives.yml` now contains XP-paying quests. Its filename and `objectives:` root are retained for compatibility.
* Existing automatic XP sources and Journey rewards are separate from quests. Disable or rebalance them when designing a quest-only economy.
* Not every registered effect has a native gameplay hook. The effect catalogue distinguishes a declared schema from source evidence of an actual consumer.
* Defaults are examples, not a balancing recommendation. Review optional integrations, command-based permissions, and direct currency awards before enabling them.
* The RPG HUD is disabled in the packaged settings. Keep it disabled unless you intentionally test it.

## What is included

The book contains operational guides, complete command and permission references, examples, all 297 registered effect schemas and their fields, every packaged theme, all packaged tree/graph pairs, full default configuration snapshots, language references, integration boundaries, and migration/troubleshooting procedures.

References are generated from the current project, not from a running server. They contain no private server configuration, player database, passwords, or personal account data. Installation examples use placeholders rather than real credentials.

Read [implementation limits](broken://pages/12ec8068b199fa285efcee3c529130cd7a3d9dd9) before using advanced schema options. A setting appearing in a YAML reference is not proof that a separate system implements it.