Skip to content

Non-Steam masterservers do not list my ReHLDS server even though heartbeats and A2S_INFO responses work #3971

@ElijonNikoliqi

Description

@ElijonNikoliqi

Description: I am trying to get my CS 1.6 server listed on Non-Steam master servers to attract players using different builds. I have a custom AMXX plugin that successfully sends heartbeats to a list of 61 master servers (Setti, Tsarvar, etc.), but the server is still not showing up in the "Internet" tab.

The Problem: My server is running ReHLDS with Reunion 0.2.0.25. Even though Reunion is running, the command dp_r_protocol returns 0. I believe this is why the master servers are rejecting my server, as they require a valid protocol (48/47) to list the server.

My Setup:

Engine: ReHLDS

Protocol Fix: Reunion 0.2.0.25

Connectivity: Ports are open (Server is visible on GameTracker).

Master Server List: 61 servers configured in setmaster.ini.

My Questions:

How can I fix Reunion so it correctly reports Protocol 48 instead of 0, so Non-Steam master servers will accept my heartbeats?

Are there any specific ReHLDS or Reunion settings required to make the server visible to Non-Steam master server browsers in 2026?

Is there a better way to "force" the server onto the master lists when using ReHLDS?

Current status: meta list shows Reunion is RUN. dp_r_protocol is 0. Server is Online, but invisible in the in-game browser in non-steam clients.
if anyone can help me i will apriciate it

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions