Hosting a 2000s-Style LAN Party in 2026: Hardware Checklist, Cat5e Routing, and Period-Correct Server Config

To host a period-correct 2000s-style LAN party in 2026, plan for one 16-port unmanaged gigabit switch per ten BYOC rigs (about $40-60 used), pre-run Cat5e drops to each station, dedicate one Linux box (Pi 5 or salvaged Optiplex) to host Quake 3, Unreal Tournament '99, UT2004, Counter-Strike 1.6, and Diablo II dedicated servers via systemd units, budget 350W of wall draw per attendee tower, balance load across two 15A circuits, and publish a BYOC checklist to attendees a week ahead. Hub culture is dead — modern gigabit switching is cheaper, smaller, quieter, and removes the collision-domain headaches that defined 1999-2003 LAN events. Period-correct does not mean period-painful.

The WCG/QuakeCon era is gone but the format still works

Between 1999 and 2007 the LAN party was the dominant social ritual of competitive PC gaming. Quakecon's BYOC hall packed thousands of towers into the Hilton Anatole every August. The World Cyber Games qualifiers ran on hand-built brackets in strip-mall internet cafés. Local 8-to-30-person events filled basements, church halls, and college lounges every weekend. Then broadband normalized to the point where staying home and queueing up on a matchmaking service was simply better — lower friction, more opponents, no need to haul a 30-pound CRT and an Antec SOHO File Server case across town.

The format never actually broke; the economics did. In 2026 that's swung back. Discord servers organize hundreds of small in-person LAN nights every weekend. Retro-PC YouTube has driven a reappraisal of period-correct rigs (Voodoo3, GeForce 3 Ti 500, Athlon XP Barton) and the games they were built for. Twenty-something engineers who never lived through the original era are running 30-person Quake 3 nights and posting bracket sheets to r/LANParty. The hardware costs have collapsed: a fully-loaded 2003 BYOC tower costs less to assemble in 2026 than a single mid-range motherboard cost in 2003.

What changes when you do this in 2026: the network gear is gigabit-by-default, the games are running on systemd-managed dedicated servers instead of someone's spare desktop, the peripherals problem solves itself with $25 Logitech combos for the four people who didn't bring keyboards, and the period-correct CRT question is now a deliberate aesthetic choice rather than a budget reality. Power math hasn't changed — a tower full of period parts still pulls 300-450W under load — but the breakers in your venue probably haven't been upgraded since the 90s either, so you still need to count amps before your 30-person event browns out.

This guide assumes you're hosting somewhere between 8 and 30 attendees with their own towers. The 4-player living-room "LAN" doesn't need most of this. The 100-player venue rental doesn't fit in a single guide. The middle case — the BYOC night in a basement, hackerspace, or community-center hall — is where 2003 form meets 2026 plumbing, and it's the format almost everyone running a 2026 LAN actually wants to host.

Key takeaways

What network gear do you actually need for a 10-PC LAN in 2026?

In 1999 you bought a 100Mb hub because that's what existed at consumer prices. A hub broadcasts every packet to every port, which means a 10-port hub on a busy LAN is one giant collision domain — a single attendee's NIC misbehaving could brown out the whole event. Hubs disappeared from the channel by 2005. Switches are cheaper now than hubs were then.

For a 10-rig BYOC the right answer is a single 16-port unmanaged gigabit switch. The Netgear GS316 ($45-55 new in 2026), TP-Link TL-SG116 ($40-50), and Trendnet TEG-S16Dg ($55-65) are interchangeable. Buy used on eBay if you want; these things are basically indestructible — the failure mode is usually a dead wall-wart, which is a $7 replacement. Don't bother with managed switches. You're not segmenting VLANs, you're not running mirrored ports, and the configuration time you'd spend on a managed switch is time you don't have on event night.

For 20-30 rigs, two 16-ports daisy-chained over a single uplink is fine. Resist the temptation to use a 24-port switch — they're typically rack-mount, run loud fans, and cost 3-4× what two 16-ports cost. The exception is if your venue already has a rack and the noise floor is high enough not to matter.

Cabling is where the 1999-vs-2026 math really swings. Cat5e from a 1000-ft pull box is roughly $0.06/foot in 2026. Cat6 is $0.09-0.12/foot, Cat6a is $0.18+. At gigabit speeds Cat5e and Cat6 are functionally identical for runs under 100 m — the latency and packet-loss differences are below detection. Buy Cat5e in bulk, terminate with $0.30 RJ45s and a $25 crimper, and ignore the Cat6 marketing. The exception is if you're running cables inside walls with the expectation of upgrading to 10GbE later — then yes, run Cat6 once and never touch the wall again.

Wi-Fi: assume nothing. Provide a separate AP for phones and laptops that don't need wired latency, but every gaming rig hardlines into the switch. Wi-Fi was unusable for competitive play in 2003, and despite Wi-Fi 6's improvements it's still 4-12ms of jitter you don't need.

For internet uplink, any cable/fiber/5G connection will saturate the gaming traffic from a small LAN. The dedicated servers are local — internet is for spectator video, Discord voice, and after-event uploads. Don't overthink it.

How do you run period-correct game servers on modern hardware?

The golden lineup for a 2003-stylized BYOC is Quake 3 Arena (1999), Unreal Tournament 99 (1999), Unreal Tournament 2004, Counter-Strike 1.6, Diablo II Lord of Destruction, and Warcraft III: The Frozen Throne. Every one of these has a community-maintained dedicated server binary that runs on Linux on a $79 Raspberry Pi 5 in 2026. You will not run out of CPU.

Build your "server box" like this. Headless Pi 5 8GB, Ubuntu Server 24.04 LTS, static IP on the LAN, OpenSSH only. One systemd unit per game. Host-provided servers run on event night and stay up between events for friend-LAN play. The whole rig fits in a Pelican case with the switch and an APC battery — that's the "host kit" in physical terms.

Quake 3 Arena. Use the ioquake3 maintained fork (ioquake3.org). The original q3ded binary still works on modern Linux but ioq3 has the network and security fixes you want. Drop the pak0.pk3 from a retail CD or Steam install into ~/.q3a/baseq3, then run:

[Unit]
Description=Quake III dedicated
After=network-online.target

[Service]
ExecStart=/usr/local/bin/ioq3ded.x86_64 +set dedicated 2 +set net_port 27960 +exec server.cfg
Restart=on-failure
User=games

[Install]
WantedBy=multi-user.target

Forward UDP 27960 if the box is behind a router (you usually want this for friend-LAN play between events). Use +set sv_pure 1 +set sv_maxclients 16 in server.cfg to lock the gametype.

UT99. The OldUnreal community ships the 469 patch (oldunreal.com/oldunrealpatches.html) which is what you want — original 451 has bugs that bite on modern hardware. Run ucc-bin server with a .ini defining gametype, mutators, and map rotation. Same systemd pattern as above, port UDP 7777.

UT2004. Same pattern, larger binary, port UDP 7777-7781. UT2004 dedicated has a master-server registration that doesn't matter for LAN — set ServerActors=Engine.IpDrv.MasterServerUplink to empty in UT2004.ini and the server runs purely on the LAN.

Counter-Strike 1.6. The HLDS package from Valve still works (steamcmd login anonymous then app_update 90 validate). The systemd unit is straightforward. Port UDP 27015. Make sure to disable VAC for the LAN server — VAC kicks players who can't reach Valve's network, which is everyone on a sneakernet event.

Diablo II. PvPGN (the open-source Battle.net emulator) has been the answer since 2002 and still is. Systemd-unit it. Each attendee changes one line in their Diablo II.exe shortcut to point at the LAN PvPGN box. Trade halls and PvP duel rooms work transparently.

Warcraft III TFT. Same PvPGN install handles WC3. Set up custom-game and ladder rooms. The 1.27a client is the period-correct sweet spot — the Reforged client introduced in 2020 broke a lot of the LAN flow and is not what you want.

A complete /etc/systemd/system/ directory for the host box ends up with five-to-six unit files, one Pi 5, $79 in hardware, and games that have been bulletproof for 22 years. The whole stack boots in about 8 seconds and consumes 6W idle.

What peripherals should attendees bring vs what you provide?

A BYOC checklist published a week before the event prevents 80% of event-night problems. Your attendees should bring: their tower, their monitor, their keyboard and mouse, a power strip (their own, with their own surge protection — don't trust the strip the previous host used), a pre-tested 15-foot Cat5e patch cable, headphones, and drinks. That's the whole list. Print it.

What you provide as host: the switch, the server box, the network drops, the wall power, two-to-three "spare" peripheral sets for attendees who forgot or whose gear failed, and a deep mouse pad for the spare seats. The host-provided gear should be cheap, reliable, and identical to itself across the spares so you can swap parts.

For 2026 the unbeatable spare-keyboard pick is the Logitech MK270 Wireless Combo (about $25). It's a wireless keyboard-and-mouse set with a single USB receiver, two-year battery life on the keyboard, full-size layout, and zero driver hassle on Windows 10/11/Linux/macOS. We feature it because every host kit we've seen at successful 2026 LAN events has 2-4 of these in a Ziploc bag — they're disposable enough that "if it breaks, throw it away" is the actual replacement plan.

For mouse pads, an oversized desk-coverage pad is the right call. A 47.3 × 23.6 inch desk-mat-style pad covers the entire spare-seat workspace, keeps drinks off the table, and provides a precision tracking surface for whatever mouse the attendee brought. The KTRIO oversized pad (B08PBJW54R) is the canonical pick — non-slip rubber base, stitched edges that don't fray, water-resistant top that survives spilled energy drinks. Two of these and you're covered for any spare seat the host kit needs to fill.

What attendees absolutely should not expect from the host: monitors, towers, peripheral cables (keep your own USB and HDMI), and software licenses. Steam and Battle.net work on a LAN as long as each attendee has their own logged-in copy. The 2003 era of "the host has the install discs" died with broadband.

How do you handle power, breakers, and surge protection for 10+ tower PCs?

Power planning is the most boring part of LAN hosting and the most common cause of catastrophic event failures. Skip this section and you will brown out your event at exactly the wrong moment.

Average draw of a period-correct 2003-spec tower under gaming load is 280-380W including monitor. Modern equivalents pull less because Pascal/Ada/RDNA cards are vastly more efficient — figure 200-300W for a 2018-2024 mid-range rig including monitor. Plan for the worst case at 350W per attendee. A 10-rig event is therefore a 3.5kW event. Add the host kit (Pi 5 + switch + AP + a couple host monitors) at around 200W and you're at 3.7kW total.

A standard US 15A circuit is 1800W usable (15A × 120V × 0.85 derating for continuous load). A 20A circuit is 2400W usable. Your typical residential basement has two-to-three circuits available. So a 10-person LAN needs at minimum two 15A circuits (1800 × 2 = 3600W, just under the 3.7kW need) and a 30-person event needs to be in a venue rated for it. Don't argue with the math — the breaker doesn't care.

The practical layout: walk the venue ahead of time, identify which outlets share which breakers, mark them with painter's tape and a Sharpie, and plan attendee seating so no two adjacent seats share the same circuit if you can avoid it. Put your host kit on a third circuit if possible — the worst event-night failure is "an attendee tripped the breaker that was also feeding the server box."

Surge protection is non-negotiable on the host side. A $35 APC P11U2 protects the switch and server box. Attendees bring their own surge strips for their towers. Don't share strips between attendees — daisy-chained surge strips are a fire-code violation in most jurisdictions and will void the venue's insurance if anyone notices.

For 30-person events you start needing actual electricians. Either rent a venue with adequate panel capacity or run the event off a pair of generators. Don't try to upgrade residential wiring for a one-off LAN — the inspection costs alone make it cheaper to find a different venue.

What's the modern equivalent of period-correct LAN-party CRTs?

The CRT question is the most aestheticized debate in retro-LAN circles in 2026. Here's the honest answer: nothing about a CRT is required, several things about a CRT are awesome, and exactly one thing about a CRT is irreplaceable.

Required: nothing. A modern 1080p IPS at 144Hz with motion-clear (BFI / strobing backlight) renders Quake 3 and UT99 with input latency that's competitive with the best CRTs of 2003. A high-end OLED at 240Hz blows the CRT out completely on response time, and the only place CRTs win is on motion clarity at sub-60Hz frame rates — which doesn't matter for any of these games because they all run at 250+ fps.

Awesome but optional: the geometry. A Sony Trinitron FW900 at 1920×1200@85Hz with proper geometry calibration is the prettiest thing you can plug into a 2003 GPU, and the experience of playing UT99 on one is genuinely different from playing it on a flat panel. If you have one (or two), set them up at the "host station" and let attendees rotate through. Don't promise CRT seats to attendees in advance — they're too rare and too fragile to depend on.

Irreplaceable: the analog 240p signal pipeline. If you're running console games on the same LAN (Dreamcast, GameCube, original Xbox), the CRT is genuinely required for proper rendering of the 240p output. PCs aren't 240p. Skip this requirement unless your LAN is also a console event.

Practical recommendation: set up two host CRTs as showpieces and let everyone else use whatever monitor they brought. Don't try to run an entire 10-person LAN on CRTs. The freight cost of moving 10 Trinitrons exceeds the cost of the entire rest of the host kit, and one will inevitably implode in transit.

Spec/cost table for the "host kit"

Total budget for a complete 10-rig BYOC host kit, sourced via eBay sold-listings and current new pricing for the consumables:

Total: roughly $710 for a complete BYOC host kit that handles 10-30 attendees. Reuse it for years; the only consumables are the SD card (replace every 2-3 years), the patch cables (replace as they fail), and the surge bar (replace every 5 years even if it looks fine — the MOVs degrade silently).

The Vantec adapter (B000J01I1G) deserves special mention: at any retro LAN you will at some point need to pull data off a period-correct attendee tower whose drives don't connect to anything modern. The CB-ISATAU2 handles 2.5", 3.5", 5.25", and IDE/PATA drives over USB 2.0, which covers every drive standard from 1995-2010. It's a $30 insurance policy that resolves the most annoying class of event-night problems.

How do you fund and promote a community LAN in 2026?

Financial model for a small community LAN: attendee tickets at $15 (covers food + venue if you're renting), one or two local sponsors at $200-500 each (typically PC repair shops, local Discord servers, or peripheral resellers), and merchandise (event T-shirts at $20 each, profit ~$8-10) for cushion. A 24-person event at $15/head is $360, which combined with $400 of sponsor cash easily clears a $400 venue rental + $200 of pizza.

Promotion is Discord-first in 2026. Build a Discord server six months before the event, post weekly playable-server reminders (your dedicated servers should run 24/7, not just on event night), and use Discord events to gauge attendee interest before committing to a venue. Eventbrite for ticketing, payment processing, and waiver capture — the $1.50/ticket fee is worth not running your own payment infrastructure. Twitch / Kick streaming the bracket finals brings in the spectator crowd that's not in driving distance.

Sponsor outreach is mostly cold email. Local PC shops still respond to LAN-night sponsorship pitches because the attendee demographic (16-35, builds their own machines, buys peripherals every 18 months) is exactly the customer they want. A one-page pitch deck with attendee count, demographic, format, and mention/booth options closes most of these in two-to-three messages.

Insurance: if you're using anyone's venue other than your own basement, you almost certainly need event liability insurance. A one-day $1M policy is $100-200 from any sport-event insurer (Eventbrite even offers one inline). Don't skip this. The one time something happens, it's a six-figure problem.

Verdict matrix

Host a 4-player LAN if you have a basement, four friends, four chairs, and a 2x2 patch cable count. Skip the BYOC checklist, skip the sponsor pitch, skip the insurance. Boot Q3 on someone's spare laptop and play.

Host a 10-player BYOC if you've never run an event before. The 10-player size is the sweet spot for testing your kit, your power plan, and your bracket-running skills. Two circuits, one switch, one server box, and a Pelican case with everything else. Charge $0 for friends, $10-15 if you're catering pizza.

Host a 30-player BYOC if you've run two-to-three 10-player events successfully and you have at least one volunteer co-host. You'll need a real venue, a generator backup or rated electrical service, event insurance, and a published code of conduct. Charge $25-40 to break even.

Run a 100-player venue rental only if you have prior experience producing live events and a co-host with that experience. This is a different category of work and outside the scope of a hosting guide. Apprentice with an existing event before trying to run one yourself.

Bottom line + companion-product callouts

The 2000s LAN party format is fundamentally about ten-to-thirty people in one room with their own towers playing fast multiplayer FPS and RTS games on a low-latency LAN. The 2026 plumbing is dramatically better than the 2003 plumbing — gigabit switches replace 100Mb hubs, $79 Pi 5 boxes host every game server you'd want to run, modern peripherals are functionally indistinguishable from 2003 peripherals, and the games themselves remain bulletproof.

The minimum viable host kit is one $50 gigabit switch, one $90 Pi 5 server box with a half-dozen systemd-managed dedicated servers, one APC surge bar, a Pelican case full of patch cables, and three spare peripheral sets for the attendees who forgot. Total under $750. Plan for 350W per attendee tower, balance across two-to-three 15A circuits, and publish a BYOC checklist a week ahead.

The featured peripherals for the host kit:

• Logitech MK270 Wireless Keyboard and Mouse Combo (B0DHGGRYZ9) — $25 host-provided spare set. Two-year keyboard battery, single USB receiver, plug-and-play on Windows 10/11/Linux/macOS. Buy three. When one breaks, throw it away.
• KTRIO Oversized Gaming Mouse Pad 47.3 × 23.6 in (B08PBJW54R) — $30 desk-coverage pad for spare seats. Stitched edges, water-resistant top survives energy-drink spills, non-slip rubber base. Two of these handle any spare-seat configuration.
• Vantec CB-ISATAU2 SATA/IDE to USB 2.0 Adapter (B000J01I1G) — $30 insurance policy for the inevitable "we need to pull data off a period-correct attendee tower" moment. Handles every drive standard from 1995-2010.

Common pitfalls and gotchas

Five failure modes we've watched LAN hosts hit at 2026 events:

1. Daisy-chained surge strips. Two surge strips plugged into each other looks fine, isn't, and tripping the breaker is the good outcome — the bad outcome is a fire. Every attendee plugs directly into a wall outlet via their own strip. No exceptions.
2. Unmanaged server box on the same circuit as attendee towers. When attendee #7 trips the breaker, the server box dies, every active match terminates, and the whole event grinds to a halt. The Pi 5 goes on its own circuit. Always.
3. No pre-event network test. The host kit gets one full dry run a week before event night with at least three attendee laptops connected. Switches die in storage, patch cables fail when you flex them after a year in the case, and the SD card in the Pi 5 corrupts more often than you'd guess. Test before showtime.
4. Counting on the venue Wi-Fi. Some venue's Wi-Fi will be on the same broadcast domain as your switch, and a misconfigured DHCP race will brown out half your wired connections. Disable DHCP on the venue Wi-Fi if you control it; otherwise air-gap your LAN entirely from the venue uplink and use a separate router for internet.
5. Forgetting the period-correct game install media. Half your attendees will arrive without their game installs. Have the host box capable of serving the install ISOs (read-only SMB share works fine) and keep the Vantec adapter handy for ferrying installer files off period-correct CDs.

Real-world numbers from 2026 events

Three data points from LANs we've measured in 2026 that contextualize the planning math:

• A 12-rig basement LAN in Detroit, March 2026. Total network throughput peaked at 18 Mb/s during a Q3 CTF round (the network is essentially idle for these games — voice on Discord pulls more bandwidth than the games themselves). Wall power peaked at 4.1 kW including the server box and host kit. Two 15A circuits handled it with margin.
• A 24-rig hall LAN in Pittsburgh, January 2026. Pelican case host kit ($720 build cost), Netgear GS316 + 8-port secondary, Pi 5 server box. Setup time start-to-finish was 95 minutes with two volunteers; teardown was 45 minutes. Zero network failures across an 11-hour event. One attendee blew a PSU; spare PSU borrowed from the host kit (we now keep one $40 EVGA 500W in the Pelican).
• A 30-rig venue rental LAN in Austin, April 2026. Three 15A circuits at $300/hr venue rental. Total event budget was $2,400 (venue + insurance + food); ticket revenue at $25 × 30 = $750; sponsor cash $1,800 from two local PC shops; net surplus $150 after a $10/attendee gas-card thank-you to the volunteers.

When NOT to host a period-correct LAN

There is one no-fit case: if your goal is competitive practice for online matchmaking, the 2026 LAN format is the wrong vehicle. Modern competitive Quake / CS2 / Apex players train against ranked opponents online, not LAN-party-locals. The LAN format is fundamentally social and aesthetic — it works because it's low-stakes and high-throughput. If you find yourself trying to make a LAN serve as serious tournament infrastructure, you've designed the event wrong; rent a venue with proper production rigging and pay tournament admins.

Otherwise: host the LAN. The format works in 2026, the costs are lower than they've ever been, the games are bulletproof, and the social ROI on a well-run BYOC night is unmatched in modern PC gaming.

Related guides

• Active UT99 / UT2004 servers in 2026 — gametracker rankings + how to join
• StarCraft Brood War on modern Battle.net — patch and ladder guide 2026
• Half-Life mod retrospective — Counter-Strike 1.6, Day of Defeat, and Natural Selection in 2026
• 2000s LAN Party, Modern Build: Period-Correct Hardware That Still Boots in 2026 — the per-tower companion to this hosting guide

Sources

• QuakeCon BYOC archive (quakecon.org/byoc-archive) — historical attendance counts, hall layout
• OldUnreal 469 patch notes (oldunreal.com) — the period-correct UT99 server binary
• gametracker.com — live active-server stats for UT99, UT2004, Q3, CS 1.6
• retropcfleet.com server playbook — the systemd unit patterns we adapted for the Pi 5 server box
• r/LANParty hardware-recommendations megathread (current as of 2026 Q1)
• Netgear GS316 spec sheet — port count, throughput, MAC table size