Saved
Systems · Tech history

Multiplayer video game

Multiplayer video games are not about playing together—they’re about negotiating presence across broken pipes.

Worth your time?4.5/5Yes.Study the whole thing.What works, what does not, who it is for ↓
9:58in productionCh. 1 · What it is/ 9:58 · ceiling 15 min
4 chapters · 9:58Ceiling 15:00

The brief is written and checked. The video joins this page when it is cut.4 chapters · 1 min read · 9:58 planned

Read the brief

A multiplayer video game is a coordination system—not a genre, not a platform, not an experience. It forces explicit decisions about timing, authority, visibility, and failure mode. Its history is one of repeated adaptation to infrastructure limits, not creative evolution.

Chapters & takeaways4
  1. 1:08
    What it is

    Simultaneous play requires either shared hardware or networked coordination—not both.

  2. 3:04
    Where it came from

    LANs and the Internet did not invent multiplayer—they scaled what began on a single PDP-1 in 1962.

  3. 4:13
    What it adds

    Social communication is not a feature—it’s the structural consequence of letting players see each other’s inputs.

  4. 5:54
    What it demands

    Cooperation and competition only hold when timing, visibility, and authority are explicitly designed—not assumed.

1 more chapterFewer chapters
Worth your time?

Yes. Study the whole thing.

4.5/ 5
What works
  • enables simultaneous participation across local, LAN, and WAN
  • supports competitive, cooperative, and supervisory interaction modes
  • introduces social communication absent in single-player games
  • relies on verifiable technical enablers (modems, AppleTalk, Ethernet)
What does not
  • guarantee fairness
  • tolerate latency
  • provide persistent identity
  • include moderation
Study it if
  • networked interaction designers
  • real-time systems engineers
  • social software architects
Skip it if
  • product managers seeking plug-and-play engagement
  • developers assuming zero-latency assumptions
Who should study it, and who should skipHide who it is for
The written brief1 min read

What it is and the problem it solves

A system enabling simultaneous participation by more than one person in the same game environment. It solves the problem of shared agency across distance or device boundaries.

How it works

It synchronises game state across multiple devices using shared memory, serial lines, AppleTalk, MIDI, modems, or IP networks. It supports local play (couch co-op, split-screen, hot-seat), LAN play, or WAN play—most commonly over the Internet.

What works

Social communication emerges reliably where players interact in real time. Competitive, cooperative, and supervisory modes all function as described—provided network conditions and input latency permit.

What does not

It does not guarantee fairness, latency tolerance, or persistent identity. It offers no built-in moderation, data portability, or cross-platform continuity.

What it changes

It replaces solitary execution with distributed consensus. It turns game logic into a coordination problem—and player behaviour into observable social data.

Is it worth your time

Yes—if your work involves networked interaction design, real-time systems, or social software architecture. It is a foundational pattern, not a tool to adopt.

Same field · Systems4 of 192
9:09
IEEE 802.11IEEEIEEE 802.11 is the foundational WLAN standard family. It defines MAC and PHY protocols for wireless local area networking. It uses CSMA/CA for channel access. It supports multiple bands and modulation schemes. It enables interoperability with Ethernet and IP. It was first released in 1997. Amendments extend functionality without replacing the base.
10:24
IPv61996IPv6 delivers on its core architectural promises: vast address space, simplified forwarding, standardised subnets, and host-managed fragmentation. But it does not deliver automatic deployment, backward compatibility, or operational simplicity. Its value is real—but only where the cost of maintaining IPv4 workarounds exceeds the cost of adopting IPv6’s stricter host responsibilities.
9:53
Router (computing)The router is not a singular invention but a functional consolidation of earlier interface computers — the NPL node (1969) and ARPANET IMPs (1969) — refined into an IP-forwarding device by Ginny Travers at BBN in 1975–1976. Its mechanism is simple: consult a routing table, match a destination IP, forward the packet. It works reliably for that task. It does not secure, inspect, or adapt beyond its table. Its value lies in interoperability, not intelligence. It changed networking by making heterogeneity operational — not inevitable, not elegant, but functional.
10:04
Cloud gamingCloud gaming is a remote execution system that streams video and audio while relaying inputs. It depends entirely on network quality — not hardware — and fails where latency exceeds ~50ms. It was first demonstrated by G-cluster at E3 2000 and released around 2003.
Up next in Technology

Optical storage

· 9:51

Optical storage isn’t about speed or convenience — it’s about fixing data in place so it survives power loss, magnets, and time.

9:51