07-19-2009, 04:43 PM | #41 (permalink) | |
Tilted
Location: Canada
|
Quote:
But I do think you missed mine. I'll use a example. Team Fortress 2 has both LAN and WAN on both the listen server and dedicated server. I made a mistake some months back and forgot to edit my dedicated server's config file before a battle to make it a lan only server. It ran just fine as long as there was only 5 or 6 of us on the server, as soon as it got to around 9 or more it became unplayable, we started getting lag spikes and players got booted with the dreaded error validating steam ticket. That error told me what was going on, changed it from LAN 0 to LAN 1. About 17 of us joined an played smooth as silk after the server did a map change. I don't know if SC2's servers will act the same as the TF2 servers though. Never Winters Nights has something along that problem also, I'm not really sure what the problem is or the solution as I'm not the one that runs the server for that but I do know that as long it's it's set to LAN only runs fines, forget to set that one variable and it starts chugging fast. I guess it just might also come down to just how big your private LAN parties tend to be |
|
07-22-2009, 12:12 PM | #42 (permalink) | |
The sky calls to us ...
Super Moderator
Location: CT
|
Quote:
Is this really a problem anymore? |
|
07-22-2009, 01:06 PM | #43 (permalink) |
Junkie
|
In college we often had college lan parties. We would reserve a large conference area, everyone would bring their computers, and we would network them. There was never internet on this network and even if there was it would not have handled the 50+ people at the party. This is where having a lan option is good. I don't see why they would require battle.net
|
Tags |
lan, sc2 |
|
|