Comprehensive Project: Complete the Energy Island Scavenger Hunt

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 determine the minimum playable rules

The first version only made three crystals and one terminal. There are no countdowns, stores and cloud saves to avoid multiple systems from failing at the same time. Go through a round first, then choose an expansion.

In this session, the collected progress will be retained when the character is reborn; it will be reset after leaving. When completed, you will get a medal for this game, and the number will not increase if you reuse the terminal.

1. Create and save "Initials_Lesson29_v01".
2. Write down the rules of the game: three different crystals → terminal confirmation → get a medal.
3. Keep Baseplate as safe ground and do an island theme with low platforms and signposts.

Step by step

02 · Build the scene according to the object list

Strictly consistent object names are the first step in connecting scenes and code. You can change the colors and decorations, but don't change the names and levels used by the script yet.

Arrange the crystals in a visible place, and then hide them next to the route after the test is successful. Hiding objectives too early will make it difficult to tell whether the gameplay is too difficult or the code is unresponsive.

1. Create a Crystals folder under Workspace, containing three parts: CrystalA, CrystalB, and CrystalC.
2. Crystal Size=3,3,3; Positions are -12,3,-12; 0,3,-26; 12,3,-12; Anchored=true, CanCollide=false, CanTouch=true.
3. Create Terminal: Size=6,4,4, Position=0,2,-40, Anchored=true.
4. Create ProximityPrompt in Terminal, ActionText=Complete Task, ObjectText=Energy Terminal, HoldDuration=0.5, MaxActivationDistance=10.
5. Create ServerScriptService > IslandQuest (Script) and StarterPlayerScripts > IslandHud (LocalScript).

Workspace
├─ Crystals (Folder)
│  ├─ CrystalA (Part)
│  ├─ CrystalB (Part)
│  └─ CrystalC (Part)
└─ Terminal (Part)
   └─ ProximityPrompt
ServerScriptService
└─ IslandQuest (Script)
StarterPlayer > StarterPlayerScripts
└─ IslandHud (LocalScript)

Step by step

03·The server records the progress and checks the end point

IslandCount is the number of crystals, IslandFinished indicates whether it has been completed, and IslandMessage provides prompts to the interface. The collected table records the specific crystals that have been collected to prevent repeated touching to refresh the progress.

The terminal only reads the server's own count and does not accept "I have collected it all" reported by the client. Medals are added only after the status check, distance check and one-time mark have all been passed.

1. Put the complete code into IslandQuest.
2. Play first and use the Output or Player attributes to verify the quantity, and then access the HUD.
3. This project only retains this task server script and does not superimpose the CrystalQuest of Lesson 19.

local Players = game:GetService("Players")
local crystals = workspace:WaitForChild("Crystals")
local terminal = workspace:WaitForChild("Terminal")
local prompt = terminal:WaitForChild("ProximityPrompt")
local TARGET = 3
local collected, lastUse = {}, {}

local function setup(player)
    if collected[player] then return end
    collected[player] = {}
    player:SetAttribute("IslandCount", 0)
    player:SetAttribute("IslandFinished", false)
    player:SetAttribute("IslandMessage", "找到 3 颗不同晶石，再前往能量终端。")
    local stats = Instance.new("Folder")
    stats.Name = "leaderstats"
    local medals = Instance.new("IntValue")
    medals.Name = "Medals"
    medals.Value = 0
    medals.Parent = stats
    stats.Parent = player
end
local function near(player, part, distance)
    local character = player.Character
    local root = character and character:FindFirstChild("HumanoidRootPart")
    local humanoid = character and character:FindFirstChildOfClass("Humanoid")
    return root and humanoid and humanoid.Health > 0
        and (root.Position - part.Position).Magnitude <= distance
end
Players.PlayerAdded:Connect(setup)
for _, player in ipairs(Players:GetPlayers()) do setup(player) end
Players.PlayerRemoving:Connect(function(player)
    collected[player], lastUse[player] = nil, nil
end)

for _, crystal in ipairs(crystals: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)
        if not player or not near(player, crystal, 8) then return end
        local record = collected[player]
        if not record or record[crystal] or player:GetAttribute("IslandFinished") then return end
        record[crystal] = true
        local count = math.min(TARGET, (player:GetAttribute("IslandCount") or 0) + 1)
        player:SetAttribute("IslandCount", count)
        if count == TARGET then
            player:SetAttribute("IslandMessage", "集齐啦！前往能量终端，按提示完成任务。")
        else
            player:SetAttribute("IslandMessage", "找到 " .. crystal.Name .. "，继续寻找其他晶石。")
        end
    end)
end

prompt.Triggered:Connect(function(player)
    if not collected[player] or not near(player, terminal, 12) then return end
    local now = os.clock()
    if now - (lastUse[player] or -math.huge) < 0.5 then return end
    lastUse[player] = now
    if player:GetAttribute("IslandFinished") then return end
    local count = player:GetAttribute("IslandCount") or 0
    if count < TARGET then
        player:SetAttribute("IslandMessage", "还差 " .. (TARGET - count) .. " 颗不同晶石。")
        return
    end
    player:SetAttribute("IslandFinished", true)
    player.leaderstats.Medals.Value += 1
    player:SetAttribute("IslandMessage", "任务完成！你获得了一枚探险奖章。")
    print(player.Name, "finished Energy Island")
end)

Step by step

04 · Let players see their progress

HUD only reads the server status and does not issue rewards or determine task completion. During initialization, first listen for changes and then render again to avoid missing the previous state when the interface is opened.

The panel width takes 84 per cent of the screen and limits maximum width; text maintains a fixed word number and allows for line change. It is easier to read than harden a long list of tips into a very small box.

1. Put the complete code into IslandHud.
2. After playing you should see "Spar 0/3" and a mission description.
3. When collecting and using the terminal, confirm that the text follows the status change.

local player = game:GetService("Players").LocalPlayer
local gui = Instance.new("ScreenGui")
gui.Name = "IslandGui"
gui.ResetOnSpawn = false
local panel = Instance.new("Frame")
panel.Position = UDim2.fromOffset(16, 16)
panel.Size = UDim2.new(0.84, 0, 0, 132)
panel.BackgroundColor3 = Color3.fromRGB(18, 35, 55)
panel.Parent = gui
local limit = Instance.new("UISizeConstraint")
limit.MaxSize = Vector2.new(420, 132)
limit.Parent = panel
local corner = Instance.new("UICorner")
corner.CornerRadius = UDim.new(0, 12)
corner.Parent = panel
local label = Instance.new("TextLabel")
label.Position = UDim2.fromOffset(12, 10)
label.Size = UDim2.new(1, -24, 1, -20)
label.BackgroundTransparency = 1
label.TextColor3 = Color3.fromRGB(240, 247, 255)
label.TextSize = 20
label.TextWrapped = true
label.TextXAlignment = Enum.TextXAlignment.Left
label.Parent = panel
gui.Parent = player:WaitForChild("PlayerGui")

local function render()
    local count = player:GetAttribute("IslandCount")
    local finished = player:GetAttribute("IslandFinished")
    local message = player:GetAttribute("IslandMessage") or "等待任务数据…"
    local heading = finished and "探险完成！" or "能量岛探险"
    label.Text = heading .. "\n晶石 " .. tostring(count or 0) .. "/3\n" .. message
end
for _, name in ipairs({"IslandCount", "IslandFinished", "IslandMessage"}) do
    player:GetAttributeChangedSignal(name):Connect(render)
end
render()

Step by step

05·Go through the acceptance form completely

"Cleared once" is not enough to prove that the task is reliable. You also need to try missing, receiving twice, and submitting twice to confirm that the rules still hold in these situations.

Two players can share the same crystal, but each player has their own progress. The crystals will not disappear globally. This is a deliberately chosen rule for this project.

1. Use the terminal if there are 0 medals: the prompt is 3 less, Medals=0.
2. A, A, B, C: the progress is 1, 1, 2, 3 in sequence.
3. Convergence resubmission: Medals=1; duplicate submission remains 1.
4. Midway rebirth: progress reserved; Stop restarting: progress 0.
5. Two people complete respectively: both sides get 1 each, without affecting each other.

Step by step

06 · Only add one extension at a time

Save v01 first, then pick an extension: clearer road signs, complete particles, or a gentle night scene. Don't add timer, save and store at the same time.

The finished product of this course is a classroom prototype and does not promise complete online anti-cheating or lasting rewards. The next lesson will wrap up testing, device experience, and security sharing.

1. A man who hasn't read the code, please try to find three crystals and see where he gets lost.
2. Only correct the point that most affects the experience and save v02.
3. Intercept three real game pictures of the starting point target, collection progress, and completion results, and do not use reference pictures to pretend to be your own results.

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.

• Server Boundaries and Authentication ↗
• Interface size and position ↗