PlaceholderAPI

Implement PlaceholderAPI expansions with onRequest methods for Spigot servers.

1|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/Kling0012/MCRPG --skill placeholderapi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: PlaceholderAPI
Source: https://github.com/Kling0012/MCRPG/tree/main/output/PlaceholderAPI
Command: npx skills add https://github.com/Kling0012/MCRPG --skill placeholderapi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

PlaceholderAPI provides a centralized way to manage and replace placeholders from multiple plugins in a Spigot server, reducing manual string handling and integration work.

Core Features & Use Cases

  • Centralized placeholder expansion system supporting internal and external expansions
  • Easy integration with other plugins to expose their placeholders
  • Debugging and testing placeholders via placeholder commands and test strings
  • Use case: expose player name, server information, and dynamic data across multiple plugins

Quick Start

Install PlaceholderAPI on your Spigot server, add an expansion (internal or external), restart, and verify placeholders by testing with a sample string containing placeholders using the API (e.g., setPlaceholders) to confirm replacements.

Frequently Asked Questions about PlaceholderAPI

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I replace placeholders from multiple Minecraft plugins on a Spigot server?

PlaceholderAPI centralizes placeholder expansion across plugins on Spigot servers. Install PlaceholderAPI, add expansions (internal or external), restart, then use the setPlaceholders API method to replace placeholders like %player_name% or %server_info% with dynamic text.

Can I create custom placeholders for my Spigot plugin expansion?

Yes. Implement onRequest or onPlaceholderRequest methods in your expansion, define frontmatter name and description, and optionally add resources like scripts or assets. PlaceholderAPI will route placeholder requests to your expansion's handler.

What's the best way to test placeholders on a Spigot server?

Use placeholder commands and test strings to verify replacements work. Create a sample string containing placeholders, call the API (e.g., setPlaceholders), and confirm the output matches expected dynamic values across your plugins.

Do I need to restart the server every time I add a new placeholder expansion?

Yes. After adding an internal or external expansion to PlaceholderAPI, restart the Spigot server so it loads the expansion's frontmatter and methods, then verify placeholders are working via test commands.

Can PlaceholderAPI work with external plugin integrations?

Yes. PlaceholderAPI supports both internal expansions (built into your plugin) and external expansions (separate plugins). External expansions integrate automatically once installed and recognized, reducing manual string handling across plugins.

Why should I use PlaceholderAPI instead of hardcoding placeholder logic in each plugin?

PlaceholderAPI eliminates duplicate string-handling code and centralizes placeholder management. Plugins expose placeholders once, and other plugins access them through a unified API, reducing integration work and debugging effort.