Five Nights TD 2 enchantments—sometimes called traits by players and older guides—modify a unit after acquisition. Current community pages discuss damage, cooldown or speed, range, economy, experience, boss-focused, and rarer special effects. Names, percentages, probabilities, costs, and available rolls can change, so the live enchanting panel is the source for your decision.
Enchant only a unit that already has a stable role in the active team. A rare roll on the wrong unit can be less useful than a common effect that improves what the unit actually does.
Match the effect to the role
Main damage
Compare current damage, cooldown, range, target coverage, and passive scaling.
Choose by: the field that limits real mode performance.
Boss damage
Read any boss-specific effect and verify target eligibility in the current mode.
Choose by: boss time under equal conditions, not the label alone.
Support and control
Check whether range or cooldown changes the passive, radius, active ability, or only personal attacks.
Choose by: team outcome and effect uptime.
Economy
Verify whether an economy enchant changes placement, upgrades, income, or another field.
Choose by: payback wave and final cash advantage.
Read the enchanting screen
Select the exact unit and confirm normal or Shiny state, evolution, skin or form, level, current enchantment, and lock status. Read the reroll cost and currency. Open the full current list of possible effects and probabilities when available.
Check whether rerolling replaces the current effect immediately, whether a confirmation or keep-old option exists, and whether special items protect or guarantee a result. Do not assume the interface works like the first game or a previous season.
Write the target effect and spending cap before pressing reroll. If the current enchantment is already useful, record it. A session without a better roll must not continue past the resources needed for evolution, summons, or ordinary upgrades.
Test the unit before rerolling
Run a familiar stage with the current enchantment. Record placement and upgrade spend, clear time or wave, boss time, leaks, support coverage, and the unit’s role. Identify the limiting field.
If the unit misses enemies because of placement geometry, range may help only if the passive or attack uses that range. If the unit attacks slowly, cooldown can help but may interact with animations or a cap. If damage is sufficient but setup is unaffordable, another effect may be more useful.
For support, inspect whether the enchantment changes the team effect. A range stat can increase attack range without increasing a buff radius unless the current card says otherwise. Test status icons and teammate results.
Set a reroll budget
Choose a currency amount you can lose without blocking the next guaranteed goal. Divide the budget into small checkpoints. Stop to inspect every meaningful result rather than clicking through unfamiliar names.
Do not chase because previous rolls failed. Random outcomes do not owe the account a rare result. Published probability tables can become stale; use the current panel and treat every roll as consuming the displayed cost.
Keep a fallback rule. Stop on a good role-matched effect even if it is not the rarest possible result. Resume later after the unit remains useful and the resource reserve is rebuilt.
Compare common effect families
Damage improves the base output when the unit already connects reliably. Cooldown or speed can increase attack frequency, but inspect caps, animation cycles, summons, and passive timers. Range can improve coverage and placement flexibility, but extra range can also change targeting in ways that need observation.
Economy effects should be measured by total cash and payback, not only a tooltip percentage. Experience effects help leveling but may not improve a finished combat unit. Boss-focused effects belong on a unit used against eligible bosses, not an ordinary Story opener.
Special effects can combine several benefits or alter a mechanic. Read every line. Do not infer that a rare name is globally best, and do not copy a recommendation from a different unit whose passive scales with another field.
Evolution and trading checks
Before evolving, confirm whether the enchantment transfers, resets, or can be previewed on the output. A current public guide reports inheritance, but the live recipe and confirmation must decide. Do not spend heavily on the base form when the evolution behavior is unclear.
Before trading, inspect the exact enchantment in both panels and compare its market premium separately from the unit’s base value. A desirable roll can improve demand, but community estimates are not official or permanent. Never send a unit away for external “enchant verification.”
Use the evolution guide and trading guide for those workflows.
Troubleshoot enchanting
If the unit is missing, clear filters and check lock, team, trade, evolution, or eligibility states. If the button does not work, confirm currency and let data load. Rejoin a fresh server after an update before repeating.
If an effect appears not to work, compare equal upgrades on the same stage, remove changing supports, and inspect whether the field affects attacks, passives, summons, buffs, or economy. Record the current description and result.
If currency leaves without a recorded result, stop rerolling, capture before and after screens, and contact creator-owned support. Do not use scripts or third-party reroll services.
Current confidence
Enchantments, Souls-related reroll decisions, role-specific effects, and the traits alias are community corroborated. Exact names, effects, probabilities, costs, caps, locks, protection items, inheritance, and premiums need current-client verification. This guide was checked September 1, 2026.
Continue with Best Support Units and Best DPS Units to define the role before spending.