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

ADR - Server/Client Heartbeat #14

Open
thoraxe opened this issue Feb 10, 2023 · 0 comments
Open

ADR - Server/Client Heartbeat #14

thoraxe opened this issue Feb 10, 2023 · 0 comments

Comments

@thoraxe
Copy link
Contributor

thoraxe commented Feb 10, 2023

ADR Context / Overview

A heartbeat is needed so that servers and clients can decide about the health of their connection to the game environment. As an example, if a client dies without sending a leave message, that player simply idles forever.

Decision

A new protobuf security message type (heartbeat) will be implemented
Clients will send regular heartbeat messages
The server will discard players that it does not receive regular heartbeat messages from

Rationale

We don't want orphaned players or clients thinking the game is still going when it isn't

Status

Proposed

Consequences

The clients currently don't care which, or any, server they are working with. As we have one server today, it's not much of a problem. However, when we get to multi-server, we may need to figure out some kind of hand-off and to figure out how to make the client care about its specific server

Authors

@thoraxe

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

No branches or pull requests

1 participant