> ## Documentation Index
> Fetch the complete documentation index at: https://docs.purpify.host/llms.txt
> Use this file to discover all available pages before exploring further.

# AGENTS

# Purpify documentation instructions

## About this project

* This Mintlify site documents Purpify Minecraft hosting.
* Purpify supports Minecraft Java Edition, native Bedrock Edition, modded servers, and Geyser cross-play.
* The game panel is at `panel.purpify.host`.
* The billing portal is at `payments.purpify.host`.
* Pages are MDX files with YAML frontmatter. Navigation lives in `docs.json`.
* Run `mint dev` to preview locally.
* Run `mint broken-links`, `mint a11y`, and `mint validate` before publishing.

## Information architecture

* **Get started**: edition choice, first server, shared reference, and help.
* **Panel**: server creation, controls, console, files, SFTP, backups, and panel troubleshooting.
* **Java Edition**: connection, server software, plugins, mods, modpacks, and Geyser.
* **Bedrock Edition**: connection, Bedrock worlds, behavior packs, resource packs, and Bedrock troubleshooting.
* **Billing**: services, invoices, payments, renewals, cancellations, and policy links.

Put a topic in one canonical section. Cross-link it instead of duplicating the same procedure.

## Audience and outcomes

* Write for server owners who may never have managed a game server.
* Help readers complete one task or diagnose one symptom per page.
* State prerequisites, edition, server software, and consequences before steps.
* Identify whether instructions apply to Java, Bedrock, or Geyser.

## Terminology

* Use "Purpify game panel" or "game panel" for `panel.purpify.host`.
* Use "billing portal" for `payments.purpify.host`.
* Use "server" for a hosted game-server instance.
* Use "Minecraft Java Edition" or "Minecraft Bedrock Edition" on first mention.
* Use "plugin" only for Java server plugins.
* Use "mod" and "modpack" only for Java mod-loader content.
* Use "add-on" for Bedrock behavior packs and resource packs.
* Describe Geyser as Bedrock-to-Java cross-play, not as a native Bedrock server.
* Use "server address" and "server port" as separate values.

## Style

* Use active voice and second person ("you").
* Keep sentences concise and headings in sentence case.
* Lead with the answer before background information.
* Bold exact UI labels: Select **New Server**.
* Use code formatting for files, commands, paths, settings, and exact values.
* Define technical terms on first use.
* Use specific nouns instead of ambiguous pronouns.
* Add descriptive frontmatter, keywords, cross-links, and image alt text.

## Draft frames

* Use `noindex: "true"` while a page contains unverified TODO sections.
* Remove `noindex` only after the content is accurate enough for search and AI answers.
* Mark unknown details with `{/* TODO: Verify the value or workflow. */}`.

## Accuracy and content boundaries

* Never invent panel labels, URLs, ports, file limits, plan limits, defaults, supported versions, retention periods, or time estimates.
* Link policy questions to the current Purpify policy instead of paraphrasing unverified terms.
* Never publish passwords, tokens, private server addresses, invoices, or personal player data.
* Do not mix Java plugins, Java mods, Bedrock add-ons, and Geyser extensions.