"End of Communications upon penalty of law."
[image: image.png]
On Mon, Nov 16, 2020 at 4:35 PM Melvyn Depeyrot
wrote:
> damn bro that's not very nice :(
>
> On Nov 16 2020, at 1:27 pm, Harlen Linke wrote:
>
> Melvyn, no one cares about your point by point take downs either. The
> thread
I have seen some crazy stuff on this list over the last 15 years or so, but
this might just be the craziest.
No one is intimidated by a troll who claims to be a lawyer but takes 3
tries to get the words "International Legal Counsel" spelled correctly. I
mean, seriously, come on. Although that
Wow, thanks for fixing that so quickly!
On Thu, Jun 7, 2018 at 3:13 PM, Eric Smith wrote:
> We've added the HLCoders mailing list. You should be able to subscribe now
> if you'd like.
>
> Thanks.
>
> -Eric
>
>
> -Original Message-
> From: hlds@list.valvesoftware.com On Behalf
> Of
I noticed that, too. It looks like hlcoders was dropped when they
transitioned to the new listserv platform. I was disappointed by that.
On Thu, Jun 7, 2018 at 1:47 PM, Björn Stabel wrote:
> It seems the list "hlcod...@list.valvesoftware.com" has disappeared.
>
> There used to be some amount
Nope.
On Thu, Nov 9, 2017 at 12:00 PM, pilger wrote:
> Isn't there a moderator in charge of this list?
>
>
> _pilger
>
> On 9 November 2017 at 14:22, Chris Dunphy wrote:
>
>> I think that was the most embarrassing little "fight" I've ever seen on a
>>
Hello,
This is usually caused by an attack which simply floods the server with
queries (usually A2S_INFO).
This happened on one of my servers a few months ago (running on Linux), and
the offending IP address was owned by NFO. I contacted them and had a good
discussion with a few of the NFO
ack,
> since it's intended obviously to make effected systems take the knee-jerk
> reaction of blocking or reporting NFO as a bad player - when I'm fact the
> traffic isn't really coming from them.
>
> I just switched to them as a host, and love it so far.
> On Jan 18, 2016
Hello,
I was investigating a report that CheckValve shows mangled information for
HLTV servers, and I discovered that HLTV returns two response packets to an
A2S_INFO query. The first response is in the old GoldSrc format (with
header byte 0x6d) and the second response in the Source format (with
Hello!
I just wanted to mention that I recently released version 2.0 of
CheckValve, my HLDS/SRCDS query app for Android. If you use CheckValve, I
would love to get some feedback regarding the new version. CheckValve 2.0
includes several bug fixes and code changes, as well as a few new
features.
If you absolutely need to leave RCON enabled, then restricting access to it
with a firewall rule is probably the best option. In other Valve games
there were server cvars to control the number of failed RCON attempts
before a client was banned:
sv_rcon_banpenalty
sv_rcon_maxfailures
Why not? Because you personally don't like it? Is there an etiquette
document for this list which says that you shouldn't reply to update
threads?
They're threads on the mailing list just like any other. He had a valid
question about something which apparently broke in the update, and Eric
I e-mailed Alfred about this a few days ago and he said that it's gone for
good. However, only my TF2 and CS:S servers have been affected so far.
A2A_PING still works on my L4D and L4D2 servers (both updated).
Alfred recommended using A2S_INFO as a replacement for A2A_PING from now on.
-
12 matches
Mail list logo