The Master server and 2.7.0

For all the help you need with Armagetron!
Post Reply
User avatar
DrJoeTr0n
"On a Roll. Paper wise."
Posts: 815
Joined: Fri Mar 05, 2004 6:49 am

The Master server and 2.7.0

Post by DrJoeTr0n »

Hey everyone. I seem to have a new bug with 2.7.0

For some reason I cannot populate a legitimate server list. It used to be fine, than one day it just stopped picking up some servers. Then stopped all together. But since I also 2.8 I tried that and it is picking them up just fine.

I use 2.7 for my server because everything is hot keyed and what have you for it. I can only access my server through LAN. But is reachable over the internet with 2.8. Which is making me wonder, does everyone on 2.7 currently having this problem? I had reports that my server was down all last week. Which I find funny because my server was up all of that week and active.

I would like to not go 2.8 permanently because I all of my admin and original stuff is set up.
User avatar
Z-Man
God & Project Admin
Posts: 11770
Joined: Sun Jan 23, 2005 6:01 pm
Location: Cologne
Contact:

Post by Z-Man »

The master does not treat 0.2.7.0 clients or servers any differently from 0.2.8_beta, so the reason lies either in a bug in 0.2.7.0 itself (but I can't remember fixing anything) or just your usage pattern. The client always remembers the list it got from the master server, so as long as you only browse the list when a server is online, it will never disappear from your list. The master however polls servers all of the time and removes them if they don't answer for some hours, knowing the server will reconnect and refresh its entry.
This won't work if the server keeps running and only loses its network connection, then the master will delete the server entry, but the server won't connect to refresh it. The way to work around that is to set DEDICATED_IDLE to some low value, like 2 or 4 hours, and run the server in a loop.
That's all I can think of.
Post Reply