All Star Tower Defense orbs are equippable unit modifiers. Community documentation describes an Orbs control in the inventory flow, one orb assignment per unit slot, generic and unit-specific orbs, material farming, crafting through the Orb Shop, and some trial-related orb rewards. Exact recipes and effects can change, so use those descriptions to find the system and let the current menu supply the values.
Find and equip an orb
Open the unit or inventory interface and locate the current Orbs control. Select the exact unit form you want to modify, then inspect the compatible orb choices. If the interface rejects the assignment, do not assume a bug; the orb may be unit-specific, the form may be ineligible, or another requirement may be missing.
Before equipping, record the unit’s level, upgrade stats, leader status, and existing orb. Equip one orb and inspect the same fields again. Run one controlled stage if the effect changes behavior that is not obvious in the panel.
Generic and unit-specific choices
A generic orb can be evaluated across several candidates, while a unit-specific orb should be matched to the exact supported form. Similar names are not enough. Confirm the inventory selection and the orb’s current description.
Judge the effect by role. An opener benefits from a change that improves early cost or immediate coverage. A main damage unit benefits from output or range that affects its actual route. A support may benefit from ability behavior or coverage even if ordinary damage barely changes.
Do not copy an “optimal orb” recommendation without its mode. A Story unit may need an early breakpoint; an Infinite carry may value maximum scaling. Compare the unit both with no orb and with the candidate orb under identical conditions.
Materials and crafting
Community references place material farming under the Infinite/Trials area and describe enemies dropping materials used at the Orb Shop. Treat the entrance name, level requirement, drop pool, and quantities as fields to confirm in your server. The live crafting panel should show the exact recipe.
Read the recipe first
Select the desired orb at the current Orb Shop and record every material, quantity, currency, and prerequisite before starting a farm.
Confirm the drop
Enter the displayed material activity, defeat enemies, and record what appears in the result or inventory. One drop proves possibility, not a stable rate.
Measure the run
Track time, success, materials obtained, attention required, and any entry cost. Compare several runs rather than projecting from one lucky result.
Protect the reserve
Keep materials assigned to a planned evolution separate until you confirm that orb crafting will not block the higher-priority target.
Some trials have historically awarded orbs directly. Check the current trial reward panel and distinguish first-clear from repeatable rewards before calling it an orb farm.
Test the orb’s real value
Use the Unit Stats baseline. Keep unit level, upgrade, leader, buffs, map, and placement stable. Record visible damage, SPA, range, cost, ability text, and the controlled wave result before and after equipping.
If the orb affects several fields, do not reduce it to one percentage. A range increase can create more contact time; an attack-interval change can alter timing; a unit-specific effect may unlock behavior not captured by a basic formula. Describe the observed result.
If the interface rounds values, retain the displayed precision. If the effect does not appear, rejoin once and verify the orb is equipped to the exact loadout copy. Avoid repeatedly crafting or replacing until the test is clear.
Decide whether to craft now
Craft when the orb improves a unit you actively use and the materials are not required for a more urgent evolution. Wait when compatibility is unclear, the recipe appears tied to an ending event, or the target unit may soon be replaced.
Compare opportunity cost. The same play time might produce Gems, Stardust, unit experience, evolution materials, or Story progress. An orb is valuable when it removes a real failure condition, not simply because a recipe is available.
For an opener, ask whether it reduces the cash or upgrades needed to stabilize. For Infinite, ask whether it improves finished placement efficiency or support synergy. For a boss specialist, compare boss health and route distance at the same ability timing.
Avoid common mistakes
Do not assume an old recipe remains current. Do not use an ASTD X orb page for the original game. Do not compare an orb-equipped screenshot with an unmodified unit at another level. Do not consume reserved evolution materials without checking Materials.
Lock valuable units before changing inventory. Record which loadout copy holds the orb, especially when you own duplicates. If unequipping or transferring has a cost in the live menu, read that prompt before confirming.
Keep an orb record
Store orb name, compatibility, effect text, recipe, material sources, crafting date, equipped unit, test baseline, observed result, and check date. Label each field live verified, community reported, or unknown. This makes later update checks quick and prevents a historical recipe from becoming a current claim.
Continue to Items for inventory planning, Materials for farming records, or Tier List to decide which owned unit deserves the limited orb.