Ricky_Honejasi wrote:Yeah indeed. Also it is annoying when the lag is determined on the b.net servers' load as opposed to the players' connections for the game itself (especially seen in early Patch 13).
If Blizzard manage to have decent connections in general for b.net 2.0, SC2 might end up lagging horribly 5-10 years later when all the expansions are out and that Blizzard will have little gain off SC2 (thus less expenses on SC2 servers, lag raises a lot) vs a future WC4 or SC3.
Of course, it's all presuming that I am not mistaken about b.net 2.0 directly hosting games.
The pathing model for sc2 won't be that much more intense on netcode than wc3, especially since physics are client-side (which is what can really kill netcode performance like it did in Halo).
They just forgot to program. Or they fired all the guys who did, either one.
Anyways, there's two teams on sc2 and both of them fucked up big time. Just as long as the editor guys listen to me tapping on their shoulder incessantly I won't really care if the rest of the world burns.