> For the complete documentation index, see [llms.txt](https://b-setups.gitbook.io/b.-setups/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://b-setups.gitbook.io/b.-setups/servers/skywars-server/additional-information/where-to-find-what.md).

# Where to Find What

This guide provides a breakdown of where to find the essential configurations, language files, menus, scripts and customizable texts for **SkyWars Server Setup**. Use this reference to translate the server, change items, or adjust the server's visual presentation.

***

### 1. Core Game Messages & Translation

*These files and folders control the primary in-game text, including chat messages, game states, win/loss announcements, kits and cages.*

* **Main Plugin Folder:** `plugins/Skywars/`
  * **Messages:** `plugins/Skywars/messages.yml` holds the chat formats, death messages, menu item names and most player-facing text.
  * **Config:** `plugins/Skywars/config.yml` controls game settings, leaderboards and the data storage.
  * **Kits / Cages / Effects:** `plugins/Skywars/kits/`, `glasscolors.yml`, `particleeffects.yml`, `projectileeffects.yml`, `taunts.yml`.

### 2. Lobby Items, Leaderboard Holograms & Void Teleport

*These features are handled by the bundled SkywarsAdditions plugin (it replaces ItemJoin, DecentHolograms, ajLeaderboards and VoidTeleport).*

* **SkywarsAdditions:** `plugins/SkywarsAdditions/config.yml`
  * **Lobby items:** the hotbar items given in the lobby (Stats head, Leave) — their slots, materials, names, lore and the command each one runs.
  * **Leaderboard holograms:** the `wins`, `kills` and `levels` hologram types — titles, header/footer, row count, line format and the `switch-format` line. The stats are read from SkyWarsReloaded's PlaceholderAPI values (`%swr_wins%`, `%swr_kills%`, `%swr_level%`). Placed holograms live in `holograms.yml`; manage them in-game with `/swholo`. A hologram with several `pages` (e.g. `wins` + `kills` + `levels`) is switched **per-player** by right-clicking it, so every player can view a different page at the same time.
  * **Void teleport:** the lobby world name, the Y level below which players are teleported, and the teleport target.
  * Reload after editing with `/swadditions reload`.

### 2b. Lobby NPCs (Solo / Teams / Quests / Rewards)

*The lobby opener NPCs are native **Citizens** NPCs (no longer handled by SkywarsAdditions).*

* **Citizens:** `plugins/Citizens/saves.yml`
  * Each NPC stores its location, skin, hologram name lines and the command its right-click runs (`commandtrait`): Solo → `sw join solomenu`, Teams → `sw join teammenu`, Quests → `swquests`, Rewards → `rwds`.
  * Move, reskin, rename or re-create them in-game with Citizens' own `/npc` commands.

### 3. Scoreboard & Tablist

*These settings dictate the UI elements shown on the right side of the screen (Scoreboard) and when holding the TAB key (Player list and server info).*

* **TAB Plugin:** `plugins/TAB/config.yml`
  * Open this file to translate or modify the scoreboard title, the lines displayed on the side, header/footer texts in the player list, and nametag prefixes.

### 4. MOTD & Server List Appearance

*The MOTD (Message of the Day) is the text players see in their multiplayer server list before they connect to the server. It also includes the hover text over the player count.*

* **AdvancedServerList:** `plugins/AdvancedServerList/profiles/default.yml`
  * Here you can translate the two lines of text displayed under the server name in the multiplayer menu, and adjust the favicon and player-count hover.

### 5. Custom Scripts & Action Texts

*Skript is used for custom lobby commands, the announcements and join messages that aren't covered by the main plugins.*

* **Skript Folder:** `plugins/Skript/scripts/`
  * This setup contains the following active script files which may hold custom hardcoded texts, chat formats, or interactive logic:
    * `main_commands.sk` (The `/help` menu pages and the `/store`, `/discord` and `/stats` commands)
    * `announce.sk` (Controls the rotating server announcements and the `/announcements` toggle)
    * `subcommands.sk` (Controls the `/party`, `/lobby`, `/l`, `/hub` shortcuts)
    * `onjoin.sk` (Controls the welcome title and sound on join)
    * `pluginhider.sk` (Hides plugin commands from tab-completion)
    * `startup.sk` (Startup logic / setup)
  * Open them and translate the texts between quotation marks `" "`.

### 6. Party System

*The party system lets players group up and play together using /party (it wraps SkyWarsReloaded's native /swparty).*

* **SkyWarsReloaded:** `plugins/Skywars/messages.yml`
  * The party chat messages live under the `party` section of `messages.yml`. The `/party` wrapper itself is in `plugins/Skript/scripts/subcommands.sk`.

### 7. Global Server Messages

*These handle basic server functions like unknown commands, joining, quitting, and core economy texts.*

* **EssentialsX:** `plugins/Essentials/`
  * If you need to translate standard commands like `/tp`, `/msg`, or economy messages, look for the `messages_en.properties` file here (you might need to extract it from the Essentials jar if it's not generated).
* **Server / Spigot messages:** `spigot.yml`
  * The whitelist, unknown-command, server-full, outdated-client/server and restart messages are set here.


---

# 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:

```
GET https://b-setups.gitbook.io/b.-setups/servers/skywars-server/additional-information/where-to-find-what.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.