nano-module-roles

Role automation for any Discord server, as a nano-core module: self-pick panels on reactions and buttons, derivation rules, divider sections with the top-section colour law, departure snapshots with rejoin restore, and a moderator command surface with confirm flows. This repository is the module’s one home, development and distribution both. A nano-core host runs it from a checkout at modules/roles inside the host tree.

Install

Two equivalent paths land the module in a nano-core host.

From the nano-store registry, which pins a released version:

npm run module -- install roles

Or as a git checkout inside the host tree, which tracks this repository directly:

git clone https://github.com/ccs-devhub/nano-module-roles \
  modules/roles

Either way the host enables it through the config entry:

{ "modules": ["./modules/roles"] }

It needs the database service (it refuses to enable without one) and declares the GuildMembers, GuildMessageReactions and GuildModeration gateway intents. GuildMembers is privileged and must be enabled in the developer portal.

Quickstart

Module defaults are EMPTY by law. Everything a server wants is per-guild config: tier-one keys move through /roles config set, structural keys (panels, sections, rules, sanction lists) move through the host tooling. See the MANUAL for every key and command.

1. Set an entry role, /roles config set entry_role_id <id>.
2. /roles sections detect proposes a section layout from the live role stack, read only, ready to paste into the config.
3. Author panels and sections in the guild config, then /roles panel create <id> publishes them.
4. Grants and removals go through /roles grant and /roles revoke, both behind a confirm step that lists any privileged permissions the role carries.

The MANUAL walks every path with worked examples: day-to-day moderation, panel publishing, section bootstrap, departure and restore, and the operations-tier config a server owner writes directly.

License

MIT. The nano-core host is MPL-2.0.