Originally posted by Zoso
I'm starting to get the feeling that MP problem is worse then just a quick fix. How do people keep their jobs with this kind of support? I just can't imagine something like this getting by without some heads rolling. Not only that I would have made sure the fix was out ASAP no longer then 48 hours or some more heads would have been rolling. This is just bad business but it seems the norm in the software industry.
Well, unless someone is REALLY incompetent, it's usually a better solution to keep them around. I mean, firing the person who wrote the code usually isn't the fastest way to fix it..
What they should have done was to get someone who really knows multiplayer to sit in on the technical design, because just judging by the performance and behavior there have been some pretty basic design flaws. Problem is, what's done is done - Right now I don't envy Johan, who's obviously having trouble isolating these bugs. Multiplayer code is inherently difficult to debug, which is why you're generally better off making sure you do it right in the first place. Worst thing you can do right now is rush him. Let him figure it out and fix it.
Waffen
(who's first industry job was spending 3 months debugging someone else's screwed up multiplayer code..)
