Purpose of Loadout Planning
Jumping into Final Swarm without a plan spreads Keys across random weapons and opens Chests at random times — wasting code rewards from update1 and firstswarm. Loadout planning means deciding your primary weapon, secondary coverage, Chest opening order, and target world before you queue, so every session advances the same build.
This page provides the strategic framework for planning. An interactive planner component will layer on top of these rules later on finalswarm.wiki; until then, use the checklists and links here manually.
Step 1: Account Resource Audit
List current Keys, unopened Chests by rarity, and unlocked weapons. If you have not redeemed supdoggy, firstswarm, and update1, do that first — planning around zero resources misrepresents your options.
Note quest objectives that reward Keys or require Chest opens. Align planned sessions with active quests from the quests page.
Step 2: Choose Primary and Secondary Archetypes
Primary weapon: pick one S or A tier archetype from tier-list/best-for-beginners or tier-list/best-loadouts matching your platform skill.
Secondary weapon: cover primary weakness — usually ninjas if primary is AoE, or goblins if primary is single-target. Jungle mixed spawns require both roles filled before deep farming.
Step 3: Key Spend Roadmap
Allocate Keys in three milestones: primary unlock, secondary unlock, reserve buffer for new patch weapons. Avoid tertiary unlocks until Jungle wave twelve-plus is stable.
Document spend in notes app or spreadsheet — interactive tooling here will automate this step in a future wiki update.
Step 4: Chest Opening Schedule
Wooden and Common: open before practice runs. Rare batch: before Jungle push day. Epic: one per personal best attempt. Follow guides/chest-opening-guide for nuance.
Pair openings with planned loadout archetypes — speed stats for kiting builds, damage for stationary range builds.
Step 5: World and Session Goals
Define each session: warm-up starter world, Jungle Key farm, quest completion, or weapon experiment. Mixed goals dilute results.
After five Jungle attempts with the planned loadout, compare wave records. Adjust tier choices using tier-list if progress stalls — not random new unlocks.
Interactive Planner Coming Soon
The wiki will add an interactive loadout planner component that visualizes Key budgets, Chest timelines, and tier recommendations. This informational page remains the strategy backbone — tools enhance planning but do not replace understanding enemy priorities and economy fundamentals from guides/best-loadout.
Example Plan Snapshot
Resources: 200 Keys from supdoggy and update1, three Wooden Chests from firstswarm, five Rare and one Epic from update1. Plan: unlock primary today, secondary tomorrow, open Wooden and Common before next starter run, Epic before first Jungle push, Rare batch before weekend Key farm session.
Adjust numbers to your account after redemption. The structure matters more than copying exact counts — every plan should sequence Keys, Chests, and world targets in that order.
Revising Plans After Failed Runs
If three consecutive Jungle attempts fail before wave ten, revise plan downward: return to starting world, open remaining Common Chests, verify secondary weapon unlock covers ninjas, then retry Jungle only after wave fifteen starter consistency returns.
Plans are living documents. Patch notes, new codes, or Epic Chest rolls should trigger a five-minute replan rather than abandoning structured progression entirely.
Share plans with co-op partners so everyone spends Keys on complementary weapons instead of duplicating the same unlock twice across a friend group.
Include code redemption dates in your plan header so you remember when supdoggy, firstswarm, and update1 were claimed and when to hunt new strings on the wiki codes page.
Revisit plans after reading tier-list patches notes — a single weapon re-tier can invalidate yesterday Key spend order without changing your overall world progression goal.
Save planner notes between sessions so weekly Jungle goals stay visible on your desktop or phone.