← ClaudeAtlas

marginalialisted

PaperMC work — writing, building, and debugging Paper/Spigot/Bukkit server plugins (plugin.yml, Brigadier commands, event listeners, Adventure/MiniMessage, inventories, PDC, scheduler, Folia, particles, paper-api Gradle setup), and contributing patches to PaperMC itself. Use for any Paper, Spigot, Bukkit, Folia, Velocity, or Adventure question.
Y2Kwastaken/Marginalia · ★ 0 · DevOps & Infrastructure · score 59
Install: claude install-skill Y2Kwastaken/Marginalia
# marginalia PaperMC work splits into two jobs that look similar and are not. **Decide which one this is before doing anything else** — the APIs, the source of truth, and even which repository you read are all different. | You are… | Signals | Go to | |---|---|---| | **Writing a plugin** — code that runs *on* a Paper server | `JavaPlugin`, `plugin.yml`, `paper-api` dependency, events, commands, a `plugins/` folder | [plugin-dev/OVERVIEW.md](plugin-dev/OVERVIEW.md) | | **Contributing to Paper** — changing Paper *itself* | Patch files, `./gradlew applyPatches`, `paper-server/`, NMS/mappings, opening a PR on `PaperMC/Paper` | **Not built yet** — see below | If it is ambiguous, ask. "Add an event" means one thing in a plugin and something completely different inside Paper's own source tree. Whichever prong applies: **do not answer from memory.** Paper moves fast, and recalled Bukkit-era patterns are the main failure mode here. Each prong names its own ground truth and how to fetch it. ## Contributing to Paper — not yet available The second prong is not written. Do **not** substitute plugin-development guidance for it: the plugin API is not how you change Paper's internals, and answering from the plugin side would be actively misleading. Say so plainly, then offer what genuinely helps: - `PaperMC/Paper`'s own `CONTRIBUTING.md` is the authoritative source, and Paper uses a patch-based workflow against upstream — contributions are patch files, not direct edits to vendore