[cod] 1.3 patch has ruined my clan

[cod at kaleplek.net]

Or better all, just ignore it, that's what i did. I was waiting until Ryan
posted something, i know he is one of the programmers and would give his
answer soon. But now i know why Ryan was so late. Was it fun Ryan???
(sorry a bit off topic).

Ryan to give you a little push i saw some people here who has made a pk3
fix file maybe this is an answer in the right direction.

Regards
Quint

> Thanks for the update there ryan. These things take time even had this
> been a global bug tracking it down would not be instant and there
> is a workaround which was provided on this list. That's the great thing
> about this and the other server lists there is such a wealth of
> experience and talent on them that they ( imo ) provide better support
> than official help lines etc. To provide that quality of support ( the
> amount of in-depth knowledge ) would cost a fortune, see support for a
> product like oracle for example.
>
> Please don't forget IW got us the linux server on release and in that
> respect are well ahead of a number of companies. Please be patient
> people, have respect. This list does get listened to so if there is an
> issue post it but don't start bitching if its not fixed the next day.
>
>     Steve / K
> ----- Original Message -----
> From: "Ryan C. Gordon"
>
>> >   Sorry, I'll get off my soap box now. :-)   Yeah, this touched a
>> > nerve...  I like CoD, and I think IW has done a great job, it's just
>> they need to get serious about Linux.
>>
>> Fwiw, Infinity Ward and Activision _are_ really serious about Linux
>> servers; moreso than most developers (and publishers!) than I've seen.
>>  1.3 for Windows was actually delayed while a Linux server bug was
>> tracked down, which, when you consider the amount of bile spewed in
>> IW's direction over the delay in releasing 1.3, this was awfully nice
>> of them.
>>
>> The reason the machine-gun-fires-to-the-right bug isn't fixed yet is
>> because I've been out of town all week at Game Developer Conference.
>> We didn't find it in QA, so we didn't fix it. I'm tracking it down
>> right now, and will release an interim binary as soon as I figure out
>> the problem.
>>
>> Activision's official line is "we don't support Linux" because they
>> aren't really staffed to support it. The calls they get are "uh, my
>> DirectX install is broken", etc. You need to have a full time staff to
>> deal with this, and they aren't prepared to talk about glibc versions
>> and CPU usage and such. Quite frankly, for admin issues, you are
>> always going to be better off talking to other admins. That's not to
>> dodge the bullet on behalf of Activision, but really, I'd rather ask
>> and answer on a mailing list like this than sit on hold on some
>> support line. The brains that make this happen (including the original
>> developers, myself, and an army of professional server admins) are all
>> here. If I was running Activision, I would train my support staff to
>> send you here anyhow, but maybe that's just me.
>
>
> ================================================
> This e.mail is private and confidential between Multiplay (UK) Ltd. and
> the person or entity to whom it is addressed. In the event of
> misdirection, the recipient is prohibited from using, copying, printing
> or otherwise disseminating it or any information contained in it.
>
> In the event of misdirection, illegible or incomplete transmission
> please telephone (023) 8024 3137 or return the E.mail to
> postmaster at multiplay.co.uk.