funman300
44fcf24d92
Evidence (resourceId 169193): its 4 owned copies are IDENTICAL in asset/rating/ position/all attributes and differ ONLY in nation/team/league (and those resolve inconsistently, e.g. team 240 'Atletico Madrid' under league 16 'Ligue 1'). A player's club affiliation is an instance-time snapshot, not part of the card DEFINITION identity. Correct the model (not a special-case): the definition-consistency gate now compares a DefIdentity projection (asset_id/version/rating/position/attrs/ rareflag) and EXCLUDES nation/league/team. A club-only difference between copies of one resourceId is no longer a conflict; a real identity disagreement (rating/position/attrs/asset) still trips it. The definition's display nation/league/club use the first-observed copy (deterministic; display-only, never identity). No --defer-conflict allowlist entry is needed for 169193 now. On the real profile: conflicts 1->0, 169193 reclassified conflict->NoName (still deferred, unnameable), supported still 1681, deferred instances still 13, BLOCKERS none without any --defer-conflict flag. 2 new tests (club-only diff is not a conflict; rating diff still is). crate suite 25 green; clippy -D clean.
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.