Skip to main content

Routes & sets

info

A set groups triggers of the same type under one name in the trigger list.

A route is a set that also has an order and unlock behaviour. Players move through the stops in that order, or in one of the open patterns below.

Routes and sets are created from the trigger list with Multiple triggers / set / route. You can also group triggers that already exist from Select mode, or by dragging triggers into (and out of) a set or route.

A set can hold GPS locations, QR codes, user buttons, or any other single trigger type. A route can be built from GPS locations, QR codes, or user buttons. A route needs at least two triggers.

Create a set or a route​

Open Multiple triggers / set / route on the trigger list.

  • "Don’t group"; create several triggers of the same type, without a set.
  • "Group in a set"; put the new triggers in one set. They share a set name and show as one block in the list. There is no unlock order.
  • "Group as a route"; create a sequenced route. GPS, QR, and user-button triggers can use unlock behaviour.

Then set:

  • "Number of triggers"; at most 50 per batch. A set or route needs at least 2. An application can hold at most 1000 triggers.
  • "Set name" or "Route name"; the name shown on the collapsed block in the list.
  • "Set color" or "Route color"; optional colour for the block in the trigger list.
  • "Name prefix" or per-stop names; each name in the application must be unique. Numbered names update when you change the order and save.

For a GPS route, coordinates are placed later, when you roll the application out to a location.

Route behaviour​

Pick Route behavior (GPS), Unlock behavior (user buttons), or the QR equivalent. The panel How it works shows what players see at the start, and what changes after a visit, a completion, or a scan.

GPS locations​

  • "Linear — unlock next (hidden)"; only the first location is visible and visitable. Visiting it makes the next location visible and active. The order is fixed.
  • "Linear — unlock next (route visible)"; every location is on the map, but only the first can be visited. Visiting it activates the next location. Players see the whole route and still follow a fixed order.
  • "Open — visit in any order"; every location is visible and visitable from the start. Visiting one location does not change the others.
  • "Any start — then unlock rest one-by-one"; every location starts visible and visitable. After the first visit, earlier stops close and the rest unlock forward, one by one.
  • "Hidden any-start — then reveal all"; every location starts active but hidden. After the first visit, the remaining locations become visible. They were already active.

For GPS you can also set what happens to the stop that was just visited:

  • "After visiting — visibility"; remain on the map, or disappear.
  • "After visiting — activeness"; remain visitable, or no longer visitable.
  • "Manually triggerable after visit?"; allow tapping the location to fire it. This also enables the popup on the icon.

QR codes​

  • "Linear — unlock next"; only the first code is active. Scanning it activates the next code.
  • "Open — scan in any order"; every code is active from the start.
  • "Any start — then unlock rest one-by-one"; every code starts active. After the first scan, earlier codes deactivate and the rest unlock forward.

"After scan — activeness" chooses whether a scanned code stays active or becomes inactive.

User buttons​

User-button routes use Unlock behavior, with the same patterns as GPS, worded as completion instead of a map visit: hidden linear, all visible linear, open, any start then one-by-one, and hidden any-start then reveal all.

The set in the trigger list​

A set is one coloured block. The count on the block is the number of stops.

  • Collapse or expand the block to hide or show the stops.
  • Drag the block to move the whole set in the list.
  • Drag ungrouped triggers into a set or route, or drag members out.
  • "Edit set" or "Edit route" opens the settings for that set or route. Changes apply when you save.

In Edit set / Edit route:

  • "Set name" or "Route name".
  • "Set color" or "Route color".
  • Stops list (caption depends on type: locations, QR codes, buttons, or triggers); drag stops in the trigger list to reorder. Numbered names update after you save. Undo order restores the order from before this edit.
  • "Add triggers"; only ungrouped triggers of the same type can be added.
  • "Remove from this set" / "Remove from this route"; the trigger stays in the application, ungrouped.
  • Dissolving the set or route ungroups every member. The triggers stay in the list.

Locked actions from a route​

Saving a route writes locked actions, labelled "Route", at the start of each stop’s action chain. This happens for a route of at least two GPS, QR, or user-button stops.

They are written again when you save the route behaviour, the stop order, or the members of the route (add or remove). They are removed when the route is dissolved, or when fewer than two stops remain. A set without route behaviour has none of these actions.

Unlock actions are written for "Linear — unlock next (hidden)", "Linear — unlock next (route visible)", "Any start — then unlock rest one-by-one", and "Hidden any-start — then reveal all" (and the QR and user-button wording of those patterns).

For "Open — visit in any order", a locked action is written when "After visiting — visibility" or "After visiting — activeness" (on a QR route: "After scan — activeness") hides the stop or makes it inactive.

These actions stay at the front of the chain. Change them from "Edit route" on the first stop. Actions you add yourself sit after them.

Select mode​

Select mode works on the trigger list.

  • Click a trigger to select it.
  • Shift-click another trigger to select the contiguous range between them.
  • "Create set"; group two or more selected triggers of the same type into a new set.
  • "Create route"; group selected GPS, QR, or user-button triggers into a new route.
  • "Add to set/route"; add the selection to one existing set or route. Ungrouped triggers must be the same type as that set. Select members of one set only when removing.
  • "Remove from this set" / "Remove from this route"; take the selected members out. The triggers stay in the list.
  • "Delete"; delete the selected triggers.
  • "Clear selection"; leave select mode.

The same limits apply as in Edit set: one set at a time, one trigger type, and a route rebuilds its unlock actions when its members change.

Actions on a set​

These actions target one set. They appear under the Set/Route group in the action picker. A single action does not mix types, so a GPS set and a QR set each need their own action.

  • "Change visibility set"
  • "Change activeness set"
  • "Change visibility and activeness set"

Choose a same-type set without a route.

Active from the start​

"Active from the start" (Start this route when the team logs in) controls when the route becomes live.

  • On: the route starts at first login. Manage shows a locked explanation under Upon Login (not a real action in the chain).
  • Off: the route stays hidden until an Activate route action runs it (for example from another route’s end trigger).

Dynamic start locations​

"Spread users / Dynamic start locations" is available on a sequenced route. Teams can start at different stops and still complete a full lap. The last stop for a team is the one before their own start.

  • Mark stops under "Possible start locations". Use "Can be start location" on a stop when selecting locations. A stop that is not eligible stays on the route and cannot be chosen as a start. At least one stop must remain eligible.
  • Enabling dynamic starts adds a route end blank (End). It fires once when a team finishes the lap. Hang finish logic on that blank, such as a message, a score change, Activate route for the next chapter, or another action.
  • Visible and active follow the route behaviour and the assigned start. The default start is stop 1. Change starts with How starts are assigned or from the host Routes page, not with the visible/active checkboxes on the stops.

"How starts are assigned":

  • "Round robin"; each new team gets the next eligible start from the top. Starts stay evenly spread. Logging in again does not move a team that already has a start.
  • "Random"; each new team gets any eligible start at random. Two teams can get the same start.

The host can still change a team’s start on the Routes page until that team has visited a stop.

Host: route starts​

When the application contains a sequenced route with dynamic start locations, the host menu shows Routes.

  • Choose a Start location per team. Changes apply after Save.
  • "Distribute this route" or "Distribute all routes" spreads eligible starts with Round robin or Random. Every team still completes the full route. Setting a start again resets that team’s progress on the route.
  • Filter with "Show only possible start locations" or "Show all locations".
warning

After a team has visited a point on the route, that start can no longer be changed for that team.

Placing a GPS route​

GPS stops in a route have no coordinates in the application. Place them when you roll the application out to a location. See Quick placement and drag and drop.