funman300
897259c8fb
ENDPOINT_MAP said this class reads one key, `configs`, and that was true and useless. What it missed is what happens after each element closes: the client feeds the STRING VALUE of `type` back through the atom hasher and switches on the result, 42 arms wide. A flag is a row, not a key, and the client hashes our string itself. Followed it to the end. FUN_18011dc50 is the only writer of the IS_* UI gate bytes inside FutDataManagerImpl, every line is `byte = (field == 1)`, and the constructor never touches those bytes. So a flag nobody sends is a gate nobody opens. friendlySeasonsEnabled and enableDraftMode have never been sent by anything, which is a mechanism for Seasons refusing while making zero requests to any of the four servers. The store is the control that makes this readable: IS_STORE_ENABLED is the same kind of byte and its screen works, because storeEnabled and friends already ship through the Blaze config store. That list has no seasons or draft flag. Ship the gates behind FUT_SETTINGS (off/keep/gates, default gates), and re-assert the working store flags in the same array on purpose: once a populated array makes the applier run, it writes EVERY gate byte, so omitting them could switch off a screen that works today. maximumTradePileSize=100 rides along as a positive control, because a boolean that changes nothing cannot distinguish "the flag did not help" from "the array never reached the consumer". check_settings_flags.py asserts each shipped name against the atom table AND the recovered switch, since a misnamed flag is silently inert and looks exactly like a failed fix. enableSquadBuildingSetsFeature is the reason both checks are needed: a real atom with no arm here. Live: 439 contract checks pass, market unit suite passes. Not yet tested in game. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
34 lines
1.3 KiB
Python
34 lines
1.3 KiB
Python
"""What does the /settings deserializer actually parse?
|
|
|
|
ENDPOINT_MAP claims FutGetSettingsServerResponse (0x18013c6d0) reads ONE key,
|
|
`configs` (0xa2), an array of {type(0x354), value(0x377)}. That is a narrow claim
|
|
about a class that is supposed to carry ~40 feature flags, and the atom table
|
|
holds flag names (enableDraftMode 0xf9, friendlySeasonsEnabled 0x133,
|
|
enableSquadBuildingSetsFeature 0x100) that have to be read by SOMETHING.
|
|
|
|
This asks the decompiler directly, and prints the coverage numbers so that any
|
|
"it does not parse X" conclusion can be checked against the whole function rather
|
|
than a truncated slice (the FutMoveCard retraction, 2026-08-04).
|
|
"""
|
|
import re
|
|
|
|
TARGETS = {
|
|
0x18013C6D0: "FutGetSettingsServerResponse deser (claimed: configs only)",
|
|
0x18013D1F0: "CONTROL: squad record parser (known multi-atom)",
|
|
}
|
|
|
|
for va, label in TARGETS.items():
|
|
f = func(va)
|
|
src = dec(va)
|
|
body = f.getBody().getNumAddresses() if f else -1
|
|
print("=" * 78)
|
|
print("%#x %s" % (va, label))
|
|
print(" ghidra name : %s" % (f.getName() if f else "?"))
|
|
print(" body bytes : %d" % body)
|
|
print(" decompile : %d chars <-- searches below cover ALL of it" % len(src))
|
|
print("-" * 78)
|
|
print(src)
|
|
print("-- callees --")
|
|
for a, n in callees(va):
|
|
print(" %#x %s" % (a, n))
|