> For the complete documentation index, see [llms.txt](https://realisticnode.gitbook.io/rnsetups/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://realisticnode.gitbook.io/rnsetups/rnkoth/reference/faq.md). # FAQ and troubleshooting Solutions to the most common questions and problems. ## I stand in the area but I do not count Look at your action bar: it tells you why. * **"move to count (AFK)"**: you did not move or turn for `rules.afk-seconds` (60 by default). Move a little. * **"not counting in this game mode"**: only `SURVIVAL` and `ADVENTURE` count by default (`rules.counted-gamemodes`). Players hidden by a vanish plugin never count. * **"Invisible players don't count here"**: you have the invisibility effect. Set `rules.invisible-players-count: true` to allow it. * **"You just died"**: wait `events.death-cooldown` seconds (5 by default). If the action bar shows nothing about the KOTH, you are **not inside** the area: * The area **starts on top of the blocks you clicked** with the wand. If you clicked blocks under the floor, or the top of a wall, the area is too low or too high. Run `/koth show ` to see it. * The area is 3 blocks high by default. On stairs, slabs or a hill, make it taller: editor → **Area height**. * With several areas, the KOTH may have moved. `/koth info ` shows where it is now. Admins can check every player inside with `/koth status `: it lists each one as `counting`, `afk`, `gamemode`, `invisible`, `cooldown` or `dead`. ## My progress keeps going back to 0 That is `capture.on-leave: reset`: progress is lost as soon as your side is not inside. Every step out of the area, every death and every knockback out counts. Make the area bigger or taller, or use `on-leave: pause` or `drain`. See [Game modes](/rnsetups/rnkoth/guides/modes.md). ## The KOTH does not start by itself Check `/koth list` and the console. Usual reasons: * **No schedule**: add a time in `/koth editor ` → Schedule. A line shown with a barrier is not understood. * **Wrong time zone**: set `timezone` in `config.yml`. Empty means the server machine's time zone, which is often UTC on hosting. The editor's **Next starts** item shows the next five starts. * **Not enough players**: `min-players` counts the players online on the server, except vanished players and spectators. The chat says `did not start: it needs X players online`. * **Disabled**: `enabled: false` stops schedules (but not `/koth start`). * **Too many at once**: `events.max-at-once`. * **No area, or its world is not loaded.** ## Nobody won when the time ran out * With `capture.best-wins-when-time-ends: false`, nobody wins when the time runs out. * With `on-leave: reset`, the holder's progress is lost when they leave, so at the end nobody may have any. * A side with 0 progress or points never wins. ## The sidebar flickers, disappears or replaces my scoreboard Another scoreboard plugin (TAB, AnimatedScoreboard, FeatherBoard...) is fighting with rnKoth for the sidebar. Set `display.sidebar: false` in `config.yml` and add the KOTH lines to your own scoreboard with the [placeholders](/rnsetups/rnkoth/reference/placeholders.md), for example `%rnkoth_current_holder%` and `%rnkoth_current_time_left%`. rnKoth gives each player their old scoreboard back when they leave the KOTH or the event ends. Players can also turn the sidebar off for themselves with `/koth hud`. ## Players in other places do not see the boss bar or messages * The boss bar is only for players in the **world of the KOTH**. * With `display.radius: 0` (default), messages, titles and sounds go to every player on the server, in every world. * With `display.radius` above 0, messages, titles, sounds and the boss bar are only for players in the world of the KOTH up to that distance. Set it to `0` to send the messages to everyone. * `display.boss-bar: false` turns the bar off. ## The hologram does not appear * `display.hologram: true` in the KOTH file, and the KOTH has an area. * A disabled KOTH has no hologram while it is not running. * It appears when the chunk is loaded, a moment after a player gets near. * Change its height with `display.hologram-height` if it is inside a block. ## Does it work on Folia? Yes. Two things are not available because Folia does not support them yet: * **No sidebar**. Use the [placeholders](/rnsetups/rnkoth/reference/placeholders.md) in a scoreboard plugin that works on Folia. * **No scoreboard teams**. Use `teams.mode: placeholder` with your clan plugin ([Teams](/rnsetups/rnkoth/guides/teams.md)). Everything else works: boss bars, action bars, the locator, holograms, particles, rewards, the editor and the reward box. ## Does it work on Spigot? Yes, 1.21.1 to 26.3. The first start needs internet to download the text library (Adventure) that Paper has built in. On Spigot the numbers on the right of the sidebar are shown (Paper hides them). ## A player did not get their reward * **Items**: if the inventory was full, they went to the reward box. The player gets a message; `/koth claim` opens it (with `rewards.claim-command: false`, open it with `/koth open claim `). * **Offline**: rewards of players who left before the end are given when they join again, with the message `You got rewards you won while you were offline.` * **Not inside**: winner, 2nd and 3rd rewards only go to players who stood in the KOTH and counted. Participation needs `participation-seconds` inside. * **2nd and 3rd place** are only given when there is a winner, and only to sides with some progress or points. * **A broken line**: the console shows `Reward line failed in hill ...` or `Unknown reward action`. The other lines are still given. * **Loot**: `[loot]` gives the loot chest only to one winner, the one who stood inside the longest. ## Placeholders in my reward commands are not replaced `{player}`, `{team}`, `{place}` and the other `{...}` placeholders of [Rewards](/rnsetups/rnkoth/guides/rewards.md#placeholders-in-rewards) work in commands, and so do `{@...}` language words (in the server language) and PlaceholderAPI placeholders (`%...%`, for the player who gets the reward; in `commands.on-start` and `on-end` without a player). If a `%...%` placeholder stays as it is, its PlaceholderAPI expansion is probably not installed (`/papi ecloud download `). ## The wand does nothing * Hold it in your **main hand** and click a **block** (not the air). * Using the wand needs `rnkoth.editor` (or `rnkoth.admin`). * Lost it? `/koth wand`. ## Holder kills give no reward The killed player must be holding the KOTH (on the gaining side, inside and counting), the killer must be on another side, and the same killer gets it only once a minute for the same victim. Killing a teammate never counts. ## I changed a file and nothing happened With `auto-reload: true`, changes apply a few seconds after saving. If not, look at the console: a file with a mistake is not applied and the console shows the line, for example: ``` koths/spawn.yml has an error and could NOT be loaded. The mistake is most likely on line 6: 5 | # Name shown to players (colors: , <#ff8800>, &6 ... all work) >> 6 | display-name: 'Spawn 7 | # false = it never starts by itself (it can still be started with /koth start spawn) Tip: This ' is never closed. Close it at the end of the value, and inside '...' write an apostrophe twice: 'don''t'. ``` Usual mistakes: a missing `'` at the end, a `'` inside a text (write it twice: `''`), or tabs instead of spaces. While a KOTH file has a mistake, that KOTH keeps the last version that was read without errors (a running event goes on). Only a file that was already broken when the server started has no area until you fix it. ## Do events survive a restart? Yes, with `events.resume-after-restart: true` (default). The progress, time, players and kills are saved in `data/running.yml` and the event continues after the restart. `/koth reload` never stops running events. ## How do I run two KOTHs at the same time? Just schedule both. There is no limit unless you set `events.max-at-once`. Give each one a `display.radius` if players near one should not get the messages of the other. ## Still need help? Join our [Discord](https://discord.gg/GzxW2FANPB) and open a ticket. See [Support](/rnsetups/support.md).