Veilbreak · incursions · tension
Read the chips, ward the wound — the Veilbreak guide
Every region carries a hidden tension value. At 0.5 the world map starts showing the wound; at 0.6 the dice for an actual incursion start rolling. Here's how to read every cue.
TL;DR
The Titan Saga: Idle Veilbreak guide in one paragraph — regions track a 0.0–1.0 tension value. A chip surfaces in the region panel at 0.4, the world-map halo lights up at 0.5, and at 0.6 the per-collection breach roll begins (5% scaling to 12% at full tension). Active incursions announce themselves through a three-surface trilogy: TopBar chip, region-panel chip, and a spawn toast. Warding doesn't stop the climb; it dims the visuals to tell you a shrine is suppressing.
What Veilbreak is, mechanically
Every region carries a hidden veil tension float between 0.0 and 1.0. Resource collection, certain quests, and the passage of in-world time push it up. Active shrines push back. When tension crosses the veiled threshold the game starts rolling for an actual incursion — a pending tear at a specific hex inside the region. Pending incursions resolve into outcomes the same way other timed encounters do.
The system has three jobs: track tension, decide when it converts into an incursion, and tell you about it through the right surfaces at the right time. Most of this guide is about reading the cues rather than gaming the math — the tension number itself isn't exposed as a raw float, only through visual ramps.
Tension thresholds and what you see at each
There are five visual stages, plus the active-incursion state. They line up with the underlying threshold constants, not with the rounded percentages the chip displays — so a region showing "Veil 59%" is in the 0.4-to-0.6 band, while "Veil 60%" has just crossed into the veiled state with a different glyph.
| Tension | Region panel chip | World-map cue |
|---|---|---|
| < 0.4 | no chip — region reads as calm | no halo, no ring |
| 0.4 – 0.6 | "Veil N%" appears in row 1 of the region panel | no halo yet — chip is the only signal |
| 0.5 – 0.6 | still "Veil N%" — chip range and halo range overlap | pre-breach hex halo lights up (subtle alpha-ramp) |
| ≥ 0.6 (veiled) | "Veil N% ◆" — elevated glyph; appends "· warded" if a shrine is active | halo brightens + dashed perimeter ring of 8 short arcs |
| ≥ 0.7 | same chip; region becomes amplifier-eligible | no extra visual; this gate is internal |
| active incursion | "Incursion N% unstable" replaces the veil chip | solid pulsing void-purple ring with danger rim |
The map-side cues only render on the world view at non-tab-switched state. Zoom in to per-plot view or switch to the routes / holdings tab and the rings disappear — they're noise outside their context.
Breach probability — the dice at 0.6
Hitting tension 0.6 doesn't open an incursion immediately. It arms the per-collection roll:
- At tension 0.6 each eligible collection has a 5% chance of converting into an incursion.
- The chance scales linearly with tension up to 12% at tension 1.0.
- Tension is per region. A 0.9 region rolling against the world and a 0.6 region rolling against the world are not the same risk pool.
The practical read: a region living at 0.6 will eventually pop, but you have time. A region at 0.85 is much more urgent — that's the difference between waiting for your next session and opening the map right now.
The surfacing trilogy — three places it tells you
A pending incursion gets surfaced through three coordinated cues so you don't miss it regardless of which screen you're sitting on.
TopBar chip
Void-purple crystal-ball icon in the persistent TopBar. Renders only when there is at least one pending incursion; hidden the rest of the time. A badge label shows the count. Tap → centered list popup → row tap deep-links into the world map and auto-opens the incursion popup.
Region chip
Row 1 of the world-map region detail panel. Reads "Veil N%", "Veil N% ◆", "Veil N% ◆ · warded", or "Incursion N% unstable" depending on state. Suppressed entirely below tension 0.4 so calm regions don't drown the row in chip soup.
Spawn toast
Notification fires once when an incursion actually spawns — "Veilbreak opened in <Region>". Squelched during catch-up after a long offline session so you don't get five at once on login. Tutorial spawn fires a separate squelch path so it doesn't double up.
The three are independent surfaces of the same underlying state. Suppressing one doesn't suppress the others — if the toast hides itself during catch-up, the TopBar chip still appears once the catch-up finishes.
Warding — what a shrine actually does
A region with an active shrine is warded. Warding does not stop tension from climbing; the float keeps moving based on the same inputs. What changes is the visual ramp and the chip:
- Halo alpha multiplied by 0.3. The pre-breach purple haze becomes much subtler — a warded 0.7-tension region looks visually quieter than an unwarded 0.5.
- Soft-cyan dot rendered at the region's center hex — the "a shrine is here" signal that distinguishes "this looks calm" from "this is actively suppressed."
- "· warded" suffix on the region chip once tension reaches the veiled threshold (0.6). Reads as "Veil 73% ◆ · warded".
Warding is consumed visually, not mechanically — you're paying for the affordance to ignore a region while still tracking it, not for immunity to incursions. The breach roll still fires at the same probability. Treat warded regions as deferred problems, not solved ones.
The mechanics of which shrines ward, how to activate one, and the cost of consecration live on the patron shrines page.
Common mistakes
- Treating 0.6 as a deadline. It's where the dice start rolling at 5% per collection. You usually have several plays to react. Don't drop everything for a 0.6 region while a 0.85 region down the coast actually needs attention.
- Assuming warded = safe. The chip says "warded" — the tension number is still climbing. A warded 0.9 will still breach; you've just made it visually less screaming.
- Mistaking "no chip" for "no tension." Tension below 0.4 hides the chip to keep row 1 clean. The float still exists; it just isn't worth a chip yet.
- Missing the on-map ring because you're zoomed in. Per-plot zoom hides incursions. If you're searching for one, zoom out to the world view first.
FAQ
What is a Veilbreak?
A region-scale tear in the world map where pending incursions can spawn. Each region tracks a tension value 0.0 to 1.0; once tension passes the veiled threshold the region becomes eligible for an incursion to open. Surfacing chips, halos, and toasts let you see it coming before it actually arrives.
At what tension does an incursion actually open?
The breach roll is gated to tension 0.6 (the veiled threshold). At 0.6 each resource collection has a 5% chance of triggering an incursion; that scales linearly up to 12% at tension 1.0. So 0.6 isn't a deadline — it's where the dice start rolling.
How does warding work?
An active shrine in the region suppresses the visual ramp — the hex halo dims to about a third of its normal alpha and a small soft-cyan dot appears at the center. Warding doesn't stop tension from climbing; it tells you the region is being actively suppressed. The chip in the region detail panel appends '· warded' once tension reaches 0.6.
Why is the TopBar chip sometimes missing?
It only renders when there's at least one pending incursion on the active-incursions list. No pending incursion, no chip — the TopBar stays clean. The chip also hides itself during catch-up after a long offline session so you don't get a barrage of stale alerts at startup.
Can I see the wound on the world map at any zoom level?
No. The incursion ring and pre-breach halo render only on the world view, not at per-plot zoom. They're also tab-gated to the default world-map tab — switching to the routes or holdings tab hides them.