Fireball
The official Fireball finishing role, clearly labeled historical Demo references, and a non-numeric timing checklist for controlled Orc Incremental observations.
- Published
- Updated
- Last checked

Quick facts
- Spell
- Fireball
- Official role
- Fireball is a timed spell used to finish a fight.
- Build boundary
- version 1.0
- Evidence check
- 2026-08-28
- Unknown fields
- damage, radius, duration, cooldown, cost, unlock, upgrade tree, targeting formula, final version 1.0 balance
Treat the role as a timing question
The registry-backed answer defines the safe role boundary. The useful next question is when a cast changes a nearly completed fight under repeatable conditions. It is not an invitation to invent an ability sheet.
Choose a stable cue before the attempt. Good cues are visible events such as a boss action, a target reaching a recorded state, or the first allied defeat. “Cast near the end” is too vague for comparison because each observer may choose a different moment.
Use the spell hub comparison when the failure symptom is still unclear. Use formation diagnosis when the army cannot reach the important target even with timing held fixed.
Non-numeric timing checklist
Record these fields for both a baseline and a changed-timing attempt:
- exact named build;
- same encounter and enemy state;
- same army and arrangement;
- same progression purchases;
- visible cue chosen before the cast;
- immediate event after the cast;
- whether the intended target falls before the reversal;
- final battle result;
- another explanation that remains possible.
Repeat the baseline. Then repeat the changed timing. If either result varies without the timing change, identify that variation before attributing the difference to Fireball.
| Check | Baseline | Timing change |
|---|---|---|
| Cue occurs | Record | Record |
| Cast begins | Record | Record |
| Target state changes | Record | Record |
| First allied defeat | Record | Record |
| Fight ends | Record | Record |
The table intentionally avoids damage or time values. Add measurements only when the named build exposes a reliable measure and the observation can be reproduced.
Keep historical Demo notes historical
Demo v0.09 contains a Fireball reference inside a named Trial fix. That sentence documents a specific historical interaction and a change to it. It does not define normal healing outside that Trial, and it does not establish version 1.0 behavior.
When citing the old note, include the Demo version and Trial context in the same sentence. Do not shorten it to a general claim about Fireball. A later released-build observation needs its own evidence record.
The patch-notes index preserves dated announcements without treating them as a current changelog mirror. It is the right place to check the original context before quoting a historical fix.
Attribution mistakes to avoid
One attribution mistake is crediting the cast when another allied attack lands at the same moment. Capture the event sequence and design a smaller test if the effects overlap.
Another is assuming the visible burst defines reach or targeting. The official hero confirms the pictured effect, not the rule that selected a target or the full boundary of gameplay impact.
A third is changing army position along with cast timing. That creates two plausible causes. Keep the arrangement fixed or move the formation question into its own comparison.
Do not carry values from an unlabeled video, a remembered Demo run, or another game's spell. Missing damage, cooldown, cost, unlock, and upgrade fields remain empty here.
Write the narrow conclusion
A useful conclusion names the build, encounter, cue, and repeated result. It might say that one recorded cue produced a repeatable outcome in that case. It should not claim universal timing across bosses or progression states.
Store the observation beside the build comparison worksheet if purchases or permanent progression matter. Retest after a combat patch. Keep the old result under its original build rather than silently updating the label.
Official sourceVerified Fireball record
- Name
- Fireball
- Boundary
- version 1.0
- Verified statement
- Fireball is a timed spell used to finish a fight.
- Checked
- Still unknown
- damage, radius, duration, cooldown, cost, unlock, upgrade tree, targeting formula, final version 1.0 balance
Frequently asked questions
- What is Fireball's confirmed role?
- Fireball is a timed spell used to finish a fight. The record is bounded to version 1.0 and was checked 2026-08-28.
- Do historical Demo notes prove current Fireball values?
- No. A named Demo patch or Trial note can explain a historical interaction in that build. It does not establish current damage, healing, timing, targeting, or upgrades for version 1.0.
- What belongs in a Fireball timing record?
- Record the build, encounter, army, cast cue, cast moment, visible target state, and result. Repeat with only the timing changed so another purchase or formation change does not receive the credit.
Source ledger
- Orc Incremental official Steam store page
steam-store ·
- Demo Update v0.09
steam-announcement ·