Skip to content

PlaceholderAPI expansion for MiniPlaceholders

License

Notifications You must be signed in to change notification settings

MiniPlaceholders/PlaceholderAPI-Expansion

Folders and files

NameName
Last commit message
Last commit date
Jan 31, 2024
Nov 18, 2023
May 7, 2023
Jul 28, 2023
Apr 21, 2023
Apr 23, 2023
Jul 28, 2023
May 8, 2023
May 8, 2023
Jun 30, 2023
Apr 21, 2023
Apr 21, 2023
Jul 10, 2023

Repository files navigation

PlaceholderAPI-Expansion

PlaceholderAPI Expansion for MiniPlaceholders

Supported Platforms

  • Paper
  • Folia
  • Velocity

If you are using Velocity

In order to use PlaceholderAPI placeholders with MiniPlaceholders Velocity, you must install PAPIProxyBridge according to its installation guide

On Velocity there is an additional optional expiry parameter for how long the placeholder should be cached. This value is in milliseconds.

Placeholders

  • <placeholderapi_global:(placeholder)> Velocity:
  • <placeholderapi_global:(placeholder):(expiry)>

This placeholder does not require any player to work. Its operation would be similar to running the command /papi parse --null (placeholders)

  • <placeholderapi_player:(placeholder)> Velocity:
  • <placeholderapi_player:(placeholder):(expiry)>

This placeholder requires an online player to function. Its operation would be similar to running the /papi parse me (placeholders) command

  • <placeholderapi_relational:(placeholder)> Velocity:
  • <placeholderapi_relational:(placeholder):(expiry)>

This placeholder requires two online players to work. The functioning of this placeholder depends on whether the plugin in which it is used has relational placeholder support

If you want to nest the result of the placeholder inside another placeholder, add the string argument. For example:

  • <placeholderapi_player:%player_name%:string>
  • <placeholderapi_player:%player_name%:string:30000>

Downloads