8087564df1b5a917f95a04ccd37e9622ff2616a8
Card Catalog — full card database browser using GET /cards with client- side filters (name, position, rarity, nation, league, club, OVR range), pagination in 80-card chunks, "Owned" green overlay/badge for cards already in the collection (cross-referenced via GET /collection). Settings/Profile — profile card with username, level, XP progress bar; editable game settings (default match difficulty, preferred formation) via GET/PUT /settings; confirmation flash on save. Squad Builder — Squad tab gains a Build/View toggle. Build mode shows 11 starter slots (labelled by position for the selected formation) plus 7 bench slots; clicking any slot opens an inline search-picker filtered to unused collection cards; GK slot highlighted; filled slots show player name, OVR, and position with a one-click clear button; Save Squad POSTs the full squad to Core (validates 11 starters required) then switches back to View mode and refreshes the chemistry display. Formations supported: 4-4-2, 4-3-3, 4-2-3-1, 4-1-2-1-2, 3-5-2, 5-3-2. 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%