@stonyx/discord 0.1.1-alpha.21 → 0.1.1-alpha.22

package/README.md

@@ -11,7 +11,7 @@ Discord bot module for the [Stonyx framework](https://github.com/abofs/stonyx),
 * **Command auto-discovery:** Drop command files into a directory and the framework registers them automatically.
 * **Event handler auto-discovery:** Same pattern for Discord gateway events.
 * **Intent auto-derivation:** Required intents computed from discovered event handlers.
-* **Lazy initialization:** Bot only starts if a token is configured and commands/events exist.
+* **Token-gated start:** The bot logs in only when a token is configured. With a token and no commands or events, it still logs in, so a send-only bot works.
 * **Singleton pattern:** Matches conventions of `@stonyx/sockets` and `@stonyx/events`.
 * **Utility methods:** sendMessage, reply with auto-chunking, role management, and more.
 
@@ -23,7 +23,7 @@ pnpm install @stonyx/discord
 
 ## Quick Start
 
-[`test/sample/`](https://github.com/abofs/stonyx-discord/tree/dev/test/sample) is the canonical usage reference: a working command and event handler, imported the way an app imports them.
+The examples below are complete files: each one imports only from `@stonyx/discord` subpaths, so it runs in an app that depends on nothing but `@stonyx/discord`. The repo's `test/sample/` directory holds a command and an event handler written the same way ([source](https://github.com/abofs/stonyx-discord/tree/dev/test/sample)), and the test suite loads them on every run.
 
 ### 1. Create handler directories
 
@@ -38,7 +38,7 @@ discord-events/         # default directory (configurable)
 
 ```javascript
 // discord-commands/ping.js
-import { SlashCommandBuilder } from 'discord.js';
+import { SlashCommandBuilder } from '@stonyx/discord/base';
 import Command from '@stonyx/discord/command';
 
 export default class PingCommand extends Command {
@@ -61,9 +61,9 @@ import EventHandler from '@stonyx/discord/event-handler';
 export default class MessageCreateHandler extends EventHandler {
   static event = 'messageCreate';
 
-  handle(message) {
+  async handle(message) {
     if (message.author.bot) return;
-    console.log(`${message.author.username}: ${message.content}`);
+    if (message.content === '!ping') await message.reply('pong');
   }
 }
 ```
@@ -76,9 +76,9 @@ Stonyx auto-initializes the bot when your app boots — no manual wiring needed:
 stonyx serve
 ```
 
-`Discord.init()` (called by the Stonyx module loader) awaits `new DiscordBot().init()`, which discovers commands/events, derives intents, and connects to the gateway. The lazy-init guards still apply: if `DISCORD_TOKEN` is unset or no commands/events exist, the bot skips login.
+`Discord.init()` (called by the Stonyx module loader) awaits `new DiscordBot().init()`, which discovers commands/events, derives intents, and connects to the gateway. If `DISCORD_TOKEN` is unset, the bot skips login. With a token it always logs in, even when no commands or events exist.
 
-## Package Exports
+## Exports
 
 | Import | Provides |
 |--------|----------|
@@ -161,7 +161,7 @@ The framework automatically computes the required intents from your registered e
 | `voiceStateUpdate` | `GuildVoiceStates` |
 | `interactionCreate` | *(none — handled by default)* |
 
-**`Guilds` is always included** when commands are registered.
+**`Guilds` is always included**, whether or not any commands or events are registered.
 
 ### Intent-to-Partial Mapping
 

package/package.json

@@ -4,7 +4,7 @@
     "stonyx-async",
     "stonyx-module"
   ],
-  "version": "0.1.1-alpha.21",
+  "version": "0.1.1-alpha.22",
   "description": "Discord bot module for the Stonyx framework",
   "main": "dist/main.js",
   "types": "dist/main.d.ts",