funman300
082246c085
Recovered the client's own dialog text from memory rather than inferring from the server, which is what finally identified the subsystem: "An error occurred downloading the FUT Squad Update" is the ROSTER update, not the player's lineup. Four squad-shaped fixes before that were aimed at the wrong thing. Wire capture shows the client aborting the handshake itself: it offers TLS1.2 with RSA suites, the server selects TLS1.2 and sends its certificate, and the client replies fatal certificate_unknown. So protocol and ciphers are compatible and the certificate is the problem. That certificate is DNS-SAN-only while the advertised ROSTERUPDATE_URL is an IP literal, and it was regenerated Aug 13 -- after the Aug 12 session being used as the known-good control, which therefore says nothing about the current cert. Notably autopatch DID patch both ProtoSSL gates in the failing process (log line plus live bytes reading back patched) and the client still rejected, so those gates do not govern this path -- contradicting roster_server.py's standing comment that they make self-signed certs acceptable. Documents what was ruled out with evidence (hub route shapes, squad shape, squad round-trip, advertised hosts, TLS version, Blaze health), the probing gotcha that a default modern TLS context misreports this server as broken, the unresolved question of why production appears unaffected, and three fix options with a recommendation. No fix applied.
OpenFUT
Offline Ultimate Team — like SPT, but for FIFA 23.
OpenFUT replaces EA's retired FUT servers with a fully offline, single-player backend. You own FIFA 23 legitimately. You just want to keep playing after EA shut down the servers.
Repositories
| Repo | Purpose |
|---|---|
openfut-core |
Game-independent offline FUT backend |
openfut-bridge |
FIFA 23 integration layer + reverse-engineering proxy |
Architecture
FIFA 23 client
│
▼
┌─────────────────┐
│ openfut-bridge │ ← intercepts FUT traffic, maps routes, logs unknown
└────────┬────────┘
│
▼
┌─────────────────┐
│ openfut-core │ ← offline FUT backend: profiles, packs, squads, SBCs
└─────────────────┘
│
▼
SQLite database
Core is game-independent. It speaks a clean REST API and knows nothing about FIFA 23 internals.
Bridge is FIFA-specific. It speaks FIFA 23's wire protocol and translates it into Core API calls. Bridge is where all reverse engineering work happens.
Current Status
| Feature | Status |
|---|---|
| Local profiles + clubs | ✅ Working |
| Coin system | ✅ Working |
| Pack generator | ✅ Working |
| Card collection | ✅ Working |
| Squad builder | ✅ Working |
| Objectives engine | ✅ Working |
| SBC engine | ✅ Working |
| Match rewards | ✅ Working |
| NPC transfer market | ✅ Working |
| Statistics | ✅ Working |
| FIFA 23 integration | 🔴 Reverse engineering in progress |
| Chemistry calculation | 🟡 In progress |
| Full Draft mode | 🟡 In progress |
| Squad Battles AI generator | 🟡 In progress |
| Objectives claim flow | 🟡 In progress |
Running
# Start the offline backend
cd openfut-core
cargo run
# Start the proxy (for traffic capture / FIFA integration)
cd openfut-bridge
cargo run
Core listens on http://127.0.0.1:8080 by default.
Bridge listens on http://127.0.0.1:8443 by default.
Design Principles
- Offline-first. No EA account required. No internet connection needed.
- Single-player only. This is not a multiplayer server emulator.
- Data-driven. All cards, packs, SBCs, and objectives are JSON files. Everything is moddable.
- Clean architecture. Core has zero knowledge of FIFA 23. Bridge has zero game logic.
- No copyrighted assets. No real player images, no EA trademarks in data files.
Disclaimer
This project is not affiliated with EA Sports. You must own FIFA 23 legitimately to use this software. This project does not bypass any ownership verification and is intended only to restore offline playability of a game whose online services have been retired.