Your copy-and-paste prompt
Replace the [brackets] with your details, then paste this into your assistant.
Turn one small part of a world I drew into a place I can explore. I will supply [one map I own] and [up to three pages of my own notes]. Focus on [three to five rooms, streets or locations]. The audience is [me or people I choose]. Use at most [time and resource budget] and save the result in [private working folder]. Preserve my original files. READ THE WORLD BEFORE BUILDING IT Inventory the supplied pages and give each a stable reference. Make a compact key of the selected places: original label, visible location, confirmed connections, notes and source reference. Keep unusual spellings. Mark unclear text and gaps rather than silently completing them. Separate what my pages say, what I confirm now and what you propose to invent. Show me a simple route diagram before coding. Ask only about ambiguities that change the route or an important story fact. If I cannot resolve a doorway or connection, leave it visibly unresolved; do not draw a new passage and present it as part of the old map. Exclude unrelated private notes. Use only material I own or may adapt; do not import a commercial game's assets or rulebook. MAKE ONE SMALL WALKTHROUGH Build a local browser scene with up to five connected places, a clear entrance, readable labels, keyboard and touch controls, and a way to return to the start. A simple top-down or point-and-click view is enough. Prioritize the map's layout and recognizable details over elaborate 3D art. Let me open a source view that relates each visited place to its original page or region without altering the originals. Include one small interaction, such as opening a chest, reading a sign or finding a key. If that interaction is absent from my notes, label it as a proposed addition and keep it separate from the recovered material. Let me turn additions off while still exploring the confirmed map. Do not invent a whole campaign, new family history or dialogue presented as something I wrote years ago. Make any required placeholder obvious. If an essential route remains unresolved, return a navigable partial scene and its specific gap instead of claiming the whole route works. Keep sound optional and off until requested; the first version does not need narration, external services, accounts or a hosted backend. WALK THROUGH THE ACTUAL RESULT Use the built scene to visit every implemented location, go back through the same connections, try the interaction, switch additions off and restart. Check that the source view points to the right page and that confirmed labels match. Test both the intended phone controls and keyboard when available. State which checks you actually performed. Include reset and a clear statement of whether progress persists. If there is save/load, test the saved file or reload behavior; otherwise explicitly say progress resets. Verify that an absent key or blocked door cannot silently strand the player. Keep unresolved routes in the gap list instead of counting them as tested paths. Stop after one repair pass. Return the playable folder or file, editable source, source-to-scene key, list of confirmed and proposed changes, and a short opening guide with any local-server requirement. If you cannot build or open the scene, return a labeled plan and the missing capability. Do not call it playable without a working artifact. Do not upload, deploy, publish or send any map or scene without my separate approval.
Automatic copying is unavailable. Select the prompt text above and copy it.