[OmegaJackie]

What

Adds a quest path for Keyward Bound (quest id 5466, SubGsc801_05466), the unlock quest for Keybound Brawler — the typing duty added at the Gold Saucer with the Keybound collaboration event. It's a limited-time quest (Festival 257).

I put it under QuestPaths/2.x - A Realm Reborn/Unlocks/Gold Saucer/ so it sits with the other Gold Saucer attraction unlocks, next to 3201_Every Little Thing She Does Is Mahjong.json (the closest precedent — also a SubGsc attraction unlock). Happy to move it to Other Quests/Special Quests/Collaboration Quests/ if you'd rather go by journal genre, which for this quest is "Collaboration Quests".

The path

Seq	NPC	Territory	Interaction
0	Catlike Mammet (1058756)	144 The Gold Saucer	AcceptQuest, AetheryteShortcut: "Gold Saucer"
1	W'zazanh (1058754), Wonder Square	144 The Gold Saucer	Interact, TargetTerritoryId: 1360
2	Magitype Master (1058752)	1360 Keybound Square	Interact (plays a cutscene)
255	Magitype Master (1058752)	1360 Keybound Square	CompleteQuest

Territory 1360 is Keybound Square, reachable only through W'zazanh in the Gold Saucer. Sequence 1 answers a "Proceed to Keybound Square?" yes/no on the way through.

One thing worth flagging

After the sequence 2 cutscene, the game shows a SelectYesno whose OK button stays disabled until an "I understand." checkbox is ticked — it's the notice that Keybound Brawler requires a keyboard. That isn't a plain yes/no prompt, so it may need explicit handling; I've left a Comment on that sequence. I don't know whether Questionable's existing dialogue handling copes with a checkbox-gated confirm, so flagging rather than guessing.

How it was recorded

I played the quest through once and read each NPC's data id, position and the quest sequence live from the client at the moment of each interaction. Positions are the NPCs' exact GameObject.Position floats.

Two deliberate omissions:

• No IsSeasonalQuest — none of the 34 existing files under Seasonal Events/ set it, so folder placement looks like the convention.
• No LastChecked — that looks like it's for whoever verifies a path rather than the author, so I left it for you.

Verification

• dotnet test QuestPaths.JsonValidator — 4384/4384 pass
• dotnet test Questionable.Tests — 62/62 pass, with QUESTIONABLE_CHANGED_QUESTS scoped to this file. I confirmed the file is genuinely in the theory rather than silently filtered out, by temporarily planting a second AcceptQuest and watching QuestShouldPassSemanticValidators(embedded: 5466_Keyward Bound) fail.
• dotnet test QuestPathGenerator.Tests — 1/1 pass

Not verified: the path has not been replayed by Questionable itself. The quest is complete on my character now so I can't re-run it, and it's a limited-time event quest. Every step's data is observed from a real playthrough, but nobody has watched Questionable drive the path end to end — worth a second pair of eyes from someone who still has the quest open.

AI/LLM disclosure

Per CONTRIBUTING.md: this was produced with AI assistance — Claude Opus 5 via Claude Code. The file carries the in-file disclaimer your AGENTS.md asks for, in the $ dev-comment field; JSON has no comment syntax and the schema sets additionalProperties: false, so that was the closest fit to the two-line form. Tell me if you'd rather it lived somewhere else, or not at all.

Opening as a draft pending my own review, so I'm not putting it in front of a maintainer before I've read it properly.

[alydevs]

Thank you for your contribution. I implemented this differently and made some code changes as well, but I put your username in the authors field of the path at #938