S. Hendriks wrote:
Suggestion:
- When releasing fixes for bots, TEST THEM FIRST.
Wait, let me rephrase that:
- When releasing ANYTHING, TEST IT FIRST (and ofcourse, with everything.
Run a bot server, run a metamod server)
Actually, it's not really Valve's responsibility to test a server with
Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of S. Hendriks
Sent: Friday, February 13, 2004 10:14 AM
To: [EMAIL PROTECTED]
Subject: RE: [hlcoders] STEAM Update and messing up bots (Again)
I do see your point, but i don't really agree with that. I understand
that changes can
10:59 AM
To: [EMAIL PROTECTED]
Subject: RE: [hlcoders] STEAM Update and messing up bots (Again)
AAAHHH, Isn't the testing the responsibility of the bot maker? Isn't
maintenance the responsibility of the bot maker? Why the heck would Valve
waist money and time testing software they don't develop
Jeffrey botman Broome wrote:
Actually, it's not really Valve's responsibility to test a server with
Metamod, AdminMOD, AMX, bots or any other type of plugin.
Hmm, I'm not so sure about that anymore. I would normally agree
with you there, but Valve is moving from an application to a
platfprm with
Cstrike now uses a hash table in the mod to cache calls to
pfnFindEntityByString(), so you won't be able to intercept them any
longer. You could intercept pfnMessageBegin(), the following set of
calls should be unique to round start:
// reset all players health for HLTV
Florian Zschocke escribió:
Jeffrey botman Broome wrote:
Actually, it's not really Valve's responsibility to test a server with
Metamod, AdminMOD, AMX, bots or any other type of plugin.
Hmm, I'm not so sure about that anymore. I would normally agree
with you there, but Valve is moving from an
6 matches
Mail list logo
