Replies: 1 comment 1 reply
-
|
I converted this to a discussion, as issues are reserved for bug reports and feature requests towards PlaceholderAPI, not for gaining feedback on your own project. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Confirmation
Type
New API feature
Description
Hi 👋
I recently created a plugin called PlaceholderAPI Mock, designed specifically for development and testing purposes.
It allows plugin developers to mock any PlaceholderAPI values through a YAML config, without needing the full plugin stack during local development.
I built this to solve a pain point I encountered when working on plugins that depend on PlaceholderAPI—especially in team environments where not everyone has the same setup.
🔧 Key Features:
• Mock both static and dynamic placeholders (e.g. %vault_eco_balance_%)
• Support multiple identifiers across different plugins
• Hot-reload config via /papimock reload
• Debug mode to print all registered placeholders
• Safe and explicitly marked development-only
📖 GitHub Repository:
https://github.com/lulu2002/PlaceholderAPI-Mock
SpigotMC
⸻
I’d love to hear your thoughts on this:
• Do you see this as a useful tool for the PlaceholderAPI ecosystem?
• Would you consider linking to it as a dev tool in your docs or wiki?
• Are there any design choices you’d advise rethinking?
Thanks again for your awesome work on PlaceholderAPI – it’s been a key part of the plugin dev experience for years.
Cheers,
Jerry
Code Example
Jar file
No response
Additional Information
No response
Beta Was this translation helpful? Give feedback.
All reactions