Daily & Weekly Loop Guide: Reset Cadence, Missions, and Weekly Caps
The loop is the engine of steady progress. Learn which missions repeat daily, which activities reset weekly, and how to schedule the week without burning out.
Current Orbis version

The daily missions are a fixed rotation
The current daily mission list repeats a fixed set: log in, cook, level a hero, level Karma, upgrade equipment, and use a Key of Light. Each mission has a small countable target, and together they form the steady income that feeds the growth systems. The progress database /progress shows the current list, and because the list is fixed, the daily loop can be trained as a routine rather than improvised. The loop is designed to take minutes, and the value compounds across a week.
The daily missions double as an achievement engine: logging in, cooking, and leveling feed the life and growth achievement categories, so the loop finishes trophies as a side effect. The progress database /progress shows both sides, which makes the routine worth more than its direct rewards.
The weekly activities are the power lever
Beyond the dailies, the activity list adds the weekly content: Currency Dungeons, Normal Dungeons, the Trait Dungeon, the World Boss, Hunts, and Raids. The World Boss and the Raids carry their own cadence and reward rules, and the current Raid data shows a shared weekly reward limit across the Raids. That limit makes the weekly schedule a portfolio decision: which activity gets the limited claims, and which rewards the ledger needs. The progress database /progress shows the list, and the boss database /bosses shows the encounters and pools.
The weekly reset is when the limits and rewards renew, so the practical habit is to spend the limited claims before the reset and to start the new week with the ledger re-read. The exact reset clock is an in-game check, because the community reports differ by region and the catalog does not publish a clock.
Build the week as a portfolio, not a grind
A sustainable loop is scheduled by goal: the daily missions run every day in a few minutes; the weekly activities are placed on the days they feed the ledger; the Raid claims are spent on the encounters whose rewards match the current shortage; the Tower climb is scheduled when the team is fresh. The material planner /material-planner is the schedule's source of truth, because it shows which shortages the week should fix.
The burnout pattern is the opposite: running every activity every day regardless of the ledger. The progress database /progress makes the limits visible, and the material planner /material-planner makes the goals visible, so the week can be planned with both in view. When two activities compete for the same session, the one that feeds the current milestone wins.
Fold achievements and completion into the loop
The loop and the completion systems overlap by design. The daily missions feed the growth and life achievements; the weekly activities feed the challenge achievements; the Adventure Book and Familiars feed the collection side. Running the loop with the progress database /progress open means every session completes something beyond its direct rewards. The Adventure Book /adventure-book and and Familiar database /familiars cover the collection categories, and the cover the collection categories, and the Orbis map /map covers the exploration categories.
The weekly review is the closing habit: check the achievements that finished themselves, re-read the activity list, update the ledger, and write the next week's schedule. The review takes minutes and keeps the loop honest.
Re-read the loop after every patch
The daily and weekly lists change with patches, and the catalog is the source of truth for what exists today. After an update, re-read the progress database /progress before planning the week, because a changed activity or a new limit moves the portfolio. The same re-read keeps the community's "best daily route" advice honest: it is only valid while it matches the current list.
Build a rest day into the loop on purpose. The daily missions repeat every day, and the weekly activities renew every week, so a scheduled light day—log in, cook, claim the dailies, and stop—protects the habit from burnout without losing the compound value. The progress database /progress shows what the light day still covers, and the material planner /material-planner shows that the standing supply chain survives a day off. A loop that survives a year beats a loop that burns out in a month.