Thanks for fixing the Atlas progression on standard, but...

Thanks for fixing the Atlas progression on standard, but...

I can't run maps because the map device is stuck on the last map and won't let me start a new one.

Any chance you all could fix that new bug?

It's not my intention to be rude, but it's not clear from your post exactly what you mean.

A screenshot might be helpful - but really, either a short video or a very detailed text-based description is likely needed.

"

Leapgrip#4529 wrote:

I can't run maps because the map device is stuck on the last map and won't let me start a new one.

Keyboard or controller?

It's a feature that the map device defaults to the last opened map.
You can just click off of that map, and navigate to a different one.

Sarno is right: video, or screenshot + details, would go a long way towards clearing up what issue you're experiencing.

Ok, so the issue is that all my other characters can start a map but the one I am currently trying to play.

When you click on the map device and it prompts you to "Activate" the map nothing happens. The old portals do not despawn and no new ones open.

I am running a valid map with no warnings like the "Maven has already witnessed this map." The activate button is clickable , the atlas screen closes, but the new portals do not open and the map is not consumed.

Is there no message in the chat window when this happens?
When that happens, if there was an error, there should be a message saying what went wrong.

There is no error message, but the problem seems to be exclusive to Corrupted Conqueror maps.

I can get non-corrupted maps to run.

Ha! Found the issue!

Ok, GGG, the node Twist of Fate on the Atlas Skill tree is not allowing you to run corrupted rare maps in Standard.

Do you have Twist of Fate allocated on your Atlas passive tree?

If so, does de-allocating it resolve the issue?


edit: RIP, too slow :(

Thank you all for your help!

Is the Twist of Fate thing a known bug?

"

Leapgrip#4529 wrote:

Is the Twist of Fate thing a known bug?

It's currently one of the most frequently reported issues.

I haven't seen a member of staff formally acknowledge it (though the majority of fixed issues are never acknowledged prior to a fix being included in patch notes).