1.8 KiB
Endgame team recommendations
GetFriendRecommendLineup (CmdID 2985 from the checked-in 4.6.53 command table) now returns three recommended teams for the current MoC floor-12 snapshot. The response uses the OJJJDPNOKHG.lineup_list shape because its repeated ChallengeLineupList entries match the three stage rows in the referenced Client page. Each external character slug is resolved through the current resources/AvatarConfig.json; the server does not embed AvatarIDs in its handler.
The bundled snapshot is dataset revision 4.6.2, collected 2026-10-14, for MoC cycle 4.6.1 “Crossing the Afterlife”. The files identify the first-ranked Prydwen team for stages 12-1, 12-2, and 12-3. The dataset repository declares MIT and asks users to credit LvlUrArti; its README says it contains processed data shown on Prydwen. Attribution and source metadata are kept in resources/PrydwenEndgameTeams.json.
To refresh for another floor and the newest published snapshot, run python tools/update_prydwen_endgame_teams.py --floor 12 --stage-count 3. The updater validates every slug against this Client's AvatarConfig before replacing the snapshot; add a source-slug-to-AvatarVOTag alias in the resource if a name differs.
Protocol limitation: the current proto retains an obfuscated JFNJKAPPNOF enum and obfuscated response oneof names. The handler echoes the request type and key, and uses the lineup-list variant based on the visible three-row MoC UI and the message's repeated lineup schema. The exact numeric type-to-mode relationship and the meaning of response field ALDBIIIGLOM are not established. This first implementation does not discriminate modes using type or key, so it is limited to the illustrated MoC page and needs in-Client verification before claiming support for other Endgame modes or the friend-cleared tab.