Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement Mud Server Status Protocol (MSSP) #131

Open
mystiker opened this issue Nov 4, 2024 · 1 comment · May be fixed by #133
Open

Implement Mud Server Status Protocol (MSSP) #131

mystiker opened this issue Nov 4, 2024 · 1 comment · May be fixed by #133
Assignees
Labels
backend This issue is specific to the backend qualify Issues that need to be discussed further

Comments

@mystiker
Copy link
Collaborator

mystiker commented Nov 4, 2024

Description:
Implement support for the Mud Server Status Protocol (MSSP) to allow the client to request and receive detailed information about the server’s configuration, capabilities, and status. MSSP is particularly useful for MUD clients that want to display server-specific details to the user, such as player count, game genre, uptime, and other server characteristics.

Details:

  1. Option Code: 70

  2. Functionality:

    • MSSP enables the server to provide structured information as a list of key-value pairs, detailing various aspects of the server environment.
    • Common MSSP fields include server name, version, player count, maximum players, genre, and uptime, among others.
    • The client initiates MSSP by sending IAC DO MSSP, and the server responds with IAC WILL MSSP if it supports the protocol.
    • Once agreed upon, the server sends IAC SB MSSP followed by key-value pairs, ending with IAC SE.
  3. Expected Workflow:

    • The client sends IAC DO MSSP to request server status information.
    • Upon receiving IAC WILL MSSP from the server, the client waits for the server to send IAC SB MSSP followed by a list of key-value pairs with server information.
    • The client should parse and display or log these details for the user, providing insight into the server’s status and configuration.
@mystiker mystiker added backend This issue is specific to the backend qualify Issues that need to be discussed further labels Nov 4, 2024
@mystiker mystiker linked a pull request Nov 4, 2024 that will close this issue
@mystiker mystiker linked a pull request Nov 4, 2024 that will close this issue
@mystiker mystiker linked a pull request Nov 4, 2024 that will close this issue
@myonara
Copy link
Contributor

myonara commented Nov 25, 2024

has no priority to me, as such information needs some sort auf header or footer line with such informations in a standard way. May be reconsidered, if more then UNItopia is supported.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend This issue is specific to the backend qualify Issues that need to be discussed further
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants