# @plugdev/cli

**The local development environment for Minecraft plugins.**

Build, boot, join, spawn test players, and reload on save. Think `npm run dev`, but for Minecraft.

```powershell
npm install -g @plugdev/cli
cd your-plugin
plugdev init --setup
plugdev          # TUI: configure + run
plug run         # full loop
```

`plug` and `plugdev` are the same CLI.

Requires **Node.js 22+**. Use `plugdev agent install --codex` for project guidance and a portable skill, or install the skill globally with `npx skills add mattbaconz/plugdev --skill plugdev -g -y`. Then tell a new Codex task “use PlugDev” or invoke `$plugdev`.

- Detect Gradle/Maven (including multi-module reactors)
- Paper-family server + deps cache in `~/.plugdev/`
- Safe reload on save; optional `--hotswap`
- Client join (embedded or Prism)
- Extra players: `.bot Tester2` headless, `.bot Tester2 open` for a real window
- Listing shots/GIFs (Windows): `plugdev capture run` → `.plugdev/media/`
- Background Fabric 26.1.2 Prism capture: `plugdev client start --instance "FO 26.1.2"`, native screenshots, animated cursors, GUI clicks and player movement
- TUI: configure, module pick, deps, live config files
- `plugdev config list|open|get|set|editor|watch|unwatch` for generated plugin configs

Docs: [github.com/mattbaconz/plugdev](https://github.com/mattbaconz/plugdev) · [pluglabs.app/plugdev](https://pluglabs.app/plugdev) · [Discord](https://discord.gg/C4X3rThtAM)

Capture needs an unlocked Windows desktop and FFmpeg with `gfxcapture` plus FFprobe. The optional client bridges are bundled and activated only for local development sessions. Protocol bots can exercise plugins but cannot render screenshots. The Prism bridge keeps your existing mods and heap; agent rendering is capped at 30 FPS active and 5 FPS idle. See the bundled `dist/capture.md` guide for repeatable scenarios and supported states.