Introduces a first-class per-guild switch to permit or block Global Chat participation at the configuration layer. The flag is persisted in guild config, enforced by relays/commands, and audited alongside other feature flags, giving admins a reversible control without touching channel bindings.
GuildConfig: destructive reset flow with confirmation and timeout safety
Adds a two-step Reset path that prompts for confirmation, cancels cleanly on timeout, and re-arms the control to avoid stale-interaction errors. On confirm, it rebuilds the guild with the default configuration and posts a success summary of what was reset.
Automatic default guild provisioning on bot join
On first join, the bot seeds a minimal, sane configuration (prefix, empty channel bindings, feature flags at defaults) so core commands work immediately. Provisioning is idempotent and will not overwrite existing settings if the bot is re-added.
Per-guild module disable controls for server staff
Admins can selectively disable modules (e.g., Automod, Global Chat, Economy) from GuildConfig. Disabled modules hide their commands where possible, skip scheduled tasks, and fail closed at runtime for safety.
Changed
GuildConfig UX: buttons → dropdown flows
Replaces the crowded button matrix with categorized select menus and guided dropdown flows, keeping controls persistent after updates, reducing interaction churn, and scaling better as options grow (modal labels remain within Discord limits).
Custom prefix handling fully honored across the stack
Fixes a routing issue where certain handlers could fall back to a default or stale cached value. The active prefix is now resolved from guild storage with short-lived caching, invalidated immediately on update, and applied consistently across messageCreate, help text, and telemetry. Direct messages continue to use the global default.
Removed
Legacy social media commands and helpers
Deprecated social commands and their utilities have been removed to reduce surface area and maintenance overhead. Use the site/about links or updated integrations instead.
Breaking Changes
Global Chat defaults enabled; requires channel binding
The Global Chat toggle now defaults to enabled, but no messages will bridge until a valid Global Chat channel is configured. Admin action required: bind a channel to activate. Integrations/scripts relying on implicit enablement must check for both the enabled flag and a configured channel.