Account
I was banned and I think it was wrong. How do I appeal?
Appeals are read. A ban that came from an automated signal can be wrong, and the whole
point of an appeal is to catch that.
What to send. An appeal that can actually be assessed contains:
- Your operator name, exactly as it appears in the Barracks.
- The approximate date and time you were first unable to play, and your time zone.
- The message you saw, word for word if you can.
- The build number you were on — it is on the main menu, and it looks like
2507.
- What you believe happened, in your own words.
Where to send it. Appeals currently go through the community channel, which is not
published yet — see Media & community. Until
it is live there is no working appeal route on this website, and this page is not
going to pretend otherwise by showing you a form that drops what you write.
What will not help: sending the same appeal repeatedly, or sending it from a
second account. Neither speeds anything up, and the second one is itself a violation.
Reporting
How do I report a bug?
From inside the game — press X in the menu. That opens the report
tool, and it is genuinely the best route, because it attaches the things that decide
whether a bug can be reproduced:
- your build number
- your operating system and version
- your graphics adapter
- the map you were on
- a screenshot, if you took one
The form asks for the steps to reproduce and what you expected versus what
happened. Those two boxes are worth more than everything else combined — "the stairs
on the north side of the cellar drop you through the floor if you jump onto the third
step" is a fix; "the map is broken" is not.
Categories are: map or structure issue, crash or error code, interface or menu, and
other.
A web form is not available. Submitting bug reports from this site needs a
receiving server that has not been built. When it exists, it will appear here.
Reporting
How do I report another player?
Press X in the menu and choose "Report a player". You can identify
them by operator name or by their player ID, and pick a reason: griefing, toxic behaviour,
cheating, or other.
Describe what they did and when. A report saying "cheating" with nothing else attached
cannot be actioned; "he was killing through the reinforced wall on the second floor of
Ashgrove for the whole last round" can.
Team-killing has an automatic answer too. When friendly fire is enabled, a player
who crosses the grief threshold starts taking their own fire back. You do not have to wait
for a report to be reviewed for that to bite.
Do not report players on this website. There is no form here, and there is a good
reason there is not: a public web form that accepts accusations about named players, with
no match context and no verified reporter, is a harassment tool. Reports from inside the
game carry the match they happened in.
Connection
I can’t connect to a match
Breach Protocol matches are peer-to-peer: one player in the lobby hosts the match
and everyone else connects to them directly. There is no dedicated game server between
you. That makes matches cheap to run and it makes connection problems look different from
what you may be used to.
Things worth trying, roughly in order:
- Check you are on the current build. Players on different builds cannot see each
other's matches. The build number is on the main menu.
- Try again. Direct connections between two home networks succeed on most
attempts and fail on some. A second attempt often just works.
- Try hosting instead of joining. If your connection can accept an incoming
match, hosting sidesteps the case that was failing.
- If you are behind a strict or carrier-grade NAT — common on mobile broadband
and some student or office networks — direct connections may fail consistently. This is
a known limitation of the current alpha, and the fix is on
the roadmap: relayed matches, which also remove the
address exposure described in the privacy notes.
Installing
The updater keeps asking me to update
The game checks its own version against the published one at launch and offers you the
new build when they differ.
If it asks again immediately after a successful update, the installed build did not
replace the running one. Try, in order:
- Fully close the game — not just back to the menu — and start it again.
- Check the build number on the main menu against the one in
the latest update notes. If they match, the update did
land and the prompt is stale; restarting clears it.
- If they do not match, download the build fresh rather than updating in place, and
install it to a clean folder.
A repeating update prompt was a real defect earlier in the alpha and it is guarded
against now, but a partially-written install can still produce it.
Performance
The game crashes, freezes, or runs badly
First: update your graphics drivers. It is the single most common fix, and it is
free.
If it crashes at launch or shows a black screen, your adapter may not support the
renderer the game defaults to. Settings has a quality tier that steps the renderer down;
starting at the lowest tier and working up will tell you where the limit is.
If the frame rate is poor rather than unstable, the Settings screen has a built-in
benchmark. Run it and it reports the median frame rate and the spread, plus what the scene
actually cost to draw. That is more useful than a single frame-rate number, because on the
same machine and the same scene the raw figure can vary enormously between runs.
Either way, send it in: press X in the menu and choose "Crash / error code".
Your adapter and driver come attached automatically.
Settings
Controls, keybinds and controllers
Every control in Settings does something — the ones that could not be wired to anything
were removed rather than left on screen doing nothing.
Keybinds are fully remappable, and there are preset schemes if you would rather not do it
by hand. Controllers are supported, including stick dead-zone handling; if walking and
looking fight each other, the dead-zone setting is where to look first.
In the menus: X opens the report tool, C opens the social hub,
and Tab opens the scoreboard during a match. In a lobby with the chat box
focused, those keys type instead — click out of chat first.
Account
Where are my career stats?
In the game, in the Barracks: level, rank, match record, weapon progress, camos,
emblems, calling cards and dog tags.
There is no career lookup on this website, and that is a deliberate decision
rather than a missing feature. The reasoning is written out in
full, including what a public lookup would expose and what the safe versions of it
look like.
Progression is stored with your local profile in this alpha. Reinstalling to a clean
folder without keeping your profile will lose it.
Alpha
How do I get into the alpha?
Breach Protocol is in a closed alpha. Builds are distributed to playtesters directly, and
once you have one the in-game updater keeps you current — you do not need to come back
here for each build.
The alpha page explains what you get, what is unfinished, and
how sign-up will work once the community channel exists.
Game
A map I used to play has disappeared
It is probably vaulted. Fifteen of the thirty built maps are in rotation right now; the
rest are held back until they pass their structural checks — every room reachable from
every spawn, no floor sealed off, no objective in a place a round cannot get to.
Vaulted maps come back rebuilt rather than patched, and several already have.
The map page lists all thirty and their status.
Outbreak
Why does Outbreak keep giving me the same maps?
Because the dedicated Outbreak maps — the ones built only for the horde — are currently
all in the vault while they are rebuilt. What is left in the matchmade rotation is the
dual-mode maps, which author a real horde layout alongside their bomb sites.
Custom lobbies still reach every Outbreak map the game has, which is the fastest route to
one you miss.