Secure reward flow
Create a server-owned first-visit practice reward. A client button requests a known reward ID; the server checks the player, distance, request rate and prior claim before changing temporary state.
Requires Roblox Studio · self-checkedLoading project… · Milestone 1 of 3
Draft preview. This project needs technical review before credited assessment.
Create the narrow request and response path
Create ReplicatedStorage/RequestReward and RewardFeedback (RemoteEvents), Workspace/RewardPad (anchored Part at 0,0.5,0), and StarterGui/RewardGui (ScreenGui) with ClaimButton (TextButton), Status (TextLabel), RewardClient (LocalScript). Use readable sized controls. Create RewardServer in ServerScriptService with RunContext Server.
Acceptance criteria
- Button uses Activated for touch, mouse and gamepad activation.
- The request contains a known ID and no client-supplied amount.
Project milestones
- Available to preview
- Available to preview
- Available to preview
Optional extension
Replace the button with a quest-completion request whose objective evidence is maintained by the server.
Project notes and references
Claims reset on rejoin or server restart; this is not durable reward idempotency or a production economy.
Persistent claims, session ownership, save failures, schema migrations, abuse monitoring and release testing require a reviewed project-specific design.
The website records a self-check, not approved-environment or instructor verification.
Output
Your output will appear here.
Sharing is an explicit choice in your portfolio editor. Label exported work “Learning project”; existing publication rules apply.