FFXIV Raid Timeline Planner

Why this is a units plan, not a loot forecast

A raid timeline becomes misleading when it turns every chest into a fractional piece for every player. Different coffers serve different slots, exchange items have distinct costs, rewards may be restricted, and a party's allocation decisions matter more than a generic average. This planner therefore asks a narrower question: how many units compatible with one named target can your current plan deliver?

You supply two paths. A direct unit is a compatible award your plan expects to allocate to the target. A token unit is purchased after accumulating enough of one compatible exchange token. Both values are explicit. If there is no defensible direct allocation, use zero; the planner will rely only on the token path you entered.

Build a sourceable scenario

1. Choose one target. Name the job, slot, or exact exchange item so “compatible” has a testable meaning.
2. Record patch and tier. Current restriction and exchange text belongs with the scenario, not in an undocumented preset.
3. Count remaining target units. Exclude already completed slots and unrelated rewards.
4. Enter current compatible tokens. Never combine books, blades, or other currencies merely because each comes from a raid.
5. Verify weekly token income and item cost. Use current Lodestone or in-game exchange information.
6. Add direct units only if justified. A written static allocation can be a planning assumption, but label it as such and update it after every award.

Calculation order

First, the planner converts as many existing tokens as possible without exceeding the target. For each later weekly boundary it applies the entered direct compatible units, adds the entered compatible tokens, and makes every whole exchange possible. It stops when the target reaches zero or after 520 modeled boundaries. This order prevents three common errors: delaying a purchase already available, spending fractional tokens, and counting units after the goal is complete.

If progress is zero on both paths, the result is “unreachable” rather than an infinite date. If the projection passes 520 boundaries, the page reports that limit instead of presenting false precision. The output uses reset counts because maintenance and calendar timing are external facts.

Worked arithmetic example

The starter scenario needs six compatible units, receives one direct compatible unit per week, starts with no tokens, earns one compatible token per week, and spends four tokens for one target unit. Weeks one through three each provide one direct unit while banking tokens. At week four, one direct unit and the fourth token produce two units. Week five supplies the last direct unit. The total is five direct units plus one token unit across five weekly boundaries.

Those figures teach the calculation only. They are not current defaults for every AAC encounter, job, coffer, or exchange. Replace each field with the exact rules and allocation behind your own target.

Current official boundary

Square Enix's Patch 7.4 Notes state that AAC Heavyweight normal duties award item-specific tokens under a weekly restriction and describe the then-current Savage reward eligibility and replay rules. These are patch-specific facts, not a permanent table. The calculator leaves token income, cost, and direct allocation editable so a future tier cannot silently inherit obsolete mechanics.

What remains outside the model

The planner does not decide whether an item will appear, who wins a party roll, whether a coffer is compatible, whether a group clears, or when restrictions will be lifted. It also does not combine several people into an “average player.” Model each target separately, reconcile it after the weekly run, and use the loot priority ledger for an actual confirmed award.