Message Forge

Purpose

Message Forge is the shared message composer for reusable staff messaging, panel content, DM templates, and feature-owned templates.

Prerequisites

• Access to message-forge panel.
• Feature-specific panel access to edit feature-owned configs (Join Quests, Portals, Spotlight).

Dashboard Settings

• Compose text/media/files/action rows/selectors.
• JSON import/export and clipboard transfer.
• Hard limits:
  • 40 components per config
  • 4000 total text characters

Command Surface

• No direct slash command.
• Consumed by feature flows and command outputs that render Message Forge content.

Permissions And Entitlements

• Library configs use owning_feature: message_forge and are plan-limited.
• Feature-owned configs are controlled by the owning feature and bypass library lock counts.
• Role-scoped controls are validated on save for role-bound component content.

Operational Example

1. Create a reusable announcement block in Message Forge library.
2. Create a feature-owned config from Portals DM tab.
3. Validate both in preview/send flow.

Edge Cases

• Empty text blocks are rejected.
• Empty action rows/containers are rejected.
• Panel contexts can require Join Quest Selector or Portal Selector blocks.
• DM contexts reject interaction blocks.

Troubleshooting

• Save denied or lock warnings: verify subscription limits and unlocked config count.
• Send/Sync disabled for panel content: add required selector blocks.
• Role validation errors: check referenced roles against your role scope.