mirror of
https://github.com/PlaceholderAPI/PlaceholderAPI
synced 2026-02-26 05:51:12 +01:00
FIx hytale config api title, weird hytale usage example & papi component
This commit is contained in:
@@ -2,7 +2,7 @@
|
|||||||
description: How to create configurable expansions in Hytale.
|
description: How to create configurable expansions in Hytale.
|
||||||
---
|
---
|
||||||
|
|
||||||
# The Configurable<T> Interface
|
# Hytale's Configurable<T> 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.
|
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.
|
||||||
|
|
||||||
|
|||||||
@@ -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:
|
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!
|
- Your plugin runs on a Paper-based Server. Spigot-based servers will not work!
|
||||||
- You use `PAPIComponent` instead of `PlaceholderAPI` to parse Components.
|
- You use `PAPIComponent` instead of `PlaceholderAPI` to parse Components.
|
||||||
///
|
///
|
||||||
@@ -347,7 +346,7 @@ public class JoinExample extends JavaPlugin {
|
|||||||
@Override
|
@Override
|
||||||
protected void setup() {
|
protected void setup() {
|
||||||
// (1)
|
// (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) {
|
public void onPlayerReady(PlayerReadyEvent event) {
|
||||||
|
|||||||
Reference in New Issue
Block a user