1.6 KiB
1.6 KiB
title, weight
| title | weight |
|---|---|
| The Module System | 2 |
Goal: Define the vocabulary and mechanics of Quetza's primary abstraction unit.
System Vocabulary
Module Declaration
The module.ts file acts as the manifest. It is the entry point for discovery.
export const name = 'my-module'; // ID
export const description = '...'; // Doc
Command Registration
Occurs during the ready event.
- Quetza scans all
commands/folders. - Compiles
ApplicationCommandData. - PUTs the payload to Discord's API.
Controller Injection
State is injected, not imported.
// The framework calls this:
execute(client, interaction, controller);
- Why? Allows the framework to manage the controller's lifecycle (singleton per module).
State Management Philosophy
Ephemeral by Default
Quetza provides no built-in database.
- Memory: Controllers store state in JS
MaporSetobjects. - Restart: All state is lost when the process exits.
- Persistence: Must be implemented manually (e.g., SQLite, Redis) inside the Controller.
Scope as Key
State must be keyed by its boundary.
Map<GuildID, ...>- Server specific (Most common).Map<UserID, ...>- User specific (DM bots).
Error Handling Model
Fail Fast & Friendly.
- Validation: Check permissions/inputs immediately.
- User-Facing: "You don't have permission" (Not "Error: 403").
- Isolation: A crash in
/pingcatches itself and doesn't kill the bot.
See also: