Add this registry to nParse+
Paste this into Settings → Plugins → Registries. It is the same document
every nParse+ install reads, and it needs no account:
https://nparseplugins.prokopto.dev/index.json
Or read the index yourself — it is JSON, it is public, and everything below is rendered from it.
Write one
Start from the plugin template, claim an id, and let your release pipeline publish on tag. How to publish a plugin walks the whole path — including the part where a brand-new plugin id waits for a human, which is expected rather than broken.
Plugins
6 plugins listed.
| Plugin | Latest | Author |
|---|---|---|
|
Death Recap
death-recap
Pops a "what killed me" timeline the moment you die.
|
0.2.3 | BennyTwoThumbs/Forsure MyDude |
|
Floating Combat Text
floating-combat-text
Nparse+ floating combat-text plugin
|
1.15.1 | BennyTwoThumbs/Forsure Mydude |
|
Loot Tracker
loot-tracker
|
0.3.3 | not stated |
|
Merchant Mode
merchant-mode
Turn your inventory into linkable WTS auction macros, find which mule is holding what, look up what anything is worth, and see how its price is actually moving — one server at a time, since that is the only place any of it can be sold.
|
0.5.1 | prokopto-dev |
|
Mob Tracker
mob-tracker
Track mob spawn points with timers
|
0.5.1 | not stated |
|
Spell Checker
spell-checker
Check missing spells in spellbook
|
1.1.2 | BennyTwoThumbs/Forsure MyDude |
Publishing
Anybody can browse this registry. Publishing needs an account, and GitHub is the only way in: artifacts live on GitHub Releases and the ownership records this registry was migrated from are GitHub handles, so a GitHub identity is the one credential that connects a publisher to the code they are publishing.
What that looks like from a plugin repository — the template to start from, the scoped token, the one job you add to your release workflow, and what the first release actually does — is on how to publish a plugin.