String
Claim by {expirationDate}
Experiments
1- The code reading it uses 3 experiments, this one among them
How we know: the 2 files reading it
8479adc51144af78.jsreads 85 strings · uses 3 experiments8515409fd1d3dd4d.jsreads 10 strings · uses 10 experiments2026-11-ad-refresh-immediate-on-focus2026-11-return-full-quest-status-in-decision2025-12-quest-cta-refactor-rollout2026-08-bounties-mobile-quest-bar2026-11-multiquest-client2026-11-linux-steam-sku-detection2026-11-mac-steam-sku-detection2026-08-dont-close-chat2026-07-renewable-end-date-sort2026-09-quest-home-bounties-feature-gate
Written next to it
Strings are stored in the order they were written, so neighbours usually belong to the same feature.
- Explore more Quests
RjPllj - Check Connection
cdd1iy - Got {gameTitle} running, but not detected? Try this.
jy9xiD - Check Progress
VN1Ajl - Claimed Quests
zyNYNB - You haven't completed any Quests yet! [See all Quests]({onClick})
Pv8u2u - Claim by {expirationDate}
APddvF - Claim Reward
cfY4PE - Claim $[rewardWithArticle](rewardWithArticleHook)
0IUT4Y - Claim {rewardName}
W8/b3Z - Show Quest Bar
GQ+4bk - Available for {rewardDuration}
aXXBxa - Quest Completed!
ij5E/5