When submitting a bug report, please use the below template and thoroughly fill out the necessary information.
Date & Time: April 1st 2018
Frequency: Happened once
World name: Zodiark
Character name: Ashelin Sama
Steps:
1. I was in the room where you are told to "get ready" and change into the correct clothes.
2. I pressed the bell to indicate that I was ready.
3. Nothing happened for a moment (I assume my partner did not click their bell yet) so I started looking around and clicked on one of the doors.
4. The door was apparently the exit, and I got teleported outside of the chapel
5. I went back inside, and got teleported to the altar. I saw everyone with the "Viewing cutscene" icon above their head. However I was not in the cutscene. This was the cutscene of both partners walking to the altar.
6. After the cutscene ended, the wedding proceeded normally. I was just sad I didn't get to see this first cutscene and cannot rewatch it in the inn.
It's possible that the issue has already been fixed by now, as this happened more than 2 years ago. I just never reported it as there didn't seem to be a clear/good bug reporting process back then.
Continue reading...
Date & Time: April 1st 2018
Frequency: Happened once
World name: Zodiark
Character name: Ashelin Sama
Steps:
1. I was in the room where you are told to "get ready" and change into the correct clothes.
2. I pressed the bell to indicate that I was ready.
3. Nothing happened for a moment (I assume my partner did not click their bell yet) so I started looking around and clicked on one of the doors.
4. The door was apparently the exit, and I got teleported outside of the chapel
5. I went back inside, and got teleported to the altar. I saw everyone with the "Viewing cutscene" icon above their head. However I was not in the cutscene. This was the cutscene of both partners walking to the altar.
6. After the cutscene ended, the wedding proceeded normally. I was just sad I didn't get to see this first cutscene and cannot rewatch it in the inn.
It's possible that the issue has already been fixed by now, as this happened more than 2 years ago. I just never reported it as there didn't seem to be a clear/good bug reporting process back then.
Continue reading...