Resources
Riachu wiki
A reference built around the registry the website actually loaded, not a promised feature list.
Registry source: Live API · cached
Command data may be cached for an hour. Source describes the catalogue, not bot uptime.
How the reference is organized
The registry groups modules into cogs and commands. Each command can include a signature, aliases, caller and bot permissions, module gates and usage restrictions. The command explorer is the searchable view; module pages show exact folder matches.
Category names are not feature guarantees
The navigation includes common areas such as security, welcome and roles. A page only lists commands when the registry has that exact module identifier. For example, a roles gate on a command does not place it in a roles folder.
Read the source documentation
The project README documents the registry endpoint, hourly cache, checked-in snapshot and website setup. It is website documentation, not a separate bot administration API. Use the links below to inspect the loaded categories or read the README.
Modules in loaded tree
Find commands filed under utilities in the loaded registry. A category name alone does not confirm a capability.
Review only commands explicitly filed under security. Moderation commands are not relabelled as security features.
Review the moderation commands, usage and permissions reported by the loaded registry.
Inspect commands filed under logging. A mention of logs in another command does not establish a logging module.
Find commands filed under welcome. No greeting or onboarding configuration is assumed when the registry has no matching module.
Inspect the roles folder. Commands with a roles gate may live elsewhere and are not moved into this category.
Explore commands filed under fun, using their registry descriptions and usage requirements.