Getting Started with Scavenge.rs: Your First Hunt Pilot
Start a small Scavenge.rs browser hunt with clear task, guest/account continuity, review and finish checks. Follow the tested tutorial before sharing.
Start your first Scavenge.rs hunt with one clear task and one closing instruction. You can open the free browser builder as a guest; account registration is not the first required step. This quick-start guide helps you decide what to prepare and what to test before sharing. It makes no thirty-minute setup, unlimited-capacity or device-compatibility promise.
Open the hunt builder when you have a simple activity in mind. For field-by-field instructions, use the main creation tutorial. This page is the first-pilot checklist, not a second full platform manual.
Prepare one small activity
Use supplied material so you can test the wording without arranging a city route. An original proposed example is a text task asking “I show the days and months. What am I?” with the intended answer calendar, followed by an informational task saying where the practice activity ends. The host should provide a calendar picture if it helps the group and test the exact accepted answer. This proposal has not been run as a customer event.
| Decision | What to enter or choose | What to test |
|---|---|---|
| Title and description | Name the practice activity, the supplied material, help contact and finish. | A new participant understands the task without your explanation. |
| Format | Choose Point Based or Guided Tour according to the intended activity. | For Point Based, give every clue a positive point value before saving; confirm the sequence and finish. |
| Task and response | Choose text and configure calendar as the expected answer; add an informational close. | The intended text answer works; use Complete Task for the final instruction and verify the saved finish. |
| Visibility and access | Choose public/private deliberately and the account or guest arrangement you need. | Private removes discovery, not access by password. Open the actual saved link in a separate browser session. |
The three-task worksheet adds a photo option when that serves your purpose. You can also rehearse a paper activity; paper responses do not automatically enter platform results.
Choose guest or account continuity
A free hunt can be prepared as a guest. Ownership is associated with the browser used to create it; clearing storage or changing devices can remove that continuity. Keep that browser available, or use the account-linking controls and test the resulting access before changing devices. Creating an account may serve a later need, but adding a profile image or biography is not a prerequisite for the guest pilot.
Paid hosting requires an account and the payment setup presented by the builder. A free creator does not make an existing paid public hunt free. Check the saved hunt's admission and participant arrangement rather than relying on an unsupported “no limits” statement. Use the product guide for the current delivery choices.
Add photos only if you have a review plan
For a guest-run photo pilot, the tested simple arrangement is automatic receipt approval with separate host discussion of image content. Automatic approval does not inspect the photo. A guest's personal completion can differ from approved points when approval is off; an organizer account alone does not create a manual review path for anonymous players.
If you need in-app human approval, use the separately tested signed-in organizer and participant workflow in the main tutorial's review section, then rehearse your actual settings. Do not promise a review queue, report export, certificate, staff tracking or custom scoring feature merely because an earlier guide listed it.
Save and inspect the actual player link
- Review the title, description, task type, expected answer, points and visibility.
- Save using the builder's actual control and inspect the resulting hunt page.
- Use its saved play link or join code; do not invent an address from the title.
- Open that link in a separate browser session, confirm the intended title and admission, then try the actual play route.
- Complete the task and final instruction and check the saved result. Opening the final task alone is not a finish test.
The connected browser flow requires internet. Keep battery/data available and the storage needed for guest continuity. GPS and QR tasks need their own permission and real-location/printed-code tests; task support does not mean continuous tracking or offline play. Start with the text pilot unless those mechanics serve the activity.
Resolve the first problem before adding more tasks
If the answer is rejected, inspect the saved expected value and test likely spelling variants. If a player cannot find the hunt, use its exact saved link and check visibility/access. If points are missing, inspect approval settings and the participant arrangement. If the creator cannot reopen it elsewhere, check guest ownership and account linking.
Record the actual device, task, result and unresolved issue in the printable pilot checklist. This guidance builds on small internal tests, not a benchmark of every phone or a large-group event. Rehearse your chosen participant path, resolve ambiguous instructions and then expand only as far as your event needs.
Choose a worksheet by purpose in the organizer toolkit: a blank plan, worked sample, rehearsal record, delivery brief, actual-cost model or separate player clues and key. The resource descriptions distinguish proposed designs from the small internal tests.
Start a small practice hunt, or use the planning worksheet to write the prompt, response, help and finish before opening the builder.