Patent pending · GM-authored hidden influence
Every other VTT shows the GM and the players the same board. The Veil System gives the GM a second one — invisible to the table, and the reason your players start to feel like something's wrong before they can say why.
"Let the rogue notice the second set of footprints next, not the cleric. Keep the lie alive one more scene."
Nothing about the player-facing view changes. The Veil System runs entirely on the GM's side — no extra window for players to peek at, no shared tracker to accidentally expose.
The Veil System isn't a scripting layer or an API you build against — it's built into Threshold. GMs set hidden state through the same interface they already use to run the game, no code required.
There's no plugin to write and no logic to wire up. Every Veil mechanic is native to Threshold — you set values, the system handles the rest.
Attach hidden properties directly to a character or an item — a cursed blade with a trait only you can see, an NPC whose true loyalty isn't on their sheet.
Hidden traits can shift based on alignment — a relic that behaves differently in good hands than evil ones, an NPC whose hidden trust decays around a misaligned party.
The moment a player can see a hidden-threat marker, a trust meter, or a flagged NPC, the mystery is over — they're not afraid of what's coming, they're reading a spoiler. Most VTTs either expose everything or give the GM nothing but a notes box.
The Veil System isn't a GM remembering to keep a secret — it's a structural layer the platform enforces. Tension, trust, and hidden threads live somewhere players can't reach, by design, every session.
The Veil System's hidden-influence mechanic is currently patent pending. As far as we've found in surveying the VTT landscape, there's no direct analog to a GM-side influence layer that's structurally separated from the player view — this is Threshold's own ground to stand on.
Status: In active development — heading toward a Kickstarter launch.
Get early access