After recruiting Serafen, the main character travels to Fort Deadlight without talking to Serafen at all, and reachs for the Forge before going to the Court. Serafen will suddenly talks about Syri out of nowhere.
I believe such dialogue should be brought up by Serafen at the Court only, not any other place else, because Syri is at the Court.
The right sequence should be :
1. Recruit Serafen
2. *** Talk to Serafen about how to infiltrate the Fort Deadlight. This step should be mandatory for the smooth story run, but currently it is not. ***
3. Infiltrate the Fort Deadlight.
4. Going to any place in Fort Deadlight should not trigger Serafen to talk about Syri.
5. When the main character visit the Court -- where Syri stays, Serafen gives a warning about Syri to the Watcher.
I wish that I do not need to attach the save file. I have rerolled new character like more than 10 times and this happens every time. Testers should not find it hard to reproduce this bug.
You can post now and register later.
If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.
Category : Minor, should be easily fixed
After recruiting Serafen, the main character travels to Fort Deadlight without talking to Serafen at all, and reachs for the Forge before going to the Court. Serafen will suddenly talks about Syri out of nowhere.
I believe such dialogue should be brought up by Serafen at the Court only, not any other place else, because Syri is at the Court.
The right sequence should be :
1. Recruit Serafen
2. *** Talk to Serafen about how to infiltrate the Fort Deadlight. This step should be mandatory for the smooth story run, but currently it is not. ***
3. Infiltrate the Fort Deadlight.
4. Going to any place in Fort Deadlight should not trigger Serafen to talk about Syri.
5. When the main character visit the Court -- where Syri stays, Serafen gives a warning about Syri to the Watcher.
I wish that I do not need to attach the save file. I have rerolled new character like more than 10 times and this happens every time. Testers should not find it hard to reproduce this bug.
Share this post
Link to post
Share on other sites