Server: [LE-64] Timeline is Locked

[Xspark]

Restarted the game, validated the files the error message persist, any other suggestions to resolve this issue ?

[srammerwv]

same issue here on one of my alts

[aggromagnet]

You have to go back and redo the quests of the previous mono. It'll most likely be a mono with alternate timeline paths to choose from at some point in the quests. Choose the quest path that would unlock the mono you're trying to access.

For example, killing Abomination in Fall of the Outcasts and talking to the spirit NPC thing let's you choose between the past (unlocking The Stolen Lance) and the future (unlocking The Black Sun). Sth like that at any rate.

Basically, old chars are stuck in the old unlock system if you've already completed a mono quest but not chosen both paths. If you hadn't opened any of those paths you need before, you don't have them open now until you unlock them the old way.

[Xspark]

Thank you

[Rogan]

Originally posted by aggromagnet:

You have to go back and redo the quests of the previous mono. It'll most likely be a mono with alternate timeline paths to choose from at some point in the quests. Choose the quest path that would unlock the mono you're trying to access.

For example, killing Abomination in Fall of the Outcasts and talking to the spirit NPC thing let's you choose between the past (unlocking The Stolen Lance) and the future (unlocking The Black Sun). Sth like that at any rate.

Basically, old chars are stuck in the old unlock system if you've already completed a mono quest but not chosen both paths. If you hadn't opened any of those paths you need before, you don't have them open now until you unlock them the old way.

I am stuck exactly at the 1st (LV58) Timeline with an old character on Legacy (online). I've already gone back, done both questlines, killed the boss twice, chosen "past" and "future" and am still locked on both of the next possible Timelines. :-( Reported bug in-game. EDIT: also tried re-Validating files. Still nothing.

[Cbarkley]

I have this exact same problem on 3 characters and support is not helping at all. Had to bug report, and guessing it will not get fixed until next major patch.