Quest objectives reset after transitioning between areas or logging out
Closed, ResolvedPublic

Description

What is happening:
Every time I change areas or log out of the game, objectives in the quest log reset, exclamation points reset (they will point toward the first objective in the quest, though sometimes it may possible to carry on and complete the later objective that came next in the quest) and quests that require you to travel between different areas, such as "Nothing a Billion Bandages Can't Fix" and "Intensive Carrot Unit" may become impossible to complete, as your current progress through said quests is often undone by this bug.

What should be happening:
The quest log should remain unchanged after travelling to a new area or logging out of the game. Exclamation points should properly direct the player toward the next objective. Progression through a quest should not reset, either.

Steps to reproduce the issue:
1.) Accept a quest with multiple steps in the quest log, preferably one that requires travelling between multiple areas. Ones that I have confirmed exhibit this problem are "Nothing a Billion Bandages Can't Fix" and "Intensive Carrot Unit".

2.) Take note of the way your quest log appears, where the exclamation point markers are guiding you, and what the current objective is.

3.) Partially complete the quest. If there is a point where the quest requires you to change areas, optionally complete every step up until that point.

4.) Take note of the way your quest log appears, where the exclamation point markers are guiding you, and what your next objective is.

5.) Travel through some load point to another area.

6.) Take note of your quest log's appearance and the exclamation point markers. Additionally, you can try to complete what was listed as the next objective in step 4 anyways, to see if you are, in fact, able to complete the quest. Sometimes you may be able to, such as when you need to talk to Flan in "Intensive Carrot Unit"

Game client version:
Build v 0.1.3.1

Reproduced by:
Aquosking

Reproduced on:
Windows 10, 64-bit, version 1607 (KB3213986)

Crash logs or exceptions generated:
N/A

Screenshots:
https://www.youtube.com/watch?v=5wrsmWv4LnU

Rattletrap closed this task as Resolved.Oct 5 2017, 7:18 AM
Rattletrap added a subscriber: Rattletrap.

This issue has been fixed.