Spring RTS Engine

whats up with the server randomly discing and timing people out in mass

probably just some connection hickups, it isn't under high load or anything AFAICS.

I get timeouts and lag spikes in the evening, the time when lots of users are on.

Apparently AFlobby (or IgnitionHub, whatever it is called) has good tolerance for this type of situation. I plan on trying it, if I can get it to run portably.

Tribulex wrote:Apparently AFlobby (or IgnitionHub, whatever it is called) has good tolerance for this type of situation. I plan on trying it, if I can get it to run portably.

If the server loses connection with you... you're going to disconnect irrelevant of what the client does. A nicer client then the TAS client might retry until it repairs the connection, much like hydra IRC does, but it won't fundamentally be able to magically keep you connected when the you disappear server side.

The JAVA grand master wizard cant just will the connection to exist?

AFLobby is more tolerant of connection hiccups as the connection code runs in a dedicated thread, issues PING in a dedicated timer thread too, prioritizes the PING above other traffic being sent, and sends it more often. As a result AFLobby clients are less likely to be booted for 'inactivity'

Sadly the download links for AFLobby are not working as when darkstars was hacked and all the files wiped, I never put it back up. I'm not happy with AFLobby 4.2, and although my personal builds are a vast improvement, there are some thing that need changing before I can put it out as beta 5.

I also need to announce the new name too.

AF wrote:AFLobby is more tolerant of connection hiccups as the connection code runs in a dedicated thread, issues PING in a dedicated timer thread too, prioritizes the PING above other traffic being sent, and sends it more often. As a result AFLobby clients are less likely to be booted for 'inactivity'

no more no less than what TASclient & SpringLobby do, and FYI I never got dropped during those mass kicks either; as swiftspear pointed, they are totally unrelated to lobby clients since they were caused by connection troubles by the server ...

AF wrote:AFLobby is more tolerant of connection hiccups as the connection code runs in a dedicated thread, issues PING in a dedicated timer thread too, prioritizes the PING above other traffic being sent, and sends it more often. As a result AFLobby clients are less likely to be booted for 'inactivity'

Sadly the download links for AFLobby are not working as when darkstars was hacked and all the files wiped, I never put it back up. I'm not happy with AFLobby 4.2, and although my personal builds are a vast improvement, there are some thing that need changing before I can put it out as beta 5.

I also need to announce the new name too.

If AFLobby is not publically available for people to use, it really doesn't matter what its capabilities are.

Its in the svn if anyone desperate enough for it want to compile and run it.

As BD said, the issue wasn't dependent upon the lobby clients...even the mighty aflobby is unable to maintain a connection if the server cuts it

Now it's constantly crapping out with less than 100 users, is Betalord running a bittorrent on the server or something?

I haven't been impacted by these disconnections so far (my autohost and BuildServ are connected 24/24). So I guess it's a peering problem...

KDR_11k wrote:Now it's constantly crapping out with less than 100 users, is Betalord running a bittorrent on the server or something?

Betalord does not run the server, fnordia does.