Here is the error message I get when I want to join my server which is now
displaying 25 slots again! I have not restarted it since yesterday.
Server Experience Warning
The server you are connecting to allows up to 25 players.
Team Fortress 2 was designed to have an optimal experience within a
Every damn morning about 7 am (+10 seattle time) the server i have less
popularity, fills up with canadian, brazilian, usa, south-korea, chile
and so on. Players with those countries. My server is in northern
europe, Finland (which is funny).
Something funny going on with the quickplay. I
NET_QueuePacket: Oversize packet from 187.45.206.108:19NET_QueuePacket:
Oversize packet from 71.13.229.61:19NET_QueuePacket: Oversize packet from
216.245.202.53:19NET_QueuePacket: Oversize packet from
70.84.217.91:53NET_QueuePacket: Oversize packet from
70.84.217.91:53NET_QueuePacket:
Yes. I have also been matchmade to servers really far away when I know for
a fact that there are available servers close by (like say those run by me
or my friends and ofcourse other servers in the area...).
There's definitely enough east coast servers to put the 4 people in my
party on, but
I just posted a small patch to nemrun that fixes an odd bug people have
been reporting forever - screens randomly not 'quitting' when using the
default kill-script. Turns out the issue is screen does not default to the
only 'window' until someone has manually connected to the screen, so if you
Thanks again! :)
Chris
On Wed, Jul 25, 2012 at 1:11 PM, John Schoenick nephy...@doublezen.netwrote:
I just posted a small patch to nemrun that fixes an odd bug people have
been reporting forever - screens randomly not 'quitting' when using the
default kill-script. Turns out the issue is
Thanks Neph!
Kyle.
On Wed, Jul 25, 2012 at 10:15 AM, Chris Oryschak ch...@oryschak.com wrote:
Thanks again! :)
Chris
On Wed, Jul 25, 2012 at 1:11 PM, John Schoenick nephy...@doublezen.netwrote:
I just posted a small patch to nemrun that fixes an odd bug people have
been reporting
The new centralized matchmaking should not affect either the server info or
invite-to-game functionality. If you are able to confirm this is happening,
please let me know. The two systems are basically unaware of each other's
existence.
-Original Message-
From:
Hello again,
The es.flags() function in eventscripts python actually worked really well
for what I was looking for.
Thank you so much.
- Bruno
On Mon, Jul 23, 2012 at 6:20 PM, Saul Rennison saul.renni...@gmail.comwrote:
It prevents the ConVar being returned in A2S_RULES (and so it will be
It looks like geolocation is failing for a much larger number of players than
is expected.
I'll look into it.
Thanks again for the reports. Keep 'em coming.
-Original Message-
From: hlds_linux-boun...@list.valvesoftware.com
[mailto:hlds_linux-boun...@list.valvesoftware.com] On Behalf
Is there anyone who runs a Ship server on linux?
The problem I'm running into is that it just freezes, stops before it
gets very far.
I've done some research but the best I can find is threads leading nowhere
and some strange report that it needs updated binaries, something about
master servers?
http://forums.blazinggriffin.com/viewtopic.php?f=10t=26
This is as far as I got. Valve changed you connect to the master servers a
long while back, the devs never updated it for linux, and the only solution
was on a forum long dead.
The only other option I have is to try running wine :(
On Wed,
And thank you for looking into it :)
On Wed, Jul 25, 2012 at 5:06 PM, Fletcher Dunn
fletch...@valvesoftware.comwrote:
It looks like geolocation is failing for a much larger number of players
than is expected.
I'll look into it.
Thanks again for the reports. Keep 'em coming.
13 matches
Mail list logo
