Master server broadcasting for any game
To connect to Broadcast with your application, check the Releases page and download either:
- netcoreapp3.0 (if your application is .NET Core compatible)
- net471 (if your application is .NET Framework 4.X compatible, like Unity is).
Put the two libraries (BroadcastClient and BroadcastShared) anywhere in your project to use them.
Before using the client, you have to instantiate it.
BroadcastClient clientInstance = new BroadcastClient(string broadcastServerAddress, string nameOfYourGame, bool allowOnlyIPV4)
Notes :
- If you choose to allow IPV6 (by setting
allowOnlyIPV4tofalse), DNS resolution may be extremly slow due to a Microsoft bug. - The client does not connect to the server upon construction. It will try establishing a connection when contacting the server. That connection is managed by the BroadcastClient - in case of connection loss, it will reconnect automatically when needed.
| I want to | Function | Returns | Info |
|---|---|---|---|
| Get the list of lobbies for my game | clientInstance.GetLobbyList() | Read-only list of object | Returns the local list, does not connect to the server. Use UpdateLobbyList to update that list. |
| Fetch the list of lobbies from the server | clientInstance.UpdateLobbyList(Query customQuery=null) | Nothing | |
| Create a new lobby | clientInstance.CreateLobby(...) | The lobby you just created, but with an ID delivered by the server | |
| Update information for my lobby | clientInstance.UpdateLobby( object) | Nothing | |
| Kill my lobby and remove it from Broadcast | clientInstance.DestroyLobby(uint lobbyID) | Nothing |
Download a binary from the /Releases section according to what you have
- winx86 for Windows 32 bit
- winx64 for Windows 64 bit
- linux-x64 for Linux 64 bit, any distro
- linux-arm for Linux ARM, like Raspbian
Unzip and run Broadcast(.exe). This should work out of the box.
- Broadcast runs on port 4004
- Lobby that hasn't sent trace of life in the past 30 seconds are cleaned up and destroyed from the server
- Broadcast uses the major version number (X) to signal compatibility break. Minor version number and revision number (Y and Z) are usually quality of life improvements or bugfixes, but no protocol change.
- Broadcast returns maximum 200 lobbies when queried