Docs
Atlas Main & retention
How atlas_rage (Atlas Main) launches coin shop, playtime shop, daily rewards, weekly quests, and family.

Why this matters
Atlas Main is the advertising face of retention: one premium hub players open, five apps they instantly understand. If visitors to your city (or this site) cannot see the loop, they will not know what Atlas is selling.
Hub resource
| Resource | Player-facing name | Role |
|---|---|---|
atlas_rage | Atlas Main | RAGE-style modular app hub (/atlasrage) |
Apps register with exports.atlas_rage:RegisterApp. Built-in KnownApps ship in atlas_rage config and open sibling resources.
Apps on the hub
| Hub card | Resource | What players get |
|---|---|---|
| Coin Shop | atlas_coinshop | Premium packages, vehicles, weapons, redeem codes |
| Playtime Shop | atlas_playtimeshop | Coins and deals earned from time in city |
| Daily Rewards | atlas_dailyrewards | Login calendar / streak claims |
| Weekly Quests | atlas_weeklyquest | Quests, milestones, leaderboard |
| Family | atlas_family | Crews, ranks, treasury, wars, family chat |


In-game UI backgrounds
Full-bleed art players see when they open each app (same assets as the live scripts):
| App | Background |
|---|---|
| Daily Rewards | ![]() |
| Weekly Quests | ![]() |
| Family | ![]() |
Start order
After core gameplay and atlas_admin:
ensure atlas_rage
ensure atlas_coinshop
ensure atlas_playtimeshop
ensure atlas_dailyrewards
ensure atlas_weeklyquest
ensure atlas_familyHub first, then apps — so cards resolve when the menu opens.
Locales
Hub and app strings live in the atlas_extras locales hub:
rage.json— Atlas Main chromecoinshop.json·playtimeshop.jsondailyrewards.json·weeklyquest.json·family.json
Staff tip
Family admin commands and quest tuning stay server-side. Do not trust client claim amounts — all grants go through Atlas money / inventory contracts.
Next: Resource catalog · Gameplay packs tour · Engagement tutorial
Atlas

