Hello! For the past few weeks, the server browser in SRB2 doesn't seem to be displaying all available servers properly.
In the first image, you can see my servers being displayed in the CUSTOM room just fine. I had just set these servers to that room today, where previously they were all tied to the STANDARD room (except for ware and battlemod). None of those servers would appear in the STANDARD or CASUAL room whenever I set it to those specific rooms, and the ALL room just flat out refuses to work.
I currently am also hosting a plain vanilla coop server named "Pikaspoop's Vanilla Coop" and have it set to the STANDARD room, as you can see it won't show up.
I hope this helps, if you need additional details or clarification please don't hesitate to ask!
Here's some assorted information I found, I don't know how relevant or useful it is but I thought I should share my observations:
The POST request page for the server list my modded and tag server shows up twice with different public IPs. At the time I recovered from a power outage, so I understand the new IP (dynamic public IP), but I'm concerned on how long the duplicate entry will be kept and if that's why the issues with the server browser persists.
https://mb.srb2.org/MS/0/rooms/33/servers (Ctrl F and type in Pikaspoop)
Same on the ALL request, except only srb2-ware shows up one time (which makes sense since I put it up after the power outage.
I also noticed that because the casual room uses number 28, it is listed first as it's the smallest number among the other rooms. The ALL room seems to mirror the CASUAL room, so there may be an error occurring before the game can ping the rest of the servers.
This is all very weird
Also I found these: https://mb.srb2.org/MS/0/versions/21 https://mb.srb2.org/MS/0/versions/18
Two version requests with the same version listed, but 18 differs that it shows the number 51 before the version string rather than 1, and 18 is the one srb2 connects to.
EDIT: I completely forgot to mention this, but there's a whole lot of server addresses being sent to clients despite being defunct for a while (including my old IP). An automated routine check and purge of these addresses would be a good temporary fix.
In the first image, you can see my servers being displayed in the CUSTOM room just fine. I had just set these servers to that room today, where previously they were all tied to the STANDARD room (except for ware and battlemod). None of those servers would appear in the STANDARD or CASUAL room whenever I set it to those specific rooms, and the ALL room just flat out refuses to work.
I currently am also hosting a plain vanilla coop server named "Pikaspoop's Vanilla Coop" and have it set to the STANDARD room, as you can see it won't show up.
I hope this helps, if you need additional details or clarification please don't hesitate to ask!
Here's some assorted information I found, I don't know how relevant or useful it is but I thought I should share my observations:
The POST request page for the server list my modded and tag server shows up twice with different public IPs. At the time I recovered from a power outage, so I understand the new IP (dynamic public IP), but I'm concerned on how long the duplicate entry will be kept and if that's why the issues with the server browser persists.
https://mb.srb2.org/MS/0/rooms/33/servers (Ctrl F and type in Pikaspoop)
Same on the ALL request, except only srb2-ware shows up one time (which makes sense since I put it up after the power outage.
I also noticed that because the casual room uses number 28, it is listed first as it's the smallest number among the other rooms. The ALL room seems to mirror the CASUAL room, so there may be an error occurring before the game can ping the rest of the servers.
This is all very weird
Also I found these: https://mb.srb2.org/MS/0/versions/21 https://mb.srb2.org/MS/0/versions/18
Two version requests with the same version listed, but 18 differs that it shows the number 51 before the version string rather than 1, and 18 is the one srb2 connects to.
EDIT: I completely forgot to mention this, but there's a whole lot of server addresses being sent to clients despite being defunct for a while (including my old IP). An automated routine check and purge of these addresses would be a good temporary fix.
Attachments
Last edited:
