A QR code is how something that happens in a room counts inside an Adventure. A player scans a printed or projected code with their phone, and the Adventure records it. BLUERABBIT has three kinds of QR code, and each does a different job: an achievement code awards a badge, a task code completes a repeatable task, and a milestone code completes a milestone outright.
Achievement QR Codes: Scan to Earn a Badge
Every achievement has a magic code, and once the achievement is saved its QR Code appears in the achievement's settings, next to the badge. Scanning it redeems the code and awards the achievement on the spot, with the same celebration as any other reward. It's the right tool for a one-time check-in: "attended orientation", "visited the lab", "met the founder".
- When the adventure has Magic Codes switched on, players can also type the code into the Redeem a code panel instead of scanning. Put it on the slide under the QR code for anyone whose camera won't cooperate.
- A player who already holds the achievement is told so, and nothing is awarded twice. Branches still hold: nobody can earn two achievements from the same branch.
- An earned achievement can be one of a milestone's conditions, so the badge scanned at the door can be what opens the next piece of content.
For one-time unique codes and handing out links in bulk, see Achievements, Paths & Ranks.
Task QR Codes: Repeatable Check-Ins
A task can be set up so that scanning its QR code is the only way to complete it. That suits anything a player does again and again in a physical place: a gym visit, a daily stand-up, each morning of a workshop. In the task editor on Manage Content's Tasks tab, set Completes when… to "The player marks it done (button or QR scan)", Recurrence to "Timed (cooldown between completions)" with a cooldown, and Reset via to "Scanning a QR code". Once the task is saved, its code appears in the editor, ready to print or display.
- Hide it from the app. Untick "Show the QR code to players in the app" and the player's task card says "Find the QR code and scan it to complete this task" instead of showing the image, so they have to go where the printed code is. You still see the code in the editor.
- Regenerate it if a photo leaks. "Regenerate (invalidates the old code)" issues a new code, and the old one stops working at once. Reprint and replace every posted copy.
- The cooldown holds. A scan before the cooldown is up shows "Not ready yet" with a countdown, so scanning the same poster twice doesn't pay twice.
See Running the Garden as a GM for everything else a task can do, and Garden Tasks for the player's side.
Milestone QR Codes: Quick-Complete
A milestone can also be completed by a scan. It completes the milestone outright for the player who scans it and pays its XP and BLOO, plus any item or achievement reward, skipping level requirements, conditions, start dates and deadlines. It's the one completion path in BLUERABBIT deliberately built to skip the rest of the system. The milestone has to be published, a second scan only says it's already completed, and the completion screen offers Back to the journey.
Because it skips everything, it's not the tool for anything you actually want gated. Reserve it for milestones where "being physically present and scanning" is the whole point.
The milestone builder doesn't currently display a milestone's QR code, so for a check-in you're printing now, use an achievement or task code.
One Code Per Cohort
A QR code belongs to the adventure it was made in, so each cohort of a template has its own. An achievement lives on the template, but its QR code is made per cohort: open the achievement from inside the cohort you're printing for, and the editor tells you which adventure the code redeems into. Tasks belong to each cohort too. A cohort's copy of a QR task starts without a code, so open it on that cohort's Tasks tab and save it to issue one. Printing one cohort's code for another sends every scan to the wrong adventure.
Before the Event
- Get everyone enrolled and logged in first. A phone that isn't logged in goes to the login page when it scans, and after signing in the player lands on their adventures rather than back on the code, so they have to scan again. Sessions last 30 days, so logging in once the day before is enough.
- Test every code with a player account before you print it.
- Put the code where the moment happens: on the door, at the station, on the last slide of the session.
Good Use Cases
- An in-person orientation day, where "you showed up and scanned in" should count on its own: an achievement code at the door.
- A scavenger hunt where physical locations map to badges, each with its own code.
- A recurring check-in, like the gym or a daily stand-up: a timed task with its code hidden from the app.
- A live session on the Event Schedule: the schedule tells players where to be, and a code in the room records that they were there.