Why multiplayer requires networking in Unity - Visual Breakdown

Concept Flow - Why multiplayer requires networking

Player 1 Input

↓

Send Data Over Network

↓

Receive Data on Player 2

↓

Update Player 2 Game State

↓

Player 2 Sees Player 1 Actions

Players send their actions through a network so others can receive and update their game state, enabling shared gameplay.

Execution Sample

Unity

void Update() {
  if (Input.GetKeyDown(KeyCode.Space)) {
    SendJumpToNetwork();
  }
  ReceiveNetworkData();
  UpdateOtherPlayers();
}

This code sends a jump action over the network and updates other players' states each frame.

Execution Table

Step	Action	Condition	Network Data Sent	Network Data Received	Game State Updated
1	Player 1 presses Space	Input.GetKeyDown is True	Jump action sent	None yet	No
2	Network sends data	N/A	Jump action in transit	None yet	No
3	Player 2 receives data	Data arrived	N/A	Jump action received	Yes, Player 1 jump shown
4	Player 2 updates game	N/A	N/A	N/A	Player 1 jump visible
5	No new input	Input.GetKeyDown is False	No data sent	No data received	No change
6	Loop continues	N/A	N/A	N/A	N/A

💡 Loop runs continuously to keep players in sync; stops when game ends or network disconnects

Variable Tracker

Variable	Start	After Step 1	After Step 3	After Step 5	Final
Input.GetKeyDown	False	True	False	False	False
Network Data Sent	None	Jump action	None	None	None
Network Data Received	None	None	Jump action	None	None
Game State Updated	No	No	Yes	No	No

Key Moments - 2 Insights

Why can't Player 2 see Player 1's jump without networking?

Because Player 2's game does not know Player 1's actions until they are sent over the network, as shown in steps 1 and 3 of the execution_table.

Why do we need to continuously send and receive data?

Because the game state changes constantly and both players need up-to-date info to stay synchronized, as the loop in steps 5 and 6 shows.

Visual Quiz - 3 Questions

Look at the execution_table, what network data is sent at Step 1?

A Jump action

B No data

C Player 2 position

D Game state update

💡 Hint

Check the 'Network Data Sent' column at Step 1 in the execution_table

At which step does Player 2 receive Player 1's jump action?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Look at the 'Network Data Received' column in the execution_table

If Player 1 never sends data, what happens to Player 2's game state?

A It updates normally

B It shows Player 1's actions anyway

C It never updates Player 1's actions

D It crashes

💡 Hint

Refer to the 'Game State Updated' column and the key_moments about data sending necessity

Concept Snapshot

Multiplayer games need networking to share player actions.
Each player sends input data over the network.
Other players receive this data to update their game state.
Without networking, players can't see each other's actions.
Continuous data exchange keeps games synchronized.

Full Transcript

In multiplayer games, each player controls their character locally. To see other players' actions, the game must send those actions over a network. For example, when Player 1 presses jump, the game sends a jump action message to Player 2. Player 2 receives this message and updates its game state to show Player 1 jumping. This process repeats continuously so all players stay in sync. Without networking, Player 2 would never know Player 1 jumped. The code example shows sending input and receiving data each frame. The execution table traces these steps clearly. This is why multiplayer requires networking.