Skip to main content
ChapterJS is young. This page is its roadmap: everything below is missing today, area by area, and an entry leaves this page the day the feature ships. When there is a way around it meanwhile, it is said.
not yet
Where commands can be used
User-installed apps. A bot that a person adds to their own account, to use its commands in every server and in private messages. A bot is added to a server, and that is where its commands are.
not yet
Knowing who pays for your bot
Premium and entitlements. Knowing who has subscribed to your bot, and being told when someone does.
not yet
What Discord sends that no event() receives
Auto-moderation, stickers, soundboard, pins, webhooks, integrations and stages. No event() for what auto-moderation does, for stickers and soundboard sounds added or changed, for a message pinned or unpinned, for webhooks and integrations changed, for stage instances, and for the status of a voice channel.
not yet
Beyond playing a sound
Recording voice. Hearing what people say in a voice channel, to record or transcribe it. The bot only plays, and is deafened by default.
not yet
Actions on what the bot only reads today
Scheduled events. Editing or deleting one.Stickers and auto-moderation rules. Creating, editing or deleting one.
not yet
How and where a bot runs
A bot spread over several machines. Running one bot on several machines at once. Meanwhile: a large bot runs on several processes of one machine by itself.Choosing what the bot remembers. A setting for how many members, users and messages the bot keeps in memory. It follows your files and the memory available.A config file. A chapterjs.config.ts. What your bot does comes from the files of src/, and what it needs to run from .env: one token, one test server.Sharing files between bots. Publishing your commands, events or components as a package, to use them in another project. A file is only loaded from the src/ of the project.
not yet
What chapterjs test does not simulate
Time, voice, polls, scheduled events and auto-moderation. Time does not pass in the test server (a cooldown, a task that runs every so often), and voice, polls, scheduled events and auto-moderation are not simulated. An event the server can not make happen is named in the report, and a request for something it does not model answers as Discord does for something that does not exist. See Testing.

Reference

Everything that exists today, structure by structure.

Troubleshooting

Every message of the CLI, and what people see on Discord.