funman300 0138a39f3e LSX gate: FIFA reaches "connecting to EA Servers" via bridge
Implement the LSX (EA App bootstrap, TCP :3216→:3217) server in the bridge
and clear the loading-screen crash gate. FIFA 23 now completes the full LSX
handshake + session against OpenFUT and advances to the online/Blaze phase
("<persona> is connecting to the EA Servers…") — verified live, not a cached
session (the displayed persona "fun" comes from our GetProfile).

Root cause of the invariant loading-screen crash: get_config() omitted the
PROGRESSIVE_INSTALLATION and PROGRESSIVE_INSTALLATION_EVENT services (Name="PI").
FIFA builds its service registry from GetConfig and resolves that handle during
online-init; the missing service left a null handle it dereferenced at
FIFA23.exe+0x133dfc5 (mov rax,[r13+0x18], r13=NULL) ~2s after LSX — identical
across every prior run. Found via FIFA's own CrashReport_*.json (stable RIP) +
diffing anadius64.dll's service-registration table against ours.

Also in this change:
- process_frame(): handle FIFA's pipelined (batched) LSX messages per read,
  eliminating the ~15s handshake hang.
- Real anadius values (RE'd from anadius64.dll + anadius.cfg): PersonaId/UserId/
  persona, locale list, GetGameInfo fixed `GameInfo="<value>"` attribute,
  GetAllGameInfo 14-attr schema, GetSetting `Setting=` attribute.
- IsProgressiveInstallationAvailable served from sender="PI".
- docs/connection-gate-findings.md: full RE trail; relocate stale openfut-hook
  copy under docs/ (canonical hook lives in openfut-launcher).

Next gate: Blaze/online (M2), ridden over ProtoSSL in-process.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-02 15:37:33 -07:00
2026-06-25 15:09:47 -07:00
2026-06-25 15:09:47 -07:00

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

  1. Point FIFA 23 at the Bridge (see docs/setup-notes.md for proxy setup)
  2. Start a game session
  3. Check captures/ or /_bridge/unknown for new endpoints
  4. Document the endpoint in docs/endpoint-map.md
  5. Add a mapping in src/mapper.rs
  6. Implement the Core handler

Proxy Setup (Research Notes)

See docs/setup-notes.md for notes on:

  • Windows hosts file redirection
  • RPCS3 network config (PS3)
  • Certificate bypass approaches
  • mitmproxy integration

Development

cargo fmt
cargo clippy -- -D warnings
cargo test

License

MIT

S
Description
FIFA 23 integration layer and reverse-engineering proxy
Readme 1.1 MiB
Languages
Rust 61.7%
HTML 38.3%