Sandbox
Sandbox creators can troubleshoot delayed or incomplete Experience results while preserving the last known state
Begin with one saved Experience and identify the exact state that should change. A completed result has visible evidence, such as a Ready action, updated Gallery details, or expected behavior in the intended test environment. An incomplete result has observable evidence, such as a Pending action or an unmet requirement. When no error, unmet prerequisite, or changed input appears, treat the result as unresolved rather than assuming a delay. Record the starting state, make one bounded move, and assess that move before adding another.
The short version: When a Sandbox Experience result is delayed or incomplete, check the saved record once before deciding whether to wait, retry, adjust, reconcile, or stop.
Anchor the first check to one saved Experience
The first check needs a saved Experience, an identified target record, and a concrete result that can be confirmed.
Confirm the record being changed
An Experience must be created and saved in Game Maker before it appears in Inventory for management. Match its name and editable copy before sharing, publishing, or changing its setup. This prevents a successful update to one copy from looking like a failure in another.
Define completion before acting
Completion evidence depends on the action. A launch requirement should show Ready, a Gallery update should appear on the existing listing, and a gameplay fix should work in the environment where the problem occurred. A button press or submitted request is only an action. It does not confirm the resulting state.
Choose a response from the visible state
The next move should follow the evidence already shown by the Experience, not the number of times an action has been attempted.
Suppose one saved Experience has just been shared, but the expected listing change remains unclear. Keep the same record and compare only the state before and after that action. If the interface shows a missing field or ownership condition, address that requirement before sharing again.
Decision checklist
- Wait when the submitted action shows no error, no prerequisite is marked missing, and the target record has not changed.
- Retry only a reversible action that cannot purchase, transfer, launch, close, or overwrite another Experience.
- Adjust the setup when the interface identifies a missing field, unavailable Asset, incompatible build, or unsuitable location.
- Reconcile the saved and shared copies when Editor, Gallery, or Game Client results disagree.
- Stop when the next step would create an unclear wallet request, duplicate record, or irreversible commitment.
The check is complete when the same target record shows the expected status or behavior. If that proof remains absent, preserve the original copy and the last clear state for the next check.
Separate missing launch requirements from delay
A Pending launch action identifies work that has not reached Ready; it does not by itself prove that processing is slow.
Experience Page content
The Experience Page has mandatory text and media fields. An incomplete field is a setup issue, so waiting will not complete it. Review the Experience Page fields and complete the missing requirement before returning to the launch status.
Asset Review
Asset Review separates Ready Assets from unavailable Assets and NFTs that the creator does not own. Those states describe different recovery paths. A missing ownership condition cannot be resolved by repeatedly reopening the manager, while an unavailable Asset requires a change to the Experience.
Map Location
Map publishing requires a suitable LAND location owned through the account’s associated wallet. The available space must fit the Experience. The Launch button becomes available automatically only after every Pending action changes to Ready. Until then, the unfinished action remains the relevant evidence.
What confirms that a Gallery update worked?
A Gallery update is confirmed by finding the original Experience and checking its revised name, description, or shared content.
Gallery placement follows the Experience creation date rather than the latest share date. An older project may therefore remain away from the first page after a successful update. Use Gallery search before treating absence from the opening results as failure. Sharing the same Experience again updates its Gallery details, so creating another copy is unnecessary when the original record remains available.
Reconcile results across testing environments
Check the same behavior in the environment where creators or players will encounter it before treating the result as reconciled.
Editor baseline
Editor testing supplies the controlled baseline. Check the affected quest, trigger, collision, or logic state without changing unrelated systems. If an earlier action can block a later quest, repair that sequence before sharing another build.
Gallery behavior
Gallery testing can expose behavior that did not appear in Editor mode. Compare the shared Experience with the saved baseline instead of assuming that one environment proves the other. A difference points to a reproducible test case, not a reason to alter several mechanics at once.
Game Client access
For multiplayer testing, access evidence also includes the validity of the generated test link. A generated multiplayer test link expires after 45 minutes. An expired link calls for a new link rather than changes to the Experience. That distinction preserves the gameplay baseline while replacing only the expired access method.
Resolve Asset states without blind retries
Use the Asset Review category to distinguish an unavailable Asset from an NFT that the connected wallet does not own.
An unavailable Asset must be replaced by editing the Experience in Game Maker. An item under NFTs to Buy is present in the Experience but is not owned by the launching wallet. The supported choices are to buy or receive that NFT, or replace it with an eligible Asset. For Gallery sharing, owned NFTs must be in the connected wallet, while a creator’s own Assets must be published in the Workspace.
These are prerequisite changes, so waiting alone does not alter the result. After making the smallest necessary correction, return to the same Experience and check whether its Asset status has changed.
Stop cleanly and preserve a reversible next move
A clean stop leaves the saved Experience intact and records the unresolved status without adding another commitment.
Closing a launched Experience is a specific availability change, not a general troubleshooting refresh. It removes the Experience from availability and unpublishes its Experience Page. The existing setup and configuration are retained, but the Experience must be launched again before it returns to the Map.
Use closure only when taking the live Experience offline is the intended action. For an uncertain Gallery update, incomplete Asset Review, or expired test link, keep the original record and stop at the reversible boundary that matches the problem.
Sandbox - your questions answered
How quickly do access restriction changes take effect after launch?
Access restriction changes are documented to apply within minutes after they are saved. That wording does not promise an exact second. Check the restriction attached to the same Experience and test the affected access condition before editing another rule. If the intended change appears, the saved restriction is the completion evidence.
Can launch requirements be completed in any order?
Yes, the launch actions can be completed at the creator’s own pace and do not require a fixed order. The Launch button still depends on every required action reaching Ready. Completing Map Location first, for instance, does not bypass an incomplete Experience Page or unresolved Asset Review.
Does editing a published Experience Page require closing the Experience?
No, a published Experience Page can be edited without closing the Experience. Saved Page changes are reflected on the published page, so closure is not a repair step for ordinary text or media edits. Confirm the revised field on the existing page before changing the Experience’s launch state.
Must a launched Experience close before moving to another location?
Yes, an Experience cannot change location while it is launched and open. It must be closed and then launched again at the new eligible location. Closing also makes the Experience unavailable and unpublishes its Experience Page, so the move should be treated as an availability change rather than a harmless retry.
Is the Experience Page allowed to go live before the Experience?
Yes, the Experience Page can be published before the Experience launches once its mandatory fields are complete. This gives the page its own observable publication state. It does not clear Asset Review, choose a Map Location, or make the Experience playable on LAND.
Which access settings are required before the Launch button activates?
NFT access restrictions are optional rather than a universal launch requirement. The required workflow includes completing the Experience Page actions, Asset Review, and Map Location until their statuses are Ready. An optional access rule should not be mistaken for the unresolved requirement when one of those mandatory actions remains Pending.