Veilbreakers: Daemon Protocol

What it is

The city looks normal until the lights flicker. Investigate hidden possession, raise the ward, read the rite, save the host, and destroy the daemon that tears free — a server-authoritative co-op loop where the outcome is decided by the server and every case leaves a receipt on the MDT. Carries a configurable lexicon (Sacred Rite / Containment / Old Ways) that names no real faith. v1 is one daemon, one scene. Designed for Qbox, QBCore, and ESX Legacy through ForgeCore. In development · not yet released · not for sale; no runtime proof published — pending Shadow bench.

The problem it exists for

Most FiveM event content is a job with a timer on it. Players run it once for the novelty, twice for the payout, and then never again — because nothing about it was a story, and nothing about it was worth clipping. The thing that actually recruits for a server is a moment someone posts, and almost no purchasable content is built to produce one.

Why we're building it

We're building the event we'd want to walk into: an investigation that turns into a confrontation, with enough staging that the crew who survives it tells the story afterward. Cinematic co-op RP is judged on whether the moment lands, not on a feature count — which makes it the hardest thing on our roadmap to fake and the easiest to evaluate honestly.

What it's designed to do

Design intent, not shipped behaviour — none of this has been built yet.

• Designed as investigation first: hidden possession that has to be found before it can be confronted.
• Designed for co-op PvE — the crew, the rite, the shield, and something that tears free and has to be fought.
• Designed around corruption zones and boss events rather than a repeating job loop with a cooldown.
• Designed so the interesting part is the scene, not the payout — an event that pays well but plays flat has failed at the only thing it was for.

What is not proven

The section every product page should have and almost none do.

• It is not released and cannot be bought. Everything above is design intent, not a demonstration.
• No runtime proof published — pending Shadow bench. Nobody outside the studio has watched this run, and an event is judged on how it plays, which makes that the gap that matters most here.
• No performance figure exists — [MEASURED-PENDING]. Event content with heavy VFX is exactly the category where that number matters most, and we don't have it yet.
• The $39.99 intro / $44.99 standard figures are planned targets, not commitments.
• We have not published a release date. Marketing a supernatural event with a fake date would be an unusually stupid way to start.

What we're building toward

Streetlights stutter down a normal block — the ward flares, the rite lands, and the daemon tears free of its host as the whole crew turns to fight.

Current status, stated exactly

• authored slice — no runtime proof published, pending Shadow bench (studio-stated 2026-07-15)
• co-op PvE · v1 = one daemon, one scene
• resmon [measured-pending]
• framework support — decided at build, published at release
• open-vs-escrowed manifest — published at release, file by file

What to verify before buying any event resource

This applies to every product in this category, ours included, whenever it arrives. Hold Veilbreakers: Daemon Protocol to exactly these when it launches — and if it fails one of them, don't buy it.

• Ask to watch unedited footage of the whole event, not a trailer cut. Trailers hide pacing, and pacing is the entire product.
• Ask for the resmon figure during the event, not at idle. Effects-heavy content is where frame budgets die.
• Ask what happens on the second and tenth run. Novelty is not replay value.
• Ask what it requires from your framework and inventory, because event content tends to reach into everything.

Universally: ask for the measured resmon figure with its method and date, the exact list of which files ship open versus escrowed, a dated changelog, and the refund window. Four answers. Any of them missing is an answer too.