Quests

The game's quests are its story: the Archon quests of the main story, a character's story quests, the world quests found about the map, an event's quests and the daily commissions. Each is a run of steps, and each step asks something of the Traveler. The world holds a quest as the game's data does, by the game's own ids, and a quest's words come from the game's own text, as the dialogue page's talks do.

How it works

flowchart TD
  DUMP["The community's dump, outside the repository:<br/>its tables and quest files"] --> READ["genshin:text quests: the quests QuestId names"]
  DECODE["The text maps, decoded from the installed client"] --> READ
  READ --> FILES["generated/quests: one file a quest, checked by its schema"]
  READ --> WORDS["generated/questText: the quests' words, one chunk a language"]
  FILES --> START["startQuests: the first Archon quest not finished starts"]
  START --> PROGRESS["Quests in progress, from step 0"]
  DOING["Traveler's doing: a talk ended, an item collected,<br/>an enemy defeated, a thing acted on"] --> ADVANCE["doQuestEvent: advanceQuest on each quest in progress"]
  PROGRESS --> ADVANCE
  ADVANCE --> MET{"Every objective of the step met?"}
  MET -->|"no"| COUNT["The objective's count goes up, held at its own"]
  MET -->|"yes"| STEP["The next step, nothing met"]
  STEP --> DONE{"Past the last step?"}
  DONE -->|"yes"| FINISHED["The quest is finished: ParentQuestFinished,<br/>its Travel Log entry opens"]
  J["J"] --> SCREEN["Quest screen: the four lists, the selected quest's step"]
  SCREEN -->|"Navigate, or F"| TRACKED["The quest navigated to"]
  TRACKED --> TARGET["findQuestTargetPosition: the objective's resident or landmark"]
  TARGET --> BEAM["A beam over it, from 50 metres off"]

A quest

A Quest has the game's id, its kind, its title and description by text id, its steps in the order they are done, and the talks it runs. A step has its id, its line by text id (the "Talk to Paimon" the quest screen shows) and its objectives. An objective has a kind, a target and a count:

The kinds are the game's five, and the quest screen files them under the game's four lists. An event's quests are listed among the world quests, as the game's own quest types have it.

Progress

A quest's progress is the step it is on, which equals the number of steps once it is finished, and how many times each of that step's objectives has been met. advanceQuest takes a QuestEvent, the kind of the Traveler's doing and the id it names. Each objective of the current step that the event names is met once more, held at its count. Once every objective is met, the quest moves on to its next step with nothing met. An event no objective names leaves the quest where it was, and so does any event once the quest is finished.

Starting and finishing

startQuests starts the first Archon quest that is not finished, once the ones before it are, so the carried Archon quests run from the prologue's first. The other kinds have no start yet, as the quests proposal sets out, and the commissions are not yet dealt at the daily reset, as commissions notes. A finished quest stays in the progress map at its last step, and the quest screen lists only those started and not finished.

doQuestEvent hands one doing to every quest in progress. Each step moved past finishes its sub-quest, which getFinishedQuestEvents turns into a QuestFinished for advanceAchievements, and a quest its last step finishes into a ParentQuestFinished. A finished main quest is added to the set the Archive opens by, and its Travel Log entry opens, the entries read off the Archive's table when first needed. The world records a talk's end as a talk-to, a dropped item or a gathering point picked as a collect, an enemy defeated as a defeat under its kind, and a waypoint or landmark unlocked as an interact. A go-to has no doing yet, since a place's trigger is not placed in region data.

The quest screen

QuestScreen is J's screen, through the screens' ScreenKind.Quests. Its tabs along the top list every quest, then each of the game's four lists, and Q and E step between them. Down the left, each list's quests sit under its heading in the game's words. On the right are the selected quest's title, its step with its first counted objective's "(n/m)", and its description, over the button that navigates to it, or cancels the navigation of the quest already navigated to. F presses that button. The screen reads the quests in progress, their progress and their text map, and the world screen holds the one navigated to.

Navigation

findQuestTargetPosition finds where an objective's target stands among the regions in reach: the resident or landmark it names, or the resident whose talk it names. QuestBeam raises a column of light over that spot once the camera is 50 metres or more away, the distance at which the wiki says the game's beam appears. The beam reaches from under the lowest ground to over the highest peak, so it rises out of the ground wherever it stands with no height read for it. The world raises it over the first objective of the navigated quest's current step, in the floating origin's group, and V or a press on the HUD's tracker navigates to the quest the tracker shows.

The quests' content

QuestId is the inventory of quests the world carries, the prologue's first two to begin with. pnpm -C scripts genshin:text quests writes each one into the world: its kind, title and description from the quest table, and its shown steps from its binary output. It also writes the talks those steps end on, from the dialog table with each speaker named from the character table, and every word they show in every language. Each quest is checked against the world's own schema before it is written.

The dump scrambles the binary output's field names each patch, so the reader finds each field by its shape, as game data formats describes. A step with no words is the game's own bookkeeping and is left out. A shown step whose conditions ask nothing the Traveler does, such as a cutscene played, is left out and noted.

Parity

The quest screen is scored whole-frame against quest-screen, the English client's quest screen at 1920 by 1080: a mean difference of 55.84% and a FLIP of 0.8998. The wiki's screenshot draws the blurred scene and its own text under the screen, so the whole-frame score counts a double print rather than a placement. The blur behind J is provisional until quest-open.mkv lands on the roadmap's Recordings owed list.

Key files

Notes

• Only the Archon quests start, and a go-to does not move. The carried prologue starts at Wanderer's Trail's first step, which asks to reach a place. No region data places that trigger yet, so the step stays where it is until the quests proposal places it, and the carried quests' other steps wait behind it.
• Progress is kept in the save. The carried quests' progress is a slice of the save, so a reload resumes them as it does the bag and the wallet.
• Quests are served in the bundle, not from a base URL. Each carried quest and its words are imported on demand from the world's generated folder, through QuestLoaderMap and QuestTextLoaderMap, which a new carried quest adds a line to. The region data is served from a base URL, the quests are small enough not to be.
• A step keeps one objective. A step that finishes on any of several places lists each as a condition, so the reader keeps the first condition that asks something. A step asking for two things at once would lose the second.
• The beam's look is provisional. Its radius and colour wait on a recording of the English client navigating to an objective.
• The quest screen is laid out, not yet likeness. Its header, tabs, list, details and navigation button sit at the English client's 1080-high places, measured off the wiki's screenshot. Its five tab glyphs stand in as diamonds until traced, its header reads the game's "Quests" where the client reads "In Progress" (that text is not in the English the package carries), and its quest distances, kind and place marks, rewards row, Quest Overview button and UID are not built. The client draws the world blurred behind the screen; the parity page has no world to draw, so its frame scores 55.84% mean and 0.8998 FLIP, most of it that blur, and the screen's open, close and tab animations are not yet timed (the roadmap's Recordings owed).

Sources

• Quest, Genshin Impact Wiki: the Archon, story and world quests and the commissions, and the beam that marks a navigated objective from 50 metres off.
• Quest/Menu, Genshin Impact Wiki: the quest screen's list grouped by Archon quests, story quests, commissions and world quests, its tabs, and its quest information with its Navigate button.
• Event Quest, Genshin Impact Wiki: most event quests are world quests, and a flagship event's are story quests.
• Controls, Genshin Impact Wiki: J for the quest menu, V for quest navigation, and holding V to show the step's objective.
• AnimeGameData, the community's per-patch dump: the quest table's types and words, each quest's binary output of steps and conditions, and the dialog and character tables a talk is read from.