Attributes and tasks: Collect three energy crystals

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 · Use Folder to put task items together

Create a folder containing only crystal parts, and the script can find them all at once. Don't put lights, signposts, and scripts in there that the program might mistake.

For simplicity, this lesson keeps the spar visible. Whether each player has collected it is determined by the server's records, not by global hidden crystals.

1. Create Folder: Crystals in Workspace.
2. Create CrystalA, CrystalB, and CrystalC inside, with Size=3,3,3, and Position respectively -10,3,-10; 0,3,-20; 10,3,-10.
3. Each crystal Anchored=true, CanCollide=false, CanTouch=true; colors are different.
4. Create CrystalQuest in ServerScriptService.

Step by step

02·First recognize the two progress labels

Crystals saves the collected quantity, QuestComplete saves whether it is completed. SetAttribute sets a value, and GetAttribute reads it; they are different from the built-in Position and Color, and are self-defined labels.

Collection records must be modified by the server. The client can use GetAttributeChangedSignal to update the HUD in the future, but it cannot treat the number it changes as the actual task progress.

1. Select Player from the server perspective of Play and find Attributes under Properties.
2. You should initially see Crystals=0, QuestComplete=false.

Step by step

03 · Use "Player → Already Received Crystal" to prevent duplication

collected[player] is the collection table of this player, which uses crystal objects as keys. Touching the same object repeatedly will return immediately, while touching another one will continue processing.

All judgments are made before increasing progress. The distance check allows a range of 8 studs for small hedrons; this range needs to be redesigned when changing to larger objects.

1. Put the complete code into CrystalQuest.
2. Touch in the order of A, A, B, C, and the expected progress is 1, 1, 2, 3.
3. Note that the target quantity TARGET must be consistent with the lesson plan, and decorations are not counted as task items.

local Players = game:GetService("Players")
local folder = workspace:WaitForChild("Crystals")
local TARGET = 3
local collected = {}
local function setup(player)
    collected[player] = {}
    player:SetAttribute("Crystals", 0)
    player:SetAttribute("QuestComplete", false)
end
Players.PlayerAdded:Connect(setup)
for _, player in ipairs(Players:GetPlayers()) do setup(player) end
Players.PlayerRemoving:Connect(function(player) collected[player] = nil end)

for _, crystal in ipairs(folder:GetChildren()) do
    if not crystal:IsA("BasePart") then continue end
    crystal.Touched:Connect(function(hit)
        local character = hit:FindFirstAncestorOfClass("Model")
        local player = character and Players:GetPlayerFromCharacter(character)
        local root = character and character:FindFirstChild("HumanoidRootPart")
        local humanoid = character and character:FindFirstChildOfClass("Humanoid")
        if not player or not root or not humanoid or humanoid.Health <= 0 then return end
        if (root.Position - crystal.Position).Magnitude > 8 then return end
        local record = collected[player]
        if not record or record[crystal] then return end
        record[crystal] = true
        local count = (player:GetAttribute("Crystals") or 0) + 1
        player:SetAttribute("Crystals", count)
        player:SetAttribute("QuestComplete", count >= TARGET)
        print(player.Name, "Crystals:", count, "/", TARGET)
    end)
end

Step by step

04 · Visible objects may not still be available for collection

The same crystal may have been claimed by A, but is still available for B, so the shared appearance cannot simply represent everyone's task status.

This lesson uses Output and personal Attribute verification. A personal HUD will be added to the comprehensive project; if you want the received crystals to fade out only for you, you also need the client's personal display logic.

1. After A touches CrystalA, and B touches the same crystal again, both of them should get 1 each.
2. If A touches CrystalA again after rebirth, 1 should not be added.
3. The entire task record will be cleared only after Stop and restart.

Step by step

05 · Check the meaning of "three different ones"

The task is completed not by touching three times, but by touching three different crystal stones. Write this sentence down first, and then check whether the code complies with it.

If new spar are later dynamically created, this connection to GetChildren on startup will not automatically overwrite them. The items in this lesson are placed before starting; dynamic generation requires additional processing of ChildAdded.

1. At least five consecutive hits on the same one, with progress remaining at 1.
2. It can still be completed by collecting three in different orders.
3. Verify that no other scripts are changing Crystals at the same time.

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.

• Properties and custom properties ↗