Direct answer: A modern gigabit switch, static IP addresses, a Linux box running the Quake 3 and Unreal Tournament 99 dedicated servers, the OldUnreal 469 patch for UT99, and the ioquake3 client for Q3 will get you a functioning period-correct LAN party in 2026. Budget $60 to $120 per seat for peripherals if attendees bring their own PCs, more if you are also providing displays. The SteelSeries QcK Gaming Mouse Pad, the Turtle Beach Recon 50 headset, and a decent set of monitors are what survive the night.
Step 0 diagnostic: period-correct or modern-hardware-retro-software?
The single decision that determines your entire budget.
Fully period-correct means each seat is a Pentium III or early Pentium 4 with a Voodoo 3 or GeForce 2 GTS, a CRT display, and PS/2 peripherals. The hardware is available on the used market but shipping and reliability are unpredictable, and 25-year-old capacitors are actively hostile to a party budget. This path is a labor-of-love project, not a party plan.
Modern-hardware-retro-software means each seat is a modern PC or laptop running Quake 3 and UT99 via the ioquake3 and OldUnreal 469 patches. The software is period-correct; the hardware is not. This is the pragmatic choice, and the shape most 2026 revivals actually take.
This article walks through the modern-hardware path in detail and gives the honest CRT-versus-LCD argument for the host seat only. The rest of the seats run whatever their owners brought.
Editorial intro: what BYOC actually was, and what a revival gets right
Bring-your-own-computer nights peaked between 1998 and 2004 and had a specific shape. Someone rented a hall or converted a basement, everyone hauled a tower and a CRT in a car, cables snaked across the floor, a switch or hub sat in the middle of the room, and the games were whatever the group had converged on that quarter. Quake 3 Arena and Unreal Tournament 99 were the canonical choices because they had proper dedicated-server support, they had large maps built for point-to-point LAN play, and they ran on hardware that everyone actually owned.
BYOC died for two reasons. Broadband internet made online matchmaking convenient enough that the hall-rental math stopped working, and the hardware side of the equation got heavier. Games needed hulking towers with power supplies that were incompatible with a car trunk. The revival works because it inverts both problems: laptops replaced towers, the software is 25 years old and runs on anything, and the point of the evening is not the technical convenience but the room being full of people playing a game together.
Key takeaways
- 8 to 12 players is the sweet spot. More than that and the room politics get messy.
- A modern gigabit switch is enough for that count; forget about VLANs and business-grade gear.
- Cable per seat: 5 to 10 meters of Cat6 cable, depending on room layout.
- Power per seat: 200 to 400W under load (mixed laptop-and-tower crowd).
- Budget per station if you provide everything: $500 to $900 for a decent laptop-plus-monitor-plus-peripheral setup.
What you will need
The full checklist for hosting a 10-player LAN in 2026.
- A dumb gigabit switch, 16 ports minimum, unmanaged. TP-Link and Netgear both sell these in the $50 to $80 range. Skip the managed models; they add complexity you do not need.
- 10 Ethernet cables, Cat6 or Cat5e, in the 5 to 10 meter range. Buy in bulk.
- A power distribution plan. A commercial venue's outlets will handle this; a residential room will not without splitting circuits. Plan two 20-amp circuits for a 10-seat LAN.
- One display per seat if the host is providing them. The KOORUI 27" 4K QD-Mini LED Gaming Monitor is a fair pick for the host seat if you are running a demo screen or a spectator display; for the 10 player seats a cheaper 24-inch 1080p monitor per seat is the right budget call.
- One headset per seat for voice comms. The Turtle Beach Recon 50 is the honest choice: cheap, comfortable, sturdy enough to survive a night, plugs into a 3.5mm jack.
- A dedicated-server host. Any modern Linux box on the network with 8GB of RAM is more than enough to host both Quake 3 and UT99 dedicated servers simultaneously.
- Peripherals per seat (see below).
Network topology
A dumb gigabit switch beats a consumer router for this workload because the router adds NAT and DHCP overhead that you do not need. Every seat gets a static IP address; the switch just moves packets. Configure the host machine on a fixed address (10.0.0.1 by convention), configure each seat on 10.0.0.10 through 10.0.0.20, and you are done. No DHCP means no leases to expire mid-match.
The one setting that breaks LAN discovery on modern operating systems is Windows Defender Firewall's default block for local subnets. Turn on private-network sharing before the party starts, not during. This is the single most common failure mode we have seen at LAN revivals.
Do not run the switch through your consumer router. Isolate the LAN. Attendees should not have to worry about whether their local file share is exposed to the internet during the party.
Server hosting
Both games have healthy dedicated-server communities and both run reliably on a modern Linux box. The ioquake3 project provides a maintained Q3 client and server; the maps and configs from the original release still work. On the UT99 side, the OldUnreal 469 patch is the mandatory install: it fixes rendering, netcode, and compatibility on modern operating systems, and it re-enables master-server discovery which the original UT99 has lost to a decade of URL changes.
Configure the servers to prefer LAN-scope broadcasts. Both engines detect LAN games on the local subnet without needing a master server if the client and server are on the same network. This is why the flat static-IP layout is not optional; it is what makes the games find each other.
Compatibility table for 2026
| Title | Required patch | Master server (Jan 2026) | Renderer options | Known gotcha |
|---|---|---|---|---|
| Quake 3 Arena | ioquake3 | ioquake3 master, community | OpenGL only | Widescreen FOV fix required |
| Unreal Tournament 99 | OldUnreal 469 | OldUnreal master | D3D9, D3D11, OpenGL, Vulkan | Original masters dead; 469 required |
| Quake 2 | Yamagi Quake 2 fork | Yamagi master | OpenGL, Vulkan | Optional but worth it |
| Half-Life 1 (DM) | Steam client, LAN mode | Steam LAN discovery | Direct3D, OpenGL | Steam login not needed for LAN |
| StarCraft (2000 era) | Battle.net 2.0.4 patch | LAN mode | 2D only | Retail CD keys not required for LAN |
The critical row is UT99. Without the OldUnreal 469 patch, the game will not find its master server, will not render correctly on modern GPUs, and will not accept modern joystick or mouse input reliably. Every seat needs the patch installed before the party starts. Do this the day before, not the day of.
Period-correct versus practical: the CRT-versus-LCD argument
CRT enthusiasts have a real point. A 4:3 CRT at 640x480 or 800x600 is the display these games were designed for; motion clarity on a 60Hz LCD does not match a 100Hz CRT. If you have a spare CRT and a working seat for it, the host seat is the right place to put it because the demo screen benefits most from the period-authentic look.
For the other seats, the argument does not hold up. Buying CRTs for a party is expensive, they are heavy, they are unreliable after 25 years, and modern LCDs are objectively easier to move. The pragmatic layout is one CRT at the host seat if you have it, and modern displays everywhere else. For anyone who wants a modern display that still looks great with retro content, the KOORUI 27" 4K QD-Mini LED does an unusually good job with lower-resolution content because of its high pixel density; a 640x480 render on a 4K panel integer-scales cleanly.
Peripherals that survive a LAN
A LAN party is hard on peripherals. Mice slam onto tables, keyboards get spilled on, headsets get sat on. Buy for durability, not aesthetics.
- Mouse pads. The SteelSeries QcK Gaming Mouse Pad in the XXL size is the reference here. Cloth, thick, rollable, cheap. Bring one per seat.
- Headsets. The Turtle Beach Recon 50 is what we recommend when you are outfitting an entire party. It costs less than a hundred dollars per seat, it has a functional boom mic for team comms, and it does not shatter when someone drops it on a concrete floor.
- Spectator mice. For seats that will occasionally be used to browse the internet or manage server settings, the Logitech M510 Wireless Mouse is a fair sidekick. It is not a competitive pointer; it is a get-me-through-the-evening pointer.
- Controllers. The DualSense does not belong at a Quake 3 seat, but if you are also running a game that plays better with a controller as a side-event, it is the right pick. Keep it wired or on a 2.4GHz dongle; Bluetooth latency in a room full of other Bluetooth devices is a mess.
The transport and setup kit
For a host who moves the setup between venues, the ivoler Carrying Storage All in One Case is a controller-and-cable transport that fits a couple of controllers, chargers, and small peripherals. It was designed for the Nintendo Switch; it fits a decent LAN-party toolkit fine.
Ambient light in the room affects how well the party feels. A KSIPZE LED Strip Lights rig behind the projector or spectator display fills the back wall with a soft glow that reduces glare and makes the room feel intentional. Two hundred feet of LED strip is more than any single party needs; use one roll and keep the other for future events.
Bandwidth, power, and the two failure modes
Two things routinely end LAN parties early.
Bandwidth. Not internet bandwidth; the LAN itself. A gigabit switch is comfortably enough for 12 seats even if everyone is streaming HD video, but the moment someone plugs in a NAS or starts a large file transfer over the LAN it can starve the game traffic. Enforce a rule: game traffic only during matches; large file transfers over the internet gateway, not the LAN.
Power. A residential room with a single 20-amp circuit will not sustain ten gaming laptops plus displays under load. Split the circuit or move to a venue that has real electrical infrastructure. Circuit breakers popping mid-match is the memorable failure mode of every LAN party revival that under-planned.
Verdict matrix
Go fully period-correct if… the point of the evening is nostalgia for the specific 2001 hardware and everyone bringing has invested in restored hardware. This is a labor of love, not a repeatable pattern.
Go modern-hardware-retro-software if… you want a working, repeatable, socially-successful LAN party. This is the correct choice for almost every reader.
Skip the LAN and play online if… your friend group is geographically distributed enough that half of them cannot come, or if the venue logistics are more expensive than the fun the party will provide. Discord voice and any modern matchmaker will keep the friend group intact without the shared-room cost.
Bottom line
A period-correct LAN party in 2026 is genuinely fun and completely practical if you plan for the pragmatic hardware layout: modern PCs, static-IP flat network, dumb gigabit switch, OldUnreal 469 for UT99, ioquake3 for Q3, and durable peripherals per seat. The purist CRT-and-Voodoo path is a hobby project; the pragmatic path is a party plan. Budget $60 to $120 per seat for peripherals if attendees bring their own PCs, and put your money on the switch, the headset, and the mouse pad. Everything else is either negotiable or optional.
Related guides
- GameSir G7 SE vs DualSense: Which Controller Is Better on PC in 2026?
- Build a Wall-Mounted Raspberry Pi 4 Arcade Cabinet
- Ryzen 7 5800X vs 5700X for a Dual-Duty Gaming and Local-LLM Build
- Best SSD for a Local LLM Model Library in 2026
Citations and sources
- OldUnreal 469 patch project — the mandatory UT99 modernization pack that fixes rendering, netcode, and master-server discovery, accessed July 2026.
- ioquake3 project — the maintained Quake 3 Arena client and server used throughout the article, accessed July 2026.
- Tom's Hardware coverage of retro-gaming hardware — corroboration of the peripheral pick reasoning cited, accessed July 2026.
_This is an editorial synthesis of published community documentation and product specifications. Verify current patch availability and per-title compatibility notes with the source projects before planning your event._
