The LAN Party Era — CRT Monitors, CAT5 Crimping, and the Golden Age of Counter-Strike 1.6

You could smell a LAN party before you opened the door. Hot plastic from eight CRT monitors running for twelve hours straight. Dominos grease. Energy drinks. The specific humid-electronics smell of a room full of tower PCs pulling more amperage than the circuit was happy with. Nobody talked about the smell because nobody noticed.

For about seven years — roughly 1999 to 2005 — multiplayer gaming meant physically transporting a computer to a friend's house. You packed your tower in the back seat, balanced the CRT on the passenger side, wrapped your keyboard and mouse in the Mountain Dew t-shirt you got free from a case of Mountain Dew, and drove to someone's basement to play Counter-Strike until the sun came up.

Then broadband got cheap, matchmaking got good, and the whole thing disappeared. This is a walk through what it actually was like.

The Hardware You Hauled

Everything weighed more than it should have. A typical LAN rig was:

• Mid-tower PC (~35 pounds), usually beige, usually with a side-panel window because the year was the early 2000s and we had just discovered you could put things in a computer case
• CRT monitor, 17" or 19", 45–70 pounds, physically deeper than the desk
• Keyboard, mouse, mousepad, usually wired, plus a spare ball mouse because optical mice were still new
• Surge protector, because the host only had two free outlets and there were going to be eleven of you
• Ethernet cable, 25 feet, coiled around your forearm, RJ45 ends taped against damage
• Headphones — the real pros had them, everyone else got yelled at for having speakers

Average load-in time for a 10-person party: 90 minutes. Average setup-to-first-frag: another 30. Nobody complained. That was the activity.

The CRT Was Not A Flaw

CRT monitors feel absurd in retrospect — they weighed as much as a microwave and rendered the screen with an electron gun that might also give you a headache. But for competitive gaming in 1999, they were actively better than the alternative.

LCDs of the era ran at 60Hz with input lag measured in double-digit milliseconds. Response times were so bad that fast motion smeared. A decent CRT at the time did 85Hz or 100Hz with essentially zero input lag and perfect motion handling. Serious Counter-Strike players refused to touch LCDs until the mid-2000s. The weight was a feature: it meant the monitor was real.

You transported it in its original box if you still had it, or in a milk crate lined with a towel if you didn't. You left the power cord plugged in. You didn't take the stand off. Everyone had a cracked corner from that one time they didn't clear the doorway.

The Network Was The Event

The reason a LAN party felt like a project more than a party was the network. Someone — usually the most-patient person — spent the first hour crimping Ethernet cables on the living-room floor while everyone else watched.

A CAT5 cable has eight wires in four twisted pairs. You stripped the outer jacket with a cable stripper. You untwisted the pairs and sorted them in T568B order from left to right: orange-white, orange, green-white, blue, blue-white, green, brown-white, brown. You trimmed them flush. You pushed them into the RJ45 connector straight and all the way to the front, cable jacket inside the connector housing. You squeezed the crimp tool until you heard the plastic punch down the pins.

A good crimp lasted years. A bad crimp caused intermittent packet loss at 3 AM that the host blamed on their ISP and the guest blamed on their netcode. Nobody blamed the crimp.

Hub vs switch

A hub broadcast every packet to every port. Eight people playing Counter-Strike through a hub got eight copies of every packet. Collisions were constant. Ping was terrible. Hubs were the budget option and the reason people hated ISDN.

A switch learned which MAC address was on which port and only sent packets where they belonged. By 2002 a five-port 100Mbit switch was thirty dollars and LAN parties suddenly worked. The person who brought the switch was always the host's best friend.

What Everyone Actually Played

Counter-Strike 1.6 was the center of gravity. Every LAN party had a CS server running from the moment the network came up until someone passed out. The maps were de_dust, de_dust2, cs_assault, de_aztec, and fy_iceworld if you wanted to fight. Your Desert Eagle aim was either good or mocked. There was no middle ground.

Around the edges:

• StarCraft: Brood War and Warcraft III for the RTS portion of the evening. APM became a vocabulary word. Somebody always started a 3v3 at 2 AM that turned into a grudge.
• Diablo II for the PvE crew. Baal runs, MF builds, hoarding Stones of Jordan.
• Unreal Tournament and Quake III Arena for people who wanted arena-style fast shooters and had reflexes.
• Age of Empires II and Command & Conquer: Generals for the folks who wanted to win by resource management rather than aim.
• Battlefield 1942, Battlefield 2 later, when the party had enough people to fill a map and a good enough host PC to run a 32-player server.

The unifying feature: LAN mode. Every multiplayer game of the era had a mode that bypassed internet servers entirely. You picked "LAN game," someone hit "host," everyone else saw the server appear in a list, and you joined. No accounts. No matchmaking. No patches. If the game disc was scratched you borrowed someone's.

The Logistics Were The Culture

The social dynamics of a LAN party were specific and won't come back.

Everyone saw each other's face. Not via webcam. In the same room. You heard the person frag you scream when you fragged them back. The table-slap when someone hit a 1v4 clutch. The particular pause when someone's PC crashed mid-round and they were debugging it out loud while their teammates covered for them. There was no muting anyone.

Food was a shared infrastructure problem. Pizza was the default because pizza scaled. Mountain Dew (for caffeine) and Gatorade (for hydration, as a cover for not drinking water). Bagel Bites. Pizza Rolls. The snacks were whatever survived being handled by eight people with keyboard hands.

Sleep was optional and politically fraught. Someone always went to sleep at 3 AM on the couch. The question was whether you played through it or quieted down out of respect. The answer was usually "play through it but move to the basement."

The host was responsible for everything. Power. Network. Temperature. Arbitrating cheating disputes. Supplying toilet paper. Most hosts burned out after three or four LAN parties and retired. A new host emerged. The gatherings continued.

Why It Died

Three causes, all economic, all boring.

Broadband got cheap. In 2001 a cable connection was $50/month, a luxury, and uploading anything was slow. By 2005 it was everywhere, fast enough both ways, and playing online from home no longer felt like a compromise. If the game was as good remote as in-person, nobody was going to haul a CRT.

Matchmaking arrived. Steam launched Counter-Strike: Source in 2004 with a server browser and later matchmaking. Xbox Live had been building the social graph on the console side since 2002. By 2007 "I'll meet you online at 8" was easier and lower-friction than "I'll meet you at Dave's at 8." The competitive scene moved to online tournaments, the casual scene to voice chat with friends.

Laptops killed the tower. Gaming laptops in 2008 were finally capable enough that bringing a full tower became eccentric. Once you didn't have a CRT in the back seat, you didn't have the ritual. The ritual was the party.

What Remained

The skills, mostly. A surprising number of people who run production Kubernetes clusters today learned networking by debugging packet loss on a basement hub in 2002. Anyone who works in esports or competitive gaming can trace a straight line back to the CS clan that played every Friday in someone's garage. The muscle memory of CAT5 crimping does not leave you.

What didn't survive was the logistics. The deliberate act of moving your computer somewhere. The specific friendship that forms when you and six friends collectively solve the problem of fitting eight PCs through one doorway at the same time. Discord voice chat is fine. It isn't the same.