# V2 EOS SDK Integration

Phase 72 task 72.21.1.3 is implemented by the
[EOS SDK integration contract](../../ue/Content/V2/Online/EosSdkIntegration_V2_Contract.json)
and the `V2OnlineServices` EOS API surface. The `V2EosSdkBridge` covers
achievements friends presence matchmaking voice and anti-cheat operations for
the Epic Online Services provider while keeping EOS headers outside gameplay
modules.

## Feature Coverage

| Feature      | EOS interface                         | Required calls                                                                                                                     |
| ------------ | ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| Achievements | `EOS_Achievements`                    | `QueryPlayerAchievements`, `UnlockAchievements`, `CopyPlayerAchievementByIndex`                                                    |
| Friends      | `EOS_Friends`                         | `QueryFriends`, `GetFriendsCount`, `GetFriendAtIndex`, `GetStatus`                                                                 |
| Presence     | `EOS_Presence`                        | `SetPresence`, `QueryPresence`, `CopyPresence`, `EOS_PresenceModification_SetData`                                                 |
| Matchmaking  | `EOS_Lobby` and `EOS_Sessions`        | `CreateLobby`, `JoinLobby`, `EOS_LobbySearch_Find`, `SetMetadata`, `CreateSessionModification`, `UpdateSession`                    |
| Voice        | `EOS_RTC` and `EOS_RTCAudio`          | `JoinRoom`, `LeaveRoom`, `UpdateSending`, `UpdateReceiving`, `AddNotifyAudioBeforeSend`                                            |
| Anti-cheat   | `EOS_AntiCheatClient` and server APIs | `BeginSession`, `EndSession`, `AddNotifyMessageToServer`, `EOS_AntiCheatServer_BeginSession`, `EOS_AntiCheatServer_RegisterClient` |

## Guard Rails

The default config records ProductId, SandboxId, and DeploymentId placeholders
for local planning. Shipping secrets are supplied outside this contract. EOS is
treated as the free cross-engine SDK path and must route through the platform
SDK abstraction.

Epic Account Services must be linked and EOS Connect login must be active before
plans are ready for the native bridge. Presence payloads are sanitized, lobby
metadata is validated, RTC voice requires explicit consent, and anti-cheat
session plans require client/server integrity readiness.

## Verification

Run the focused gate with:

```bash
python3 V2/ue/Tools/check-v2-eos-sdk-integration.py
```

The checker validates the contract, C++ source declarations, automation spec,
CI/Horde wiring, this document, and the Phase 72 TODO evidence.