Emotional Damage

It adds sarcasm, jokes, roasts, random thoughts, chat prompts, and interactive chaos while giving server owners control over where and how it behaves. It is designed to make people talk, laugh, react, and come back.

Server owners control where adult humor, message replies, reactions, and direct roasts are enabled. They can also set profanity levels from clean through heavier 21+ language and choose roast intensity from playful through brutal/unhinged 21+ modes. The bot is entertainment, not moderation, and the public launch plan keeps those controls opt-in instead of default-on.

Emotional Damage action channels can operate as clean panel surfaces with pinned buttons, while public bot responses and conversation happen in one managed chat thread per channel. Server owners can dry-run legacy layout migration, refresh compact headers, create/reuse managed threads, and clean only bot-created panel channels. Connected community chats are behavior-only snark/reaction zones and are never cleaned, purged, locked, or reset by the bot.

Owners acknowledge the 21+ disclaimer privately, choose setup style, personality, profanity level, and feature toggles, then confirm before the bot creates or reuses any recommended channels. If DMs are disabled, an owner/admin can fall back to /setup start inside the server.

Managed surfaces keep setup panels, info posts, rules, the central User Hub, compact channel headers, command maps, and summaries refreshable without deleting user content or spamming duplicate bot posts. Important panels are pinned when permissions allow it, and /panel lets members pull the current channel controls back privately if conversation has buried them.

The default layout intentionally does not create a #after-hours text channel or a separate adult-only humor channel. Darker humor, message replies, and reactions remain admin-controlled through settings and allowed channels. Manual channel connection is reserved for existing server chats that admins explicitly want the bot to interact with.

The updated surface model keeps larger help centralized: bot-settings is the admin control center, disclaimer is the user hub and start-here panel, and action channels use pinned compact headers with the few commands and buttons people need in that space. This keeps conversation channels from getting buried under long bot guide posts.

Member buttons are being tuned for low-friction use: profiles and command maps answer privately, action-channel buttons create public bot moments, and confession or bad-idea flows use modals without turning channel history into stored raw watched-message data. Server owners can refresh the hub and compact headers, bump panels when they need to be visible again, and inspect pin status. Legacy bulky guide posts are cleaned only when they are tracked bot-owned messages.

The public disclaimer surface includes an I Agree button. Servers can require acknowledgement before adult or edgier features such as direct roast opt-in, brutal roast modes, confessions, and heavy-language actions.

Anonymous does not mean unmoderated or impossible to trace. The bot keeps minimal moderation metadata for abuse controls and does not expose confession text in admin logs by default.

Profiles such as stoner chaos, gaming trash talk, soft sarcasm, server menace, and after hours influence tone and content packs while admin tone controls remain the cap. Damage stats avoid confession text and are meant to be playful, not harassment tools.

Emotional Damage does not watch every channel by default, does not store raw watched-channel message content, does not record voice, does not listen to voice, and does not transcribe voice.

Tone controls are planned to let admins dial the bot down for lighter community spaces or push it sharper in properly configured 21+ channels.

Profanity controls are separate from tone. Servers can keep public spaces clean or allow mild, moderate, or heavier adult language where appropriate. Slurs, protected-class attacks, threats, self-harm encouragement, and illegal instructions remain outside the product boundaries.

The bot is also being prepared for Railway-friendly operations, including optional startup migrations for test deployments and multi-guild command registration so slash command updates can be pushed quickly across test communities before global rollout. Operators can also run a safe database check to confirm which Railway database the bot is using and whether the social schema migrations actually applied.

For testing, the bot can register commands into every guild it is currently in after startup. Public/global command registration remains available for later rollout when command propagation delay is acceptable.

Operator tools are being shaped around dry-run command cleanup, command diffs, local feature flags, future tier display, guild analytics, and first-run orientation that points new servers to setup without auto-creating channels on join.

The bot is being structured with owner overrides, test guild bypasses, Patreon-skip controls, and future Grizzly Nexus entitlement hooks. Subscription enforcement is not active until the entitlement provider is connected. Local feature flags and a future tier catalog are product-readiness scaffolding, not live monetization.