From 9d09114529c306f2a9cd3da57c2240d26cdd8b05 Mon Sep 17 00:00:00 2001 From: PiggyPiglet Date: Tue, 10 Feb 2026 11:15:38 +0800 Subject: [PATCH] FIx hytale config api title, weird hytale usage example & papi component --- docs/developers/configuration-api-hytale.md | 2 +- docs/developers/using-placeholderapi.md | 3 +-- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/developers/configuration-api-hytale.md b/docs/developers/configuration-api-hytale.md index 2e18452..c34d67d 100644 --- a/docs/developers/configuration-api-hytale.md +++ b/docs/developers/configuration-api-hytale.md @@ -2,7 +2,7 @@ description: How to create configurable expansions in Hytale. --- -# The Configurable Interface +# Hytale's Configurable Interface Unlike in spigot, in Hytale PAPI does not forward through Hytale's configuration API and instead implements its own. Effectively you'll be required to create a class representing your configuration section in PlaceholderAPI's main config.yml, and PAPI will handle the rest. diff --git a/docs/developers/using-placeholderapi.md b/docs/developers/using-placeholderapi.md index a08283a..4749987 100644 --- a/docs/developers/using-placeholderapi.md +++ b/docs/developers/using-placeholderapi.md @@ -258,7 +258,6 @@ Starting with version 2.12.0 is it now possible to provide Components from the A In order to use this new feature are the following things required to be true: -- You depend on `placeholderapi-paper` and not just `placeholderapi` - Your plugin runs on a Paper-based Server. Spigot-based servers will not work! - You use `PAPIComponent` instead of `PlaceholderAPI` to parse Components. /// @@ -347,7 +346,7 @@ public class JoinExample extends JavaPlugin { @Override protected void setup() { // (1) - Universe.get().getWorlds().keySet().forEach(name -> getEventRegistry().register(PlayerReadyEvent.class, name, this::onPlayerReady)); + getEventRegistry().registerGlobal(PlayerReadyEvent.class, this::onPlayerReady)); } public void onPlayerReady(PlayerReadyEvent event) {