When allocated, the sample starts a TCP server on the port defined in the server.json file
When de-allocated, this TCP server is stopped
Dynamic server query results
Data such as number of players, map name, etc. are handled appropriately
sqp and a2s query protocols supported over the query port defined in the server.json file
Backfill allocation keep alive
If "enableBackfill"="true" is set on the server.json then the server will support keeping alive a backfill ticket in the matchmaker
If you are not using the production matchmaker gateway URL (https://matchmaker.services.api.unity.com), then you can change this location by setting the matchmakerUrl parameter in your build configuration settings
e.g. "matchmakerUrl": "https://matchmaker-stg.services.api.unity.com"
A TCP connection can be opened with a netcat command: nc <ip> <port>. Once the connection is opened, this connection represents a player - as such, the 'Concurrent Users' count will be updated in the dashboard