General solution for comms channels #405

Open
opened 2025-01-17 14:42:15 -08:00 by scionaltera · 0 comments
scionaltera commented 2025-01-17 14:42:15 -08:00 (Migrated from github.com)

Right now all the "channels" for communication are implemented separately. It would be nice to refactor so that there are a number of kinds of channels defined by who messages are delivered to (e.g. to-room, to-zone, to-world, direct) but the channels themselves could be created and edited dynamically with an in-game editor. Basically there are a bunch of predetermined types of channels and this would just be creating new skins. It wouldn't be able to filter down to special cases like guild or clan channels without a code change to add a new type for that, but it would provide a framework for adding new types in the future.

If you wanted to add an "OOC" channel or an "auction" channel that works like "gossip" does, you'd choose the "to-world" channel type, set a name, a command, colors and formats and create the channel.

Some ideas for properties a channel could have:

  • Name (e.g. auction)
  • Command (e.g. AUCTION)
  • Type (e.g. to-world or to-room-target)
  • Formats
    • to self
    • to target (optional)
    • to others
Right now all the "channels" for communication are implemented separately. It would be nice to refactor so that there are a number of kinds of channels defined by who messages are delivered to (e.g. to-room, to-zone, to-world, direct) but the channels themselves could be created and edited dynamically with an in-game editor. Basically there are a bunch of predetermined types of channels and this would just be creating new skins. It wouldn't be able to filter down to special cases like guild or clan channels without a code change to add a new type for that, but it would provide a framework for adding new types in the future. If you wanted to add an "OOC" channel or an "auction" channel that works like "gossip" does, you'd choose the "to-world" channel type, set a name, a command, colors and formats and create the channel. Some ideas for properties a channel could have: * Name (e.g. auction) * Command (e.g. AUCTION) * Type (e.g. to-world or to-room-target) * Formats * to self * to target (optional) * to others
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
agony-forge/agonyforge#405
No description provided.