probing… turnier-server/help | last ping gitlab

Turnier-Server

A short document to get you started with the turnier-server.

# Intro

The turnier-server hosts the game lobbies for the final SoPra tournament and lets students test their own client or ai-client implementations against a real server.

The bar at the top of this page probes wss://pac-server.de from your browser every 10s. Green means the server is online and accepting WebSocket connections. Red means it isn't. In that case, give it a few minutes to restart, or contact your tutor if it stays in this state.

# Connect

The server is reachable on this hostname:

wss://pac-server.de

# Report an Bug

Before filing:

  • Status bar above shows the server as reachable.
  • Issue is reproducible with another client.
  • Issue is not yet listed in the repo issues.

If all three hold, open an issue in the turnier-server repo on GitLab. To make it as easily as possible to find your specific bug, use the provided template in the repository.

# FAQ

> Are the configs the same as for the tournament?
Not exactly. The tournament configs will be similar in shape and difficulty to the ones currently on the server, but expect them to differ in the concrete values.
> Closed: "Too many active connections from this IP." — why?
The server enforces a limit on how many WebSocket connections a single IP may hold open at the same time. Once that limit is reached, every additional handshake is rejected immediately with close code 1008.
> Closed: "Message rate limit exceeded." — why?
Each connection has its own message rate limit. If your client sends too many messages in a short period of time, the offending message is dropped and the socket is closed with code 1008.