Flow Now Gaming

Part of the Plugin data protocol. Packet: Packet-mumcord-nowgaming. Sibling flow: Flow-Now-Playing.

Flow: now gaming

Shows the game a user plays, with an optional "Join game" link, to everyone on the server.

sequenceDiagram
    participant A as Client A (user plays a game)
    participant S as Mumble server
    participant B as Client B (any other client)
    A->>A: game process detected
    A->>S: plugin data mumcord.nowgaming
    S-->>B: relayed
    loop every 60 s while playing
        A->>S: same payload again
        S-->>B: relayed
    end
    Note over A,B: A newcomer gets the current payload once, after the hellos
    A->>S: payload without game (stopped)
    S-->>B: relayed, B clears the game

Loading

Steps

1. The client looks for a running game every 5 seconds (POLL_INTERVAL). A new, changed or ended game counts as a change.
2. On a change, the client sends mumcord.nowgaming to everyone on the server, resends it every 60 seconds (RESYNC), and sends it once to each person who joins.
3. The receiver shows the game name and icon (from the Steam CDN when steam_app_id is set). If join is present and valid, it offers "Join game".
4. When the game ends or the setting is turned off, the client sends {"v":1} and receivers clear the entry.

Official clients see a "Game" line in the user's comment, written after a 5 second settle time.

Limits and errors

• Game name at most 100 characters.
• join must be steam://connect/<host>:<port> with port 1 to 65535; otherwise it is dropped. The receiver must validate it before handing it to the operating system.
• Lost updates are repaired by the 60-second resend.
• Unknown fields are ignored; v below 1 drops the message.

Packets used

Packet-mumcord-nowgaming, with Packet-mumcord-hello for joining people.