The quests block
Your community's quests on a store page, what customers can do in it, and which quests open elsewhere.
Your community's quests, on any page of your store. A customer opens a quest, does it, and claims the reward without leaving.
What customers see
A grid of cards. One per quest, up to four across on a wide page and one on a phone. The quest's picture fills the card. Its rewards sit at the top, and a frosted panel at the bottom holds the title, a short description and a button.
A button that fits the quest. "Complete", "Verify", "Submit" and so on, depending on what the quest asks for. A visitor who is not logged in sees "Sign in to take part" in its place.
A pop-up for the detail. Pressing a card opens the quest over the page: the full description with its formatting, pictures and videos, the rewards, and the form if the quest needs an answer. The page behind stays where it was.
A reward to claim. When a quest is done and its reward is waiting, the pop-up shows "Claim Reward". A prize that needs an email or an address asks for it first. A loot box opens with a reveal.
A short confirmation. "Quest completed", with the reward, at the bottom of the block. The card, the customer's points in the header and the profile card all update at once.
Add it
- In the theme editor, check the FanBase app embed is on and filled in. Setting up covers it.
- Open the page template where the quests should go.
- Press Add block or Add section, choose Apps, and pick the quests block.
- Adjust the settings and save.
Settings
| Setting | Default | What it does |
|---|---|---|
| Heading | Quests | The title above the grid. Leave it empty for none. |
| Quests to show | 10 | Between 3 and 30 |
| Status | All | All, Available (still to do) or Completed |
| Show description | On | The description on each card and in the pop-up |
| Show rewards | On | The rewards on each card and in the pop-up |
| Max card width | 288 px | How wide a card can grow, 200 to 480 px |
| Card height | 360 px | How tall every card is at least, 240 to 640 px. Cards share one height, and grow together if one has more text. |
| Text color | Empty | The text on the cards and in the pop-up, for this block only |
| Glass color | Empty | The frosted panels on each card and the pop-up's background |
| Pop-up glass inset | 10 px | How much of the picture shows as a frame around the pop-up's panel |
| Accent color | Empty | Buttons, links and progress, for this block only |
| Corner radius | 8 px | For this block only |
An empty color follows the app embed's Style settings, and those follow your theme. Styling has the whole picture.
Leave Status on All unless you have a reason. A completed quest is where its reward is claimed, so hiding completed quests can hide a reward a customer has not collected.
Which quests run in the store
The block runs most quests itself. A quest it cannot run still shows, with a button that opens it on your community's own site.
These run in the store
| Kind of quest | What the customer does |
|---|---|
| One press | Presses "Complete" |
| Level check, or another quest done first | Presses "Verify" |
| Hold a number of points | Sees a progress bar towards the target and presses "Check" |
| Written answer | Types it and submits. If your team reviews answers, the quest shows as in review. |
| Answer checked on the spot | Types it and presses "Verify" |
| Enters it | |
| Wallet address | Types it. No wallet app opens. |
| Quiz | Picks one answer. A wrong answer uses an attempt. |
| Poll | Picks one, then sees the results unless the poll is private |
| Prediction | Picks one before it locks, then sees their answer and the split |
| Visit a link, or a page on Facebook, Instagram, TikTok or YouTube | Opens the link, comes back and presses "Verify" |
These open on your community's site
| Kind of quest | Why |
|---|---|
| Image upload | Uploads from the storefront come in a later release |
| Social and game quests: X, Discord, Twitch, YouTube, Spotify, Steam, FACEIT, Battle.net | They need the customer to link that account. Linking from the storefront comes in a later release. |
| Riot Games quests | They need a region as well as an account |
| Wallet balance checks | Connecting a wallet is not offered in the store |
| Referral quests, and quests that count other quests or events | Not in the store yet |
If most of your quests are in the second table, the block will mostly send customers away. For a store, lead with quests from the first.
Rewards
| Reward | In the store |
|---|---|
| Points and XP | Claimed in the pop-up |
| Items | Claimed in the pop-up |
| Discord roles | Claimed in the pop-up |
| Prizes | Claimed in the pop-up, with a details form when the prize needs one |
| Loot boxes | Claimed in the pop-up, with a reveal |
| Profile pictures, borders and backgrounds | A button that opens your community's site |
| Rewards your team hands out by hand | A button that opens your community's site |
Sign-in
- Visitors see every quest, with "Sign in to take part" on the ones the block runs. It opens your store's login and returns to the same page.
- Logged-in customers get the buttons straight away.
- The first action joins the community. A customer is not a member until they do something. Completing their first quest joins them and completes it in one press.
- A new customer picks a username the first time they complete or claim.
When a quest is stopped
A quest that cannot be done right now keeps its button, greyed out, with a note saying why: a tier it needs, attempts used up, an answer under review, a prediction that has locked. The customer is never left guessing.
Descriptions
The pop-up shows the description as your team wrote it in the Hub.
- Links open in a new tab
- Pictures load as they scroll into view
- Videos play inside the pop-up from YouTube, Vimeo and Twitch. A video from anywhere else shows as a link.
If a video area stays empty, your store's security policy is blocking the video host. Your theme developer can allow it.
Troubleshooting
| What you see | Cause |
|---|---|
| Only the heading | The block could not load the quests. Open the theme editor to read why. Usually the community slug or API URL. |
| No buttons on the cards | Let signed-in customers take part is off in the app embed |
| Most quests open your community's site | Those quest types do not run in the store yet. See the tables above. |
| "Verify" is greyed out on a visit quest | The customer has not opened the link yet on this visit |
| The Completed view says there are no quests | The customer has not finished one, or is not logged in |