docs: correction — empty endpoint map is partly downstream of never-connecting

GetSetting only carries IGO/ENVIRONMENT (not endpoints); no HTTP config fetch.
The endpoint map is filled from the online connection/login response in a live
client, so its emptiness is downstream of 'never dialed redirector', not root.
Integrated picture: frontend shows 'connecting' but the online subsystem never
initiates any network connection; the upstream 'start connection' trigger never
fires = the M2 frontier. Forcing corrected nucleusConnectREST's role (config
lookup, not sender) but found no callable shortcut.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
funman300
2026-07-02 18:44:20 -07:00
parent 105cca1cbe
commit 8f5b6b1d59
+15
View File
@@ -1041,3 +1041,18 @@ POPULATOR (who inserts into [ctx+0x19c8]) and its data source/channel. 29 funcs
+0x14153e010, +0x141603fc0, +0x146f5a400 (store sites). This needs the LSX-response→map mapping
or a decompiler. Live-memory + hook-call forcing (openfut-hook `probe`/force) is proven safe and
reusable. Weigh vs [[project_direction_pivot]].
### Correction/nuance (same session): the empty map is partly downstream
Checked the LSX channel: FIFA's only GetSetting requests are IS_IGO_ENABLED, IS_IGO_AVAILABLE,
ENVIRONMENT — NOT endpoint URLs. And no HTTP config fetch happens. So the endpoint config map is
NOT populated by a request we're mishandling; in a live client it's filled from the online
connection/login response (post-redirector). Therefore the empty map is (at least partly)
*downstream* of "never connected", not a pure root cause. Net integrated picture across all
runs: FIFA's frontend shows "connecting" but the online subsystem never initiates ANY network
connection (no getaddrinfo, no redirector dial); every deeper object (connect states, session
ctx, endpoint map) sits in its initial empty/dormant state because no connection ever happened.
`nucleusConnectREST` is a config-lookup (empty), not a sender, so it can't be used to trivially
trigger the dial. The true trigger — "start the online connection / dial gosredirector" — is
upstream and never fires; that remains the M2 frontier. Forcing was valuable (safe; corrected
the function's role; proved the endpoint map empty) but did not find a callable shortcut.