- summary: Adds a quest, or one objective of it, to the followed list shown in the quest tracker.
- area: Game.Quest
- confidence: 0.88
Adds a quest, or one objective of it, to the followed list shown in the quest tracker.
- Kind request
- Area Game.Quest
- Named by beta, gamemapping
ADDS A QUEST TO THE TRACKER. Its opposite number removes one, and the two are the only difference between two otherwise identical messages - read the section below before you pick one.
WHEN TO SEND IT
WHEN YOU START FOLLOWING SOMETHING YOU ARE NOT ALREADY FOLLOWING. That second half matters. The real client keeps its own list of followed quest ids and checks it before sending: if the quest is already there it sends the UNFOLLOW message instead, and if it is not, it sends this one and adds the id. So the client never sends a follow for a quest it already follows.
Do the same. Track what you follow, and send this only for a quest you are not tracking - otherwise you and the server disagree about the list, and the client UI that reads it back will disagree with both.
ONE INTENT, TWO MESSAGES. Both come out of the same UI action and the same client method; which one goes out is decided by that list check. There is no "toggle" message.
WHAT TO PUT IN IT
THE QUEST, AND OPTIONALLY ONE OBJECTIVE. Send -1 as the objective to follow the quest as a whole rather than a specific step - that is the sentinel the client itself tests against, and it is what a capture of "follow this quest" shows.
Both values are 32-bit on the wire but the client carries them as 16-bit internally, so they are small ids, not handles.
WHAT COMES BACK
NOTHING DEDICATED. The followed list is state the server mirrors; no dumped client waits for a reply to this message. If you need confirmation, it arrives as the quest data the server pushes, not as an answer to this request.
When you may send it
- Requires
context_readyobserved - Raised by: a client-side state change: the player turning tracking ON for a quest or one of its objectives in the quest UI. The screen raises one intent carrying the quest, the objective and an on/off flag, and the writer checks its own followed-list first - it sends this only when the quest is not already in that list inferred
Related messages
- Nothing answers it - send it and move on no dumped client waits for a reply; the followed list is client state the server mirrors
Fields
| # | Field | Type | Meaning | You set it |
|---|---|---|---|---|
| 2 | quest_id | int32 | The quest to follow. | required |
| 3 | objective_id | int32 | Which objective of it to follow, or -1 to follow the quest itself. | required |
Recovered with score 200, confidence 0.88, margin 200 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: 2 of 3.
Aucun avis à afficher.