- summary: Asks for the players the character has recently met or grouped with, as distinct from added friends.
- area: Game.Social
- confidence: 0.89
Asks for the players the character has recently met or grouped with, as distinct from added friends.
- Kind request
- Area Game.Social
- Named by beta, gamemapping
It is one of a FIXED FOUR-REQUEST BURST the client fires once per entry into the
world, straight after asking for the game context. The client's own name for the
routine survives obfuscation: SendRequestAfterCharacterLoaded. The order is
constant:
ContextCreationRequest(the context first) 1.FriendListRequest2.AcquaintanceListRequest3.SpouseInformationRequest4.GuildInformationRequest
That order is not guessed from traffic: it is the order the routine allocates the four objects in, and a live capture reproduces it exactly - the first three land inside the same millisecond, the guild request three milliseconds later.
SEND IT ONCE, AT THAT POINT. NEVER POLL IT. The trigger is "the character finished loading", not a timer.
ACQUAINTANCES ARE NOT FRIENDS. These are players the character has recently met
or grouped with; explicitly added friends come from FriendListRequest. The
two lists overlap but neither contains the other.
Carries nothing.
When you may send it
- Requires
character_loadedobserved
Related messages
- Reply not yet recovered: the acquaintance list arrives as an event that has no signature here yet.
Sequence
Step post_character_load.2 observed — of 4 requests, in the order the client's own routine allocates them
Recovered with score 215, confidence 0.89, margin 215 over the runner-up. A margin close to the score means nothing else came near; a thin margin means a decoy nearly won. Members recovered: 0 of 0.
Aucun avis à afficher.