pixachux
eae24f1c34
Source, config, and docs only — UE template assets stay local to save storage. Co-authored-by: Cursor <cursoragent@cursor.com>
31 lines
1.1 KiB
Markdown
31 lines
1.1 KiB
Markdown
# Crossplay (Epic Online Services)
|
|
|
|
VocationLife ships with an EOS integration layer that is **disabled by default**.
|
|
|
|
## Enable EOS
|
|
|
|
1. Open `VocationLife.uproject` and enable the **OnlineSubsystemEOS** plugin.
|
|
2. Set credentials in [`Config/DefaultGame.ini`](../Config/DefaultGame.ini):
|
|
|
|
```ini
|
|
[/Script/VocationLife.VocationEOS]
|
|
bEOSEnabled=true
|
|
ProductId=YOUR_PRODUCT_ID
|
|
SandboxId=YOUR_SANDBOX_ID
|
|
DeploymentId=YOUR_DEPLOYMENT_ID
|
|
```
|
|
|
|
3. Configure the EOS plugin settings in `Config/DefaultEngine.ini` per Epic documentation.
|
|
4. Call `InitializeEOS()` on `UVocationEOSSubsystem` from your menu flow once UI is ready.
|
|
|
|
## Console ports
|
|
|
|
Console builds require platform SDKs and certification. Recommended order:
|
|
|
|
1. Stabilize PC multiplayer (listen + dedicated)
|
|
2. Enable EOS for PC crossplay
|
|
3. Add PlayStation / Xbox targets with platform-specific Online Subsystem modules
|
|
4. Use separate scalability profiles (no hardware RT on consoles)
|
|
|
|
The `UVocationSessionSubsystem` can be extended to route session creation through EOS when `UVocationEOSSubsystem::IsEOSEnabled()` returns true.
|