Stellar Affinity Summon Planner
Write the plan before the banner UI writes it for you.
The summon planner is a browser checklist — not a pity calculator, not an account login, not a gacha simulator. It exists because Stellar Affinity’s 29 July 2026 launch bundles newbie targeted recruit, ~200 login pulls, seven-day carnival tickets, story free six-star growth, and (for some accounts) CBT 200% star-diamond mail into the same week your brain wants to tap “ten-pull” until icons blur. Before you spend, write: target role, lane, tickets banked, gem floor, and stop condition. Data saves in localStorage on this device only.
Read summon priority and gacha & summon first. This tool holds the plan; those pages explain the reasoning.
Fields explained
| Field | What to write | Example |
|---|---|---|
| Target name / role | Carry, support, or flex from roster archetypes — not three girls at once | “Burst carry — newbie lane” |
| Lane | Newbie recruit, login campaign, event banner, carnival box, or diamond spend | “Login pull stash — hold until day 5” |
| Tickets banked | Count visible tickets + unclaimed login days you will bank | “42 tickets + 8 login days unclaimed” |
| Gem floor | Minimum star diamonds (星鑽) you refuse to drop below | “Keep 6000 after CBT mail” |
| Stop condition | Sentence that ends the session | “Stop at carry OR 60 tickets spent” |
Planner workflow
- Open tier list and pick one primary target.
- Fill the planner fields before entering the banner UI.
- Pull in deliberate batches — note each batch in the tool if you like.
- When stop condition hits, close the banner even if excitement says continue.
- Revisit after dock walls — if artifacts not conversion are the blocker, pause pulls and read artifacts & energy.
- Sync mentally with F2P plan weekly; gems are not infinite because mail felt generous once.
What this tool deliberately does not do
- No invented pity math — CBT footage reported ~0.7% SSR in one JP CBT video; live tables differ. Verify in-client; use soft pity mindset only.
- No cross-device sync — phone and PC emulators keep separate plans unless you copy notes yourself.
- No code redemption — tickets from active codes still need how to redeem; fragment mail is not a ticket code.
- No reroll automation — delete burn accounts outside this checklist (reroll).
Wrong math feels confident; a written stop condition feels boring and saves accounts.
Pairing with other launch tools
- Codes tracker — separate alphanumeric redeems from mail/login rows.
- Bond checklist — if you pulled a carry but bonded nobody, DPS will lie to you.
- Launch rewards — know which injections are mail before you count them as tickets.
Sample plans (copy and edit)
Plan A — pure F2P week one: Target burst carry via newbie recruit. Lane: newbie only until resolved. Bank all login pulls until day 4. Gem floor: 0 paid gems. Stop: carry secured + 30 tickets spent max on newbie lane.
Plan B — login stash for limited banner: Target sustain support from best teams Template B. Lane: login + carnival only; newbie already done. Gem floor: 3000. Stop: one copy OR 80 tickets consumed, whichever first.
Plan C — CBT diamond return: Target limited support that completes team. Lane: diamonds after F2P lanes exhausted. Gem floor: 50% of mailed return untouched for emergencies. Stop: one copy + artifact slot upgraded.
After you pull
Dump mats into the same target via progression. Run bond ticks on bond checklist. Push one dock from planet walkthrough to prove the pull mattered. If the pull did not move clears, fix artifacts before the next batch.
Related
Plans are cheap. Regret pulls on three banners in one evening are not.
Weekly review ritual
Every Sunday, rewrite target and stop condition if current events added a banner. Archive completed plans in your own notes if you want history — localStorage is convenience, not an archive. Compare ticket bank to beginner week or daily routine so calendar claims do not silently inflate your planner numbers.
If stop conditions fail three sessions in a row, the problem is usually not RNG — it is missing artifact conversion or bonding on the deployed carry. Fix systems before raising ticket budgets in the planner.
Frequently Asked Questions
Quick answers to the most common questions.
Does the planner calculate pity?
No. It tracks your personal plan and stop rules — verify live rates in-client.
Will my plan sync to another phone?
Not automatically. Copy fields manually or use one primary device.
Should I include mail fragments in ticket bank?
No. Fragments (碎星) are soft currency — map them on [currencies](/items/currencies/), not summon tickets.
What stop condition works best?
Combine a role goal (“carry online”) with a ticket cap (“60 spent”) so emotion cannot override math.
Where do login ~200 pulls fit?
Lane = login campaign; bank until [summon priority](/characters/summon-priority/) target is chosen.