Skip to content

Redesign party commands #600

Description

@Askaholic

It may be better to send party commands using a single command with many subcommands than our current implementation of having a separate command for every action.

We could go with a "polymorphic" approach:

{
    "command": "party",
    "action": "invite",
    "recipient_id": <player_id>
}

Or more of a "compositional" approach:

{
    "command": "party",
    "action": "invite",
    "data": {
        "recipient_id": <player_id>
    }
}

The compositional approach has a little more boilerplate built into the message, but it feels cleaner to me.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions