Guides for deeper integrations with Agones

Feature Stages

This page provides a description of the various stages that Agones features can be in, and the relative maturity and support level expected for each level.

Best Practices

Best practices for running Agones in production.

Agones Game Server Client SDKs

The SDKs are integration points for game servers with Agones itself.

Windows Gameservers

Run GameServers on Kubernetes nodes with the Windows operating system.

Fleet Updates

Common patterns and approaches for updating Fleets with newer and/or different versions of your GameServer configuration.

GameServer Health Checking

Health checking exists to track the overall healthy state of the GameServer, such that action can be taken when a something goes wrong or a GameServer drops into an Unhealthy state

GameServer Counters and Lists

Track, allocate and auto-scale based on user defined counters and lists stored on a GameServer.

Player Tracking

Track player connections, disconnections, counts and capacities through the Agones SDK

Local Game Server

Register your local game server with Agones.

Latency Testing with Multiple Clusters

When running multiple Agones clusters around the world, you may need to have clients determine which cluster to connect to based on latency.


Access Agones via the Kubernetes API

It’s likely that we will want to programmatically interact with Agones. Everything that can be done via the kubectl and yaml configurations can also be done via the Kubernetes API.


Troubleshooting guides and steps.

Last modified July 17, 2024: Introduce external resource(s) on multiplayer game programming to docs (#3884) (03a0a4c)