What this tool does
You pick name, main class, version, maybe authors and a couple of commands or permissions. It turns that into YAML. Download it, or copy-paste if you only need a quick fix.
Server & Files
Build a Spigot / Paper / Bukkit plugin.yml from the official field set: required name, main, version, plus commands, permissions, depend, and more. Download into your plugin resources folder.
name: MyPlugin main: com.example.myplugin.MyPlugin version: 1.0.0 description: 'A cool new plugin.' api-version: 1.21 author: Player
Server & Files
Tired of typing plugin.yml by hand and missing a space? This just fills in the usual fields and spits out a file you can drop into your plugin project.
You pick name, main class, version, maybe authors and a couple of commands or permissions. It turns that into YAML. Download it, or copy-paste if you only need a quick fix.
It does not write your Java code. If your command in plugin.yml does not match what you register in code, the plugin still will not work. That part is on you.
Keep the plugin name simple: letters, numbers, underscores. api-version should be close to the Minecraft version you actually build against. depend and softdepend only matter if those plugins exist on the server.
No. Only plugin.yml. You still code and compile the plugin yourself.
Same file for both, for the basic fields. Set api-version to whatever you support.
Usually src/main/resources/plugin.yml so it ends up at the root of the jar.
If something feels wrong, a Minecraft version is missing, the wording is confusing, or you have a better workflow idea, send it over. Real player feedback is how these tools get sharper.
Server & Files
Tired of typing plugin.yml by hand and missing a space? This just fills in the usual fields and spits out a file you can drop into your plugin project.
You pick name, main class, version, maybe authors and a couple of commands or permissions. It turns that into YAML. Download it, or copy-paste if you only need a quick fix.
It does not write your Java code. If your command in plugin.yml does not match what you register in code, the plugin still will not work. That part is on you.
Keep the plugin name simple: letters, numbers, underscores. api-version should be close to the Minecraft version you actually build against. depend and softdepend only matter if those plugins exist on the server.
No. Only plugin.yml. You still code and compile the plugin yourself.
Same file for both, for the basic fields. Set api-version to whatever you support.
Usually src/main/resources/plugin.yml so it ends up at the root of the jar.
If something feels wrong, a Minecraft version is missing, the wording is confusing, or you have a better workflow idea, send it over. Real player feedback is how these tools get sharper.