Five Nights TD 2 Summoning is a major way to obtain units, but the safe first action is reading the live banner. Community documentation describes normal or season-style pulls, a Souls banner, rarity probabilities, pity, rotation controls, and auto-sell selections. Exact names, odds, pity thresholds, currencies, and featured units are update-sensitive.
Do not copy an old pity number into your plan. Record what the current screen shows, decide which team role you need, set a budget, and stop when the banner no longer improves that goal.
Read the banner from top to bottom
Identify the banner name and currency first. Check the featured or obtainable units, every displayed rarity probability, single and multi-pull prices, remaining rotation time, pity counters, guarantees, and whether different pull buttons advance the same counter.
Open each featured unit card. Read role, attack type, element, placement cost, upgrades, passives, forms, and acquisition notes. A rare banner unit may still be too expensive for your current Story route. Compare the unit with the actual roster gap rather than the animation.
Look for the current controls that switch banners or currencies. Community pages describe coin or season and Soul-related choices, including access to some older units. Do not assume the current pool or exclusions match a previous season.
Set auto-sell safely
Before the first pull, inspect every auto-sell or auto-delete selection. Understand whether a checkmark means keep or sell. Read the full rarity and unit labels, including any Shiny exception. Test with the lowest-risk pull when the interface is unfamiliar.
Keep units needed for the active team, Hero quests, evolution, crafting, collection milestones, events, or trading. A duplicate is not automatically useless. Lock important copies immediately after the pull when the inventory supports it.
Recheck settings after changing banners and after updates. A new rarity, unit, or saved preference can alter what the next multi-pull does. If the UI is unclear on mobile, increase interface scale or use a larger display before spending.
Understand pity without guessing
Pity is only actionable when the current interface states the counter, target rarity, guarantee condition, and whether the value carries between banners or currencies. Record the starting counter and take one test pull. Confirm how much it advances.
Ask whether a featured unit is guaranteed, whether pity grants any unit in a rarity, whether the counter resets on an early hit, and whether rotation changes preserve progress. If the screen does not answer, stop before committing a long budget and seek a current creator-owned explanation or direct test.
Public community pages publish exact thresholds, but those values can become stale. Use them to know which fields to inspect, not as substitutes for the live counter.
Choose a pulling goal
Name the missing role: affordable starter, area damage, boss damage, control, support, economy, evolution ingredient, Hero prerequisite, or collection target. Compare the featured pool with that role. If the banner cannot solve it, saving is a valid action.
Set three stopping rules: a currency floor you will not cross, a target result that ends the session, and a pity condition that changes the plan. Do not chase a unit because several pulls have already failed; spent currency does not make the next pull affordable.
For a new account, broad roster improvement can be more useful than one remote top rarity. A reliable starter and reachable carry progress Story and create more farming options. Use Best Starter Units and Units before selecting a target.
Compare banner currencies
Treat every currency as a separate budget until the current UI proves otherwise. Check where it comes from, what else spends it, and whether an event or shop also needs it. Souls may be relevant to summoning, enchantments, values, or other systems depending on current implementation, so read the exact icon and label.
Do not convert Robux into pulls through an external site or player. Legitimate purchases use Roblox’s own confirmation. Compare the real price, the absence of a guaranteed target, and the account role before buying.
If a boost affects luck or pulls, read duration, activation, stacking, and whether it applies to the chosen banner. Activate it only when you can complete the planned pulls. A code or item description from an old season is not proof of the current effect.
After the summon
Confirm every acquired unit in inventory and make sure auto-sell behaved as intended. Lock useful copies. Read the current card before feeding experience, rerolling enchantments, evolving, trading, or opening more pulls.
Test a candidate on a familiar Story night at low investment. Compare placement timing, attack shape, first upgrades, passive activation, and the team problem it solves. Rarity alone does not prove a unit is better than the built copy it would replace.
Update your pity record from the live screen. If the banner rotated, capture the new pool and counter state before another pull. Stop when the budget or target rule says to stop.
Summoning problems
If the pull button does not respond, let account data load, close other panels, check currency, and rejoin a fresh server once. Do not repeatedly click during lag. If currency leaves without a visible result, capture the before and after screens and contact creator-owned support.
If a unit appears missing, clear filters, search exact spelling, check new or recent inventory, and confirm it was not auto-sold. If pity behaves differently from a guide, use the live banner and record the current rule.
Current confidence
Multiple banners, visible probabilities, pity, and auto-sell controls are documented by the community. The current banner names, pools, odds, thresholds, carryover, rotation, currencies, boosts, and exclusions must be checked in the client. This guide was reviewed September 1, 2026.
Continue with the beginner guide, evolution guide, and enchantments guide after obtaining a unit.