Changelog
This page summarizes the currently documented BotRS release line. The main API surface is intentionally small and follows the runtime path used by examples and gateway event handling.
[0.13.0] - Current
Current Surface
Clientowns the gateway lifecycle and dispatches typed events toEventHandler.- Event callbacks receive session objects that expose the shared
BotApiand add reply helpers for the current event. BotApicovers bot info, gateway discovery, message sending/recall, group/C2C file upload, guild/channel resources, roles, mute, channel permissions, announcements, schedules, API permissions, reactions, pinned messages, and audio controls.- Message sending uses session helpers for common replies and
MessageParams,GroupMessageParams,C2CMessageParams, andDirectMessageParamsconstructors for lower-level calls. - Gateway events are decoded into typed payloads for messages, direct messages, group/C2C messages, reactions, interactions, guilds, channels, members, audits, manage events, audio events, and forum events.
Notes
- The crate version in
Cargo.tomlis0.13.0. - The public docs focus on what users can build with the current API.
- Examples under
examples/are the best entry point for end-to-end usage.