- summary: Asks for the whole anomaly board: every subarea, whether an anomaly is there and what it pays. Empty payload.
- area: Game.Anomaly
- confidence: 0.86
Asks for the whole anomaly board: every subarea, whether an anomaly is there and what it pays. Empty payload.
- Kind request
- Area Game.Anomaly
- Named by beta, gamemapping, stringtable
Carries nothing. One request returns the entire board - there is no per-subarea form.
THIS IS THE MESSAGE A FARMING SCRIPT WANTS. The board says which subareas currently carry an anomaly and what reward bonus each grants, which is exactly the input for deciding where to go.
Ask when you need to choose, not on a loop. The board changes when anomalies
open and close, and AnomalyOpenedEvent and AnomalyStateEvent tell you
about those as they happen - so you can keep your copy current without asking
again.
Three builds pad this message; no writer in any dumped build populates anything. Send it empty.
When you may send it
- Requires
character_loadedobserved - Raised by: one internal client notification, once per session - not a timer, not per subarea, not per map change. The bus hides what raises it, so send it once the session can render the map and zaap UIs inferred
Related messages
- You will then receive
AnomalySubareaInformationEventinferred — the server answers with the whole board
Recovered with score 150, confidence 0.86, margin 150 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.