2 Atlas Node Bugs - Node Access with and Completed/Not - Completed Maps
|
I've seen the bug regarding not being able to access an Atlas map even though there is a completed connected map. The following bug I am reporting includes that but, in addition, a bug where a nearby node that suddenly became accessible even though no connected nodes have been completed. Might be coincidence but it also might be related: i.e. did it unlock the wrong map after I completed one?
See screenshot. Nodes 1 and 2 described below. ![]() Nodes 1. Can't move to map to despite completing connected map. 2. Can move to map despite not completing any connected maps. Last bumped on Nov 21, 2025, 10:06:24 AM
|
|
|
Follow up:
See screenshot below. I just ran map 2 (Molten Vault) and the connectors seemed to have visually corrected themselves. So it looks like a visual bug: it's not that the connections are incorrect, it's the rendering of the connections that are incorrect. See how one connector is gone from the original screenshot while another connector appears which would have been correct in the original screenshot. ![]() |
|










