SKWOLETS / DEV LOG / 001

MORE THAN A
SERVER LIST

Building a custom master server

MASTER SERVER

A master server is the dispatcher of the game's infrastructure. It knows which servers are running, who is playing on them, and which servers are available for connection.

When a game server starts, it reports the following information to the master server:

STATUS

The server is running and responding.

NAME

Server name and identifier.

PLAYERS

Current number of players.

SLOTS

Whether there is a free slot available.

THE FIRST VERSION

This is what the system looks like from the player's perspective. The master server collects information from game servers and builds an up-to-date list of available connections.

PRE-ALPHA

All materials shown are from an early stage of development. Visual elements, interface, mechanics and game systems may change during development.

The servers shown are test data generated exclusively to demonstrate how the browser works.

WHY BUILD OUR OWN SYSTEM

Because someone else's solution means someone else's limitations.

That's why I am building the core infrastructure from scratch. Without relying on third-party solutions. Without hidden limitations. With full control over how players access the game world.

Which servers are displayed in the list.
How quickly information is updated.
How search, filters and sorting work.
How the connection process works.
NO EXTRA NODES. This is not just a technical decision — it is the foundation for a fair and transparent game.

HEARTBEAT SYSTEM

How does the master server know that a game server is still running?

Game servers regularly send special signals — Heartbeat.

GAME SERVER I AM ONLINE
HEARTBEAT
MASTER SERVER SERVER RESPONDS

[10:42:01] HEARTBEAT received

[10:42:01] server: eu-hardcore-01

[10:42:01] players: 30 / 60

[10:42:01] status: ONLINE

[10:42:01] server is healthy

If a server stops sending Heartbeat signals, the system knows that it is no longer available and automatically removes it from the list.

SERVER ONLINE → HEARTBEAT → MASTER → VISIBLE

CONNECTION QUEUES

A full server is not the end.

If a server is full, the player does not simply receive a connection error. They can take a place in the queue.

GAME SERVER 60 / 60 FULL
→
MASTER SERVER QUEUE
1 2 3 4 5
→
PLAYER #3 WAITING

WHAT DOES THIS GIVE THE PLAYER

📶

UP-TO-DATE SERVER LIST

Players see real servers and their current status. Offline and unavailable servers disappear automatically.

🔗

RELIABLE CONNECTION

The entire process is controlled — from discovering the server to checking availability and free slots.

⚙

MORE POSSIBILITIES

The custom architecture makes it possible to create priorities, filters, ratings, favorites and special access modes.

FEATURES

In the future, the server list can display much more than just a name and player count.

THIRD PERSON VIEW AVAILABLE
VOICE CHAT ENABLED
GAME MODE HARDCORE
WEATHER RAIN

ACCESS CONTROL

Our own infrastructure provides full control over the interaction between servers and players.

WHITELIST

Management of allowed users.

BLACKLIST

Restricting access for rule breakers.

PRIORITY

Connection priorities.

QUEUE

Queue management.

CONCLUSION

This is only the first stage of the system's development.

The master server can already discover game servers, monitor their status, manage connections and handle player priorities.

In the future, the system will continue to evolve alongside SKWOLETS — adding new ways to discover servers, manage queues, control access and interact with the community.