- summary: One completed quest in the journal: which quest, and Ankama's completion counter for it.
- area: Game.Quest
One completed quest in the journal: which quest, and Ankama's completion counter for it.
Kind struct · Area Game.Quest
One entry of the journal's finished list (QuestsEvent.finished_quests). It is declared
inside QuestsEvent and travels nowhere else.
HOW TO USE IT. Only QuestFinished.quest_id matters: the quest is complete. The client
appends that id to its finished list and looks it up in the game data to mark every
objective of every step of the quest as done - the wire carries no objectives for a
finished quest, because they are all done by definition.
QuestFinished.finished_count is never read by any dumped client; do not build logic on
it.
The id is narrowed to a signed 16-bit value on the way in.
Not sent on its own — it is only ever an entry of QuestsEvent.finished_quests. inferred
Used by
Fields
| # | Field | Type | Meaning | You set it |
|---|---|---|---|---|
| 1 | finished_count | int32 | Ankama's completion counter for the quest. Never read by the client on any dumped build; the meaning comes from Ankama's field name only. Named only where exactly one other int32 is declared, and left obfuscated otherwise. | never |
| 2 | quest_id | int32 | Which quest was completed. (quest id) The only member the client reads. It is stored as a signed 16-bit value. | never |