> ## Documentation Index
> Fetch the complete documentation index at: https://www.chapterjs.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Roadmap

> The roadmap of ChapterJS: what it does not do yet, so that you do not look for it, and what to do meanwhile

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.

**Commands**

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.

**Premium**

Knowing who pays for your bot

**Premium and entitlements.** Knowing who has subscribed to your bot, and being told when someone does.

**Events**

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.

**Voice**

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.

**Servers**

Actions on what the bot only reads today

**Scheduled events.** Editing or deleting one.

**Stickers and auto-moderation rules.** Creating, editing or deleting one.

**Running the bot**

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](https://www.chapterjs.org/run/start.md#large-bots) 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](https://www.chapterjs.org/memory.md).

**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`](https://www.chapterjs.org/setup/project-structure#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.

**Testing**

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](https://www.chapterjs.org/testing.md#what-it-does-not-do-yet).

> [card] [Reference](https://www.chapterjs.org/reference.md)
>
> Everything that exists today, structure by structure.

> [card] [Troubleshooting](https://www.chapterjs.org/run/troubleshooting.md)
>
> Every message of the CLI, and what people see on Discord.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.