Guides

Feature Stages

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

Best Practices

Best practices for running Code Blind in production.

Code Blind Game Server Client SDKs

The SDKs are integration points for game servers with Code Blind 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

Player Tracking

Track player connections, disconnections, counts and capacities through the Code Blind SDK

Local Game Server

Register your local game server with Code Blind.

Latency Testing with Multiple Clusters

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

Metrics

Access Code Blind via the Kubernetes API

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

Troubleshooting

Troubleshooting guides and steps.