Destination Hunts
Library & Shared Assets

Game Templates

Reusable hunt blueprints — what a template captures, visibility and cloning rules, saving an event as a template, and how events are created from templates.

A game template is a complete, reusable hunt blueprint. Templates live under Game Templates in the sidebar.

What a template captures

A template snapshots the full structure of a hunt:

  • Challenges — links to library challenges, with per-template overrides (sort order, starter flags, max completions, speed bonuses, location overrides, stack membership)
  • Groups — challenge groups with their unlock modes and unlock conditions
  • Stacks — multi-step challenge stacks
  • Default teams — team names and visual identity only (never join codes)
  • Artifacts and collectibles, including their reward wiring (which challenges award which artifacts/collectibles, and collectible requirements)
  • Branding — logos, colors, theme, and related event styling

The template detail page exposes these as tabs: Overview, Challenges, Stacks, Artifacts, Collectibles, Teams, Branding.

Visibility

  • Seeing templates: list views show your own org's templates plus public ones. Opening or cloning a template requires it to be yours or public.
  • Editing/deleting: your own org's templates only.
  • Publishing public: setting Visibility to Public is restricted to internal Destination Tours organizations ("Only internal organizations can set visibility to public"). New templates are always created Private.
  • The Featured switch ("Highlight this template in the marketplace") stars a template in listings.

Cloning a template

On a template's detail page, Clone opens the Clone Template dialog ("Create a copy of this template with all its challenges and groups."):

  • Template Name — defaults to {name} (Clone).
  • Exclude location-based challenges — a checkbox that removes challenges with GPS coordinates, useful when reusing a template in a different city.

Cloning deep-copies everything (challenges, groups, stacks, default teams, artifacts, collectibles, and reward wiring) into your organization as a new template you fully own.

Saving an event as a template

From an event's More menu, Save as Template captures the event back into a template. You can either create a new template (always private, and linked to the event) or update the template the event is already linked to, overwriting its contents.

Creating an event from a template

The API supports creating an event directly from a template: pass a template id at event creation and everything is copied in — challenges (with locations snapshotted per the location hierarchy), groups, stacks, artifacts, collectibles, reward wiring, and branding. Default teams are instantiated with fresh join codes (templates never store codes), a Welcome group is seeded, and the event always starts in Draft.

No template picker in the event form yet

The current Create Event form does not expose a template picker, so this API path has no direct button in the UI. The in-app ways to reuse a template today are: Clone the template and build an event from its content, Save as Template from an existing event, and Import on the Events page (which accepts a JSON export envelope). Don't go hunting for a "create event from this template" button — it isn't there yet.

On this page