Skip to content

Updated requirements #40

Description

@PatrickPedersen

Upcoming Operations Embed

As discussed in issue #1, two implementations for operation messages should be implemented.

  1. Persistent embed that shows a list of upcoming operations.
  2. A scheduled embed that shows a list of upcoming operations at a specific interval. I.e., every day at 19:00 EST.
    This is not a replacement for using Discord's built-in Event system, which the bot should also utilize.

For OPSEC-specific Operations, Discord's built-in Event system should not be used; instead, an OPSEC version of the above two implementations should be used.

New Operation Posted Embed

When a new operation is posted, create a new embed in a game-specific or guild-wide channel. This would allow members to sign up through Discord or to subscribe to operation notifications. Like:

  1. Operation is 30 minutes out.
  2. If operation details are updated. I.e., the start time or the description.

If the operation changes after the fact to OPSEC, ensure the notification is deleted, and any non-OPSEC members are removed from RSVP and operation notifications.

This notification should not be posted to Discord until after 5 minutes to allow the op lead to correct any mistakes made when posting the op.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    Status
    Prioritized

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions