Opened 8 years ago

Last modified 20 months ago

#3787 new enhancement

Network window — at Version 5

Reported by: elexis Owned by:
Priority: Should Have Milestone: Work In Progress
Component: Network Keywords: patch
Cc: Patch:

Description (last modified by elexis)

There should be a network window listing all relevant information and giving access to hosting related actions. It should be accessible both from gamesetup and session (while #3263 only makes sense in the session, since the gameattributes are already listed in gamesetup).

  • List of players and observers
  • In the session: Connection state of players (see who is disconnected)
  • should show performance stats of the clients
    • meanRTT (#3264)
    • dropped packets?
    • average actual turn length to estimate individual cpu-performance-lag (i.e. the time a client needs to compute the next simulation-state)
  • should allow the host to
    • kick/ban by clicking on a button (#3765)
    • local mute by clicking on a button (#3380)
    • set maximum number of observers (#3671 and #3254)
  • Show who hosts the game

Change History (5)

comment:1 by elexis, 8 years ago

Component: UI & SimulationNetwork

(changed component to network)

comment:2 by elexis, 8 years ago

Keywords: patch rfc added
Milestone: BacklogAlpha 21

https://github.com/elexis1/0ad/tree/3787-network-window

Implemented network window showing a sortable list of clients. The window can be opened from the session menu and a gamesetup button. It is reloaded if someone joins or leaves. It has a kick and ban button.

Unless someone argues that's not useful, the network code should be adapted so that we can see the latency of all players in that window, perhaps even lost packets.

Edit: The branch is not updated anymore.

Last edited 5 years ago by elexis (previous) (diff)

comment:3 by Imarok, 8 years ago

Description: modified (diff)

comment:4 by elexis, 8 years ago

Keywords: rfc removed
Milestone: Alpha 21Backlog

comment:5 by elexis, 8 years ago

Description: modified (diff)
Note: See TracTickets for help on using tickets.