67b84abe7c7267b212902745db0c35dd4d6b8513
Matches — difficulty selector, generate opponent (shows AI squad rating and formation), quick-score buttons (3-0 / 1-1 / 0-2), submit custom score via POST /matches/result, inline reward display (coins, XP, objective triggers, season points), live match history list. Pack Store — lists all purchasable definitions from GET /packs/store (name, description, cost, card count) with one-click Buy that calls POST /packs/buy; coin balance refreshes after purchase. SBC — renders all challenges with requirements as pills (min OVR, required nations/leagues/clubs, same-club counts), card picker (select from owned collection, click pill to remove), Submit fires POST /sbc/submit and shows reward or validation failures; cards re-loaded from Core after a successful submission. Statistics — career stat grid (matches, W/D/L, win rate, goals, coin totals, streaks, packs, SBCs), goals-by-position bar chart, paginated match log with outcome badges and date, sourced from GET /statistics and GET /statistics/history. 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
Description
Languages
Rust
61.7%
HTML
38.3%