channel-system

Coordinate Oxidus channel modules and central daemon for message routing and delivery.

8|3|Updated Sep 29, 2021
One-click install
npx skills add https://github.com/gesslar/oxidus-mudlib --skill channel-system
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: channel-system
Source: https://github.com/gesslar/oxidus-mudlib/tree/main/.claude/skills/channel-system
Command: npx skills add https://github.com/gesslar/oxidus-mudlib --skill channel-system

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Understand and extend Oxidus' channel communication system, enabling modular channel modules, persistent histories, and GMCP integration for in-game chat.

Core Features & Use Cases

  • Central channel daemon for registration, routing, and tuning.
  • Per-channel module architecture with permission checks and history.
  • Supports built-in commands and dynamic channel modules for new networks.

Quick Start

Create a new channel module by inheriting D_MOD_CHANNEL, define its channel_names, and rely on CHAN_D to register it.

Frequently Asked Questions about channel-system

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a modular channel module for a MUD daemon?

To create a modular channel module, inherit D_MOD_CHANNEL, define your channel_names, and rely on CHAN_D to register it. The central daemon handles routing, permission checks, and message broadcasting across the new module.

How does GMCP message broadcasting work with in-game chat channels?

GMCP message broadcasting works by routing formatted channel messages through the central daemon. The daemon coordinates module-based rec_msg formatting and broadcasts outgoing messages to connected clients using the GMCP protocol.

What is the best way to enforce per-channel permissions in a MUD?

The best way to enforce per-channel permissions is through modular channel architecture. Each channel module implements an is_allowed check, letting the central daemon verify user access before routing messages or chat history.

How do I track persistent chat history for specific in-game channels?

You can track persistent chat history by utilizing the per-channel module architecture. When registered with the central daemon, each module maintains its own history records, ensuring past channel messages are retained.

Does the central channel daemon support dynamic registration of new channel networks?

Yes, the central channel daemon supports dynamic registration of new channel networks. By creating new channel modules that inherit D_MOD_CHANNEL, the system dynamically registers and routes messages for new networks.