Epic: Message Channel System #130

New issue

Open

opened 2026-03-15 04:13:28 +00:00 by freemo · 0 comments

freemo commented

2026-03-15 04:13:28 +00:00

Owner

Metadata

Commit Message: feat(ui): implement message channel system
Branch: feature/message-channels

Background and Context

The specification (§ Message Channel System) describes named message channels that
route output to specific windows with per-player filtering. Channels enable players
to control where different types of messages appear and which ones are muted.

Acceptance Criteria

MessageChannel data model with name, display_name, default_window, filterable, admin_only
ChannelRegistry for registering and querying channels
ChannelRouter resolves output to the correct window respecting mute/override settings
Player commands: channels, setchannel, mute, unmute, resetchannels
Channel preferences persisted in player save/load
Backwards compatibility with existing output calls
BDD test coverage

Subtasks

Implement MessageChannel and ChannelRegistry
Implement ChannelRouter
Implement player commands
Add output pipeline integration
Add persistence

Definition of Done

This Epic is complete when all child issues are closed.

## Metadata - **Commit Message**: `feat(ui): implement message channel system` - **Branch**: `feature/message-channels` ## Background and Context The specification (§ Message Channel System) describes named message channels that route output to specific windows with per-player filtering. Channels enable players to control where different types of messages appear and which ones are muted. ## Acceptance Criteria - MessageChannel data model with name, display_name, default_window, filterable, admin_only - ChannelRegistry for registering and querying channels - ChannelRouter resolves output to the correct window respecting mute/override settings - Player commands: channels, setchannel, mute, unmute, resetchannels - Channel preferences persisted in player save/load - Backwards compatibility with existing output calls - BDD test coverage ## Subtasks - [ ] Implement MessageChannel and ChannelRegistry - [ ] Implement ChannelRouter - [ ] Implement player commands - [ ] Add output pipeline integration - [ ] Add persistence ## Definition of Done This Epic is complete when all child issues are closed.