> For the complete documentation index, see [llms.txt](https://lethium.gitbook.io/lethium-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lethium.gitbook.io/lethium-docs/getting-started/requirements.md). # Requirements Server software, Java version, required and optional plugins, and what is and is not bundled in the Clicker package. ### Server | | | | --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Server software** | **Purpur 1.21.11** (a Paper fork). The package ships `server.jar` (Purpur build for 1.21.11). Paper 1.21.x also works. Spigot is not supported. | | **Java** | Java **25** | | **Minecraft version** | 1.21.11. Older and newer clients can join with ViaVersion and ViaBackwards. | | **Operating system** | Windows or Linux | | **Internet** | Required at startup to verify your licence. Also needed by ItemsAdder's pack host, Geyser updates and similar. | | **Ports** | Java (TCP), `server-port` in `server.properties`. Bedrock (UDP), `bedrock.port` in Geyser's `config.yml`, if you allow Bedrock players. | | **Memory** | Plan for **at least 4 GB** dedicated to the server for a small community, more as players grow. Five loaded worlds with hundreds of mobs cost more than a normal survival server. | | **Disk** | The package is about 400 MB zipped. Keep room for player data and backups. | {% hint style="info" %} The server is set to `online-mode=true`, `view-distance=10`, `simulation-distance=10` and `max-players=200`. These can be changed in `server.properties`. {% endhint %} ### Required plugin | Plugin | Why | | ------------------ | -------------------------------------------------------------------------- | | **MythicMobs 5.x** | ClickEm will not start without it. Every mob and boss is a MythicMobs mob. | ### Strongly recommended (the setup expects them) | Plugin | What it gives you | | ------------------------------------- | ---------------------------------------------------------------------------------------------- | | **LuckPerms** | Ranks and permissions. | | **Vault** | Economy and prefix bridge. | | **PlaceholderAPI** | Placeholders for TAB, holograms, HUD and chat. | | **WorldGuard** | Zone regions and world protection. | | **Multiverse-Core** | Loads the five worlds. | | **ItemsAdder** | The resource pack: menu art, icons, armor, eggs, badges. **Without it the game looks broken.** | | **BetterModel** | Boss and effect models. | | **BetterHud** | The on-screen HUD. | | **CinematicView** | The tutorial flight and boss cutscenes. | | **FancyNpcs**, **FancyHolograms** | The hub NPCs and signs. | | **AdvancedPortals** | World portals and best-zone portals. | | **ExcellentCrates** and **nightcore** | The seven crates. | | **TAB** | Tab list, name tags, Bedrock scoreboard. | | **LPC** | Chat format. | | **FastAsyncWorldEdit** | Building and zone deploy. | | **ProtocolLib** and **packetevents** | Libraries other plugins need. | ### Optional EssentialsX, LethiumMessages, LethiumLanguage, DeathControl, EasyCommandBlocker, SkinsRestorer, MiniMOTD, MobDisabler, VoidGen, Geyser, floodgate, ViaVersion, ViaBackwards, LethiumBans (DonutBans jar), AntiDamageParticles, IA-Edit. ### What the Clicker package contains `Clicker.zip` is a complete server folder: ``` Clicker/ server.jar Purpur 1.21.11 server.properties, bukkit.yml, spigot.yml, purpur.yml, commands.yml, help.yml config/ Paper configuration World1 ... World5/ The five built worlds plugins/ Every jar and configuration ``` Jars inside `plugins/` include ClickEm (`clickem-core--obf.jar`), MythicMobs, LuckPerms, Vault, PlaceholderAPI, WorldGuard, Multiverse-Core, FastAsyncWorldEdit, BetterModel, BetterHud, CinematicView, FancyNpcs, FancyHolograms, AdvancedPortals, ExcellentCrates, nightcore, LPC, EssentialsX, LethiumMessages, DeathControl, EasyCommandBlocker, SkinsRestorer, MiniMOTD, MobDisabler, Geyser, floodgate, ViaVersion, ViaBackwards, ProtocolLib, packetevents, LethiumBans (DonutBans jar), AntiDamageParticles and IA-Edit. {% hint style="warning" %} **Not bundled, install them yourself:** * **ItemsAdder** (paid). Its configuration and content are in the package, the jar is not. * **TAB** (free). Its configuration is in the package. * **VoidGen** (free). Its configuration is in the package, and World 1 uses it as its generator. * **Converter plugins** for Bedrock (`BedrockGen`). Only their data folders are present. * A **voting plugin** if you want the Vote crate key. * **FancyAnalytics** and **bStats** are optional telemetry. {% endhint %} ### Checking your environment ``` java -version # must show 25 ``` In the game console after start, `/version` shows the server build, and `/plugins` (or `/pl`) shows every plugin in green if it loaded. --- # 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://lethium.gitbook.io/lethium-docs/getting-started/requirements.md?ask=&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.