Download shared per-title configuration files using the Epic Online Services Title Storage interface
domain: dev.epicgames.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Initialize the EOS Platform with a 64-character hex EncryptionKey required for Title Storage
Upload the shared files through the Epic Developer Portal (Title Storage is read/query only via the SDK)
Acquire the EOS_HTitleStorage handle and query the file list or specific file metadata
Download files in chunks via the read request callbacks and reassemble on the client
Cache downloaded title files locally since they change infrequently and are shared by all players
Known gotchas
Unlike Player Data Storage, Title Storage cannot create, modify, or delete files from the SDK -- uploads only happen through the Developer Portal
Files are encrypted with the title's EncryptionKey, so a missing or wrong key silently breaks decryption
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?