funman300
afdbb364ca
A twelve-agent pass over the parts of pack opening we did not understand, run against
the live client (CardsDLL slide proven, not assumed) plus static CardsDLL. Findings
below survived an adversarial verification round that corrected several of them; where
a verifier and a finder disagreed, the verifier won.
THE HEADLINE IS A NEGATIVE, and it deletes work rather than creating it. There is no
pack-inventory endpoint in FIFA 17 and there never was. Proven three independent ways:
the 48-entry UTAS route template array at 0x18021df80, a regex for "ut/" over the whole
PE, and the 125-row client action table at 0x1802caa20, which is the complete set of
requests the client can originate. "Serve the pack inventory" comes off the backlog.
The unclaimed-pack tile and My Packs are two fields on responses we already build.
Corrections to ENDPOINT_MAP.md, both freeze-risky as written:
* duplicateItemIdList is an array of OBJECTS (element parser 0x180138e10: itemId
0x16d, duplicateItemId 0xeb, itemLoans 0x16f, duplicateItemLoans 0xed), not the
int list documented at :1095 and :218. Control that this is not a misread:
dreamSquads 0xe9 in FutMoveCard genuinely is a bare int array and parses with no
inner object loop. We serve [], so this is a docs bug today and a live freeze the
moment somebody implements it from the map as written.
* FutDiscardCardServerResponse is {"items":[{"id":N}],"totalCredits":N}. There is no
top-level id. :968-971 is wrong twice over.
packContentInfo is DECORATIVE. It is read only into a store-tile view model, and
nothing compares the declared counts against the delivered itemList, so open_pack()
does not have to honour the distribution.
The reveal is entirely CLIENT-SIDE. Walkout, tiering, colours and ordering are
arithmetic over fields we already send. Genuine outstanding server work reduces to
three items: duplicates, quick-sell credit, unopenedPacks.
Perishable intel captured: the real FIFA 17 retail pack catalogue, 41 SKUs with Origin
offer ids, recovered from the client heap as a parsed copy of data/store/storecfg.xml.
It is in no file on disk, only in a running process.
futmem/ is a standalone read-only Rust crate for this kind of work (maps, find,
strings, read). Read-only by construction: it opens /proc/<pid>/mem with File::open
and there is no code path in it that can write to another process, because a live game
session depends on that. Its own [workspace] table keeps it out of the parent
workspace. Chunked scanning overlaps by pattern_len-1 so a match spanning a chunk
boundary is still found.
utas_server.py gains FUT_PORT/FUT_LOG so a throwaway instance can be started without
bouncing the one the live client is using. Defaults unchanged (8099, /tmp/utas_server.log).
Noted for the record: this edit came from a research agent that had been told not to
touch server code. It is benign and useful, but it was out of scope.
Not committed: the doc proposes ENDPOINT_MAP.md changes as pasteable text rather than
applying them, and every proposed server change defaults off per the house rule.
Nothing in this commit changes a response the client sees.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
63 lines
2.3 KiB
Python
63 lines
2.3 KiB
Python
"""D4 Q3/Q4 part 2. The pack-open summary builder FUN_1800aa440 picks a headline item
|
|
and builds a display struct. Decompile everything it leans on:
|
|
|
|
0x18013fe00 shared ITEM element deserializer -> atom -> struct offset map, so we can
|
|
name the fields FUN_1800aa440 reads (+0x18, +0x38, +0x3c, +0x4c, +0x58,
|
|
+0x94, +0xb4, +0x146, +0x148)
|
|
0x1800aa330 the headline predicate (does this item qualify for the special path)
|
|
0x1800a9fe0 called with (item[0xb], item.byte@0xb4) -> stored as a display field.
|
|
Prime suspect for the animation-style / tier number.
|
|
0x1800aa060 per-top-3-item expander
|
|
0x1800a96a0 the sort over the collected (a,b,c,index) tuples <- Q4 lives here
|
|
0x1800a9b10 display-struct init
|
|
0x1800a9a10 display-struct -> event payload
|
|
callers of 0x1800aa440
|
|
|
|
CONTROL: the item deserializer must reproduce a field we already know from
|
|
docs/CARD_SYSTEM.md / ENDPOINT_MAP.md, e.g. atom 0x271 rareflag and atom 0x6c
|
|
cardsubtypeid must both appear in its atom ladder. If they do not, I have the wrong
|
|
function and the offset map is worthless.
|
|
"""
|
|
import traceback
|
|
|
|
OUT = "/tmp/claude-1000/-home-alex-Documents-OpenFUT/8e521ca1-ca3e-4138-bb96-df1744dd1d30/scratchpad/packres/"
|
|
BUF = []
|
|
|
|
|
|
def p(*a):
|
|
s = " ".join(str(x) for x in a)
|
|
print(s)
|
|
BUF.append(s)
|
|
|
|
|
|
try:
|
|
for va, nm in ((0x18013FE00, "item_deser"),
|
|
(0x1800AA330, "headline_predicate"),
|
|
(0x1800A9FE0, "style_from_item"),
|
|
(0x1800AA060, "top3_expander"),
|
|
(0x1800A96A0, "sort"),
|
|
(0x1800A9B10, "disp_init"),
|
|
(0x1800A9A10, "disp_to_event")):
|
|
src = dec(va, 300)
|
|
p("\n\n########## %s %#x len=%d ##########" % (nm, va, len(src)))
|
|
p(src)
|
|
with open(OUT + "d4_%s.txt" % nm, "w") as f:
|
|
f.write(src)
|
|
|
|
p("\n=== callers of FUN_1800aa440 (pack-open summary) ===")
|
|
for c in callers(0x1800AA440):
|
|
p(" %s" % (c,))
|
|
p("=== callers of FUN_1800a9fe0 ===")
|
|
for c in callers(0x1800A9FE0):
|
|
p(" %s" % (c,))
|
|
p("=== callers of FUN_1800aa330 ===")
|
|
for c in callers(0x1800AA330):
|
|
p(" %s" % (c,))
|
|
|
|
except Exception:
|
|
traceback.print_exc()
|
|
finally:
|
|
with open(OUT + "d4_reveal_path2.txt", "w") as f:
|
|
f.write("\n".join(BUF))
|
|
print("WROTE d4_reveal_path2.txt")
|