Client vs. Server: Who Sees the Changes

Learning route

Prepare first, then do it; after seeing the result, remember to save it.

Every time a small step is completed, it is tested. Say what you expect to see first, and then use Play and Output to check it. Don't rush to write all the code at once.

Step by step

01· First draw two operating positions

Ordinary Scripts in ServerScriptService are run on the server. The LocalScript in StarterPlayerScripts will be copied to each player's PlayerScripts and run on their respective clients.

This lesson keeps the map small and uses the default small Baseplate test. You don't need to modify your account, publishing permissions, or cloud settings.

1. Create Anchored SharedBlock, Size=8, 4, 4, Position=0, 2, -12.
2. Create ServerScriptService>SharedWorld(Script).
3. Expand StarterPlayer > StarterPlayerScripts and create MyView (LocalScript).

Step by step

02· Server changes to sharing scenario

The server turns the shared square green, and the client receives this change. Normal network replication takes time and it should not be assumed that it will arrive at the exact same time as another message.

Adding [Server] in front of print is just our own reading tag. The real execution source depends on the context of Output.

1. Put the code into SharedWorld.
2. When playing, observe that the box turns green and there is a server message in Output.

local block = workspace:WaitForChild("SharedBlock")
block.Color = Color3.fromRGB(70, 220, 150)
print("[Server] SharedBlock is green")

Step by step

03·Each client has its own LocalPlayer

Players.LocalPlayer represents the player who is using this screen on the client side. The server manages many players at the same time, and there is no "only me".

The following code is used to create a simple interface, and there is no need to use the file of Lesson 15. It only shows the identity and does not copy the same name on other people's screens.

1. Put the code into MyView.
2. Note that the Parent of ScreenGui is the PlayerGui of the current player.
3. After Play, read the name in the upper left corner and find the corresponding Client output.

local Players = game:GetService("Players")
local player = Players.LocalPlayer
local gui = Instance.new("ScreenGui")
gui.Name = "MyViewGui"
gui.ResetOnSpawn = false
local label = Instance.new("TextLabel")
label.Size = UDim2.fromOffset(300, 56)
label.Position = UDim2.fromOffset(16, 16)
label.TextSize = 20
label.Text = "我的屏幕：" .. player.Name
label.Parent = gui
gui.Parent = player:WaitForChild("PlayerGui")
print("[Client] This is", player.Name)

Step by step

04 · Open two clients for comparison

Select Server & Clients in Studio test mode, set up two clients and start. Different versions of the button may have different locations. Find them by function name instead of memorizing the icon coordinates.

View the two client and server perspectives respectively. Don't mistake two client windows for two servers. The game still only has shared servers for this round of testing.

1. Verify that both players see the green SharedBlock.
2. Confirm that the two labels display their player names respectively.
3. View player records in Server Explorer; client-specific interfaces should not be treated as server authoritative data.

Step by step

05 · Decide where a feature should live

The personal performance of cameras, flashcards, button feedback, etc. is usually handled by the client.

If the client wants to do something that will affect the common rules, it needs to make a request. The next lesson will use RemoteEvent to hand this request to the server for inspection.

1. Write Client or Server respectively for "Open prompt card, obtain gold coins, change camera, receive treasure box".
2. End all test clients with End Session.
3. Save the project and compare it with a screenshot of two players to avoid leaving a test window that takes up resources.

Exit questions

Answer it yourself first, and then expand on it.

Explore further

This is where we start when we need to check the data.

The text code can be copied directly. First confirm the script type, placement, and whether this code is a complete version or a small experiment; do not run multiple versions of the same script superimposed. The source of the interface reference picture has been marked. The object names in the picture may be different from those in this lesson. Please refer to the operation steps.

• Client and server ↗
• Studio test mode ↗