funman300
b8e766e9dd
- shaper.rs: shape_response() dispatches on core_path to wrap Core JSON in FUT envelope format; shapes auth (/ut/auth → sid/pid/ phishingToken/persona envelope), profile, club, squad, market, packs; unknown paths pass through unchanged - proxy.rs: calls shape_response() on every successful Core response before returning to the FIFA 23 client - mapper.rs: expanded from 6 to 18 speculative FUT endpoint mappings covering auth, profile/settings, club/usermassinfo, item/collection, squad (GET+PUT), packs+purchase, transfer market+watchlist+bid, objectives, events, squad battles, and match result submission - admin.rs: GET /_bridge/captures/diff?a=<id>&b=<id> compares two captures; reports method/path/status changes, header diffs, and structured JSON body diffs (key-level for objects, length for others) - main.rs: registers /_bridge/captures/diff route - Unit tests: 4 shaper tests, 6 mapper tests (10 total, all passing) - All 13 integration tests still passing Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
OpenFUT Bridge
FIFA 23 integration layer and reverse-engineering proxy.
OpenFUT Bridge sits between the FIFA 23 client and the internet. It intercepts all FUT API traffic, logs every request, and routes known endpoints to OpenFUT Core. Unknown endpoints receive safe placeholder responses so the client keeps running.
What it does
- Transparent HTTP proxy — point FIFA 23 here instead of EA's servers
- Logs every request (method, path, headers, body, timestamp) to
captures/ - Maps known FUT endpoints to OpenFUT Core API calls
- Returns placeholder JSON for unknown endpoints (prevents client crashes)
- Admin API for reviewing captures and identifying unmapped routes
- Foundation for building the full FIFA 23 integration
Architecture
FIFA 23 client
│
▼
OpenFUT Bridge (port 8443)
│
├── Known route → OpenFUT Core (port 8080)
└── Unknown route → Placeholder JSON + saved to captures/
Quick Start
# Run Core first
cd ../openfut-core && cargo run
# Run Bridge
cargo run
# Or with config
CORE_URL=http://127.0.0.1:8080 BRIDGE_LISTEN_ADDR=127.0.0.1:8443 cargo run
Environment Variables
| Variable | Default | Description |
|---|---|---|
BRIDGE_LISTEN_ADDR |
127.0.0.1:8443 |
Bridge listen address |
CORE_URL |
http://127.0.0.1:8080 |
OpenFUT Core URL |
CAPTURES_DIR |
captures |
Where to save captured requests |
PLACEHOLDER_MODE |
true |
Return 200 for unknown endpoints |
Admin API
| Method | Path | Description |
|---|---|---|
GET |
/_bridge/health |
Bridge status |
GET |
/_bridge/captures |
All captured requests |
GET |
/_bridge/unknown |
Unknown endpoints only |
Reverse Engineering Workflow
- Point FIFA 23 at the Bridge (see
docs/setup-notes.mdfor proxy setup) - Start a game session
- Check
captures/or/_bridge/unknownfor new endpoints - Document the endpoint in
docs/endpoint-map.md - Add a mapping in
src/mapper.rs - Implement the Core handler
Proxy Setup (Research Notes)
See docs/setup-notes.md for notes on:
- Windows
hostsfile redirection - RPCS3 network config (PS3)
- Certificate bypass approaches
- mitmproxy integration
Development
cargo fmt
cargo clippy -- -D warnings
cargo test
License
MIT