I've played through some content that's introduced much later than we can meet Kiyoko (Dracia, druid's temple, Cait's temple, half of the siege, ...), then I've got the Amulet of Transference and found out that its possible to free Kiyoko without ever interacting with her.
Steps to reproduce: (not verified, I'm basing it on the save file that's been with me for about a month or longer. I can start a fresh playthrough to verify, but it may take a while...)
1. Finish the following quests and their prerequisites:
- "Den of Foxes"
- "Meet and Greet"
2. Probably have following interactions:
- Have Keros make you an offer to become Kitsune. (I didn't [Bind] at that time)
- Win the Duel of Wits with Nareva.
3. Obtain Amulet of Transference.
4. To prevent interactions with Kiyoko do not:
- equip the amulet.
- sleep. (in-game)
5. Go to Kitsune Den and navigate to Komari, interact with her (you may need to [Wait], but it won't affect the bug) and pick the [Free Kiyoko] option, which shouldn't be here.
While following along (clicking [Next]) Keros will mention Nareva related stuff. Afterwards, Amulet of Transference will be removed, and player will be rewarded with a Control Rod.
I'm not entirely sure which other quests and interactions may be required to trigger the bug, I've mentioned everything I think could have an impact. The only other quest related to Kitsune I finished is "For Want of a Nail".
Alternatively, instead of going to Komari in step 5, player can [Talk] with Kura (Kitsune Agent) - here, the tooltip of [Amulet] mentions Kiyoko, whom player hasn't met yet.
I don't know whether there is a steam achievement for freeing Kiyoko, but I didn't get it. If there should be a quest in the journal, its neither started nor completed.
---
Version: 0.8.17 (Steam and web) However, the save file went through a few public game versions; started during or before 0.8.10.
Browser: firefox 145.0.
Browser errors: none after loading the save file. I've set ad blockers and similar protections off. Bug progressed exactly the same as in steam version of the game. The warnings and errors during game loading were due to:
1. compatibility mode (lack of <!DOCTYPE html>)
2. HTTP 404 when loading cordova.js
3. some error in vendors.chunk.js
but they didn't seem to have any impact on gameplay.
Steps to reproduce: (not verified, I'm basing it on the save file that's been with me for about a month or longer. I can start a fresh playthrough to verify, but it may take a while...)
1. Finish the following quests and their prerequisites:
- "Den of Foxes"
- "Meet and Greet"
2. Probably have following interactions:
- Have Keros make you an offer to become Kitsune. (I didn't [Bind] at that time)
- Win the Duel of Wits with Nareva.
3. Obtain Amulet of Transference.
4. To prevent interactions with Kiyoko do not:
- equip the amulet.
- sleep. (in-game)
5. Go to Kitsune Den and navigate to Komari, interact with her (you may need to [Wait], but it won't affect the bug) and pick the [Free Kiyoko] option, which shouldn't be here.
While following along (clicking [Next]) Keros will mention Nareva related stuff. Afterwards, Amulet of Transference will be removed, and player will be rewarded with a Control Rod.
I'm not entirely sure which other quests and interactions may be required to trigger the bug, I've mentioned everything I think could have an impact. The only other quest related to Kitsune I finished is "For Want of a Nail".
Alternatively, instead of going to Komari in step 5, player can [Talk] with Kura (Kitsune Agent) - here, the tooltip of [Amulet] mentions Kiyoko, whom player hasn't met yet.
I don't know whether there is a steam achievement for freeing Kiyoko, but I didn't get it. If there should be a quest in the journal, its neither started nor completed.
---
Version: 0.8.17 (Steam and web) However, the save file went through a few public game versions; started during or before 0.8.10.
Browser: firefox 145.0.
Browser errors: none after loading the save file. I've set ad blockers and similar protections off. Bug progressed exactly the same as in steam version of the game. The warnings and errors during game loading were due to:
1. compatibility mode (lack of <!DOCTYPE html>)
2. HTTP 404 when loading cordova.js
3. some error in vendors.chunk.js
but they didn't seem to have any impact on gameplay.
