# Supported protocols and engines

> What the game profile protects — UDP game traffic, A2S query/status, RCON, and voice — and which engine presets are a Game Pro feature.
>
> Canonical: https://xdp.network/docs/openshield-xdp-game/supported-protocols · Updated 2026-08-09

The game profile protects the UDP traffic your game or voice server lives on. This
page lists what is covered and where the per-engine presets of Game Pro fit in.

## What the game profile protects

| Traffic | Protocol | What the profile does |
| --- | --- | --- |
| Game traffic | UDP | Per-player token buckets absorb floods at line rate |
| Query / status | A2S | Flood shielding that keeps server-browser listing working |
| Remote admin | RCON | Rate-limits abuse without locking out real admins |
| Voice | UDP voice traffic | The same line-rate flood mitigation as game traffic |

The base **Game** edition protects any UDP-based server with this generic tuned
profile — you do not need an engine-specific preset to be covered.

## Engine presets are a Game Pro feature

**Game Pro** adds per-engine detection profiles with presets for Source, FiveM,
Minecraft, and Rust. These match detection thresholds to each engine's normal traffic
shape, which matters when you run a public server whose patterns attackers study.
See [Game vs Game Pro](/docs/openshield-xdp-game/game-vs-game-pro) for the full
comparison.

:::note
TCP services behind the same host — game launchers, patch servers, community
websites — are not the game profile's job. Pair the agent with
[PingLess WAF](/docs/pingless-waf/overview) to protect HTTP.
:::

## Check which presets are installed

Installed presets are listed on the server itself:

```bash
openshield profile list
```

Select one with the `profile` key in `/etc/openshield/openshield.yaml`, then run
`openshield reload` to apply it.

## Next steps

- [Game vs Game Pro](/docs/openshield-xdp-game/game-vs-game-pro)
- [Attack types](/docs/attack-mitigation/attack-types)
- [PingLess WAF overview](/docs/pingless-waf/overview)