Atlas pathing problems - 0.2.0g
Having problems with paths in the Atlas map in 0.2.0g.
Please consider why adjacent nodes don't connect. Wondering if there is there even a need for paths vs. just only being able to go to nodes you've discovered? Or nodes within a particular range of each other? (in the range idea, you could also add options to to "jump" longer ranges - extra waystones or mods or "stone of traveling" or something). Here is one from my Altas with a path that goes from the far left node to the far right node, directly through the middle (green) node where I am now, but doesn't connect to it! Of course, figured that out after running the middle map and then zooming all the way in to check lines after finding I couldn't progress to the next node as expected. Bug Report ID: #1351757739 ![]() Here's one a friend sent me that from the tower (1) at the top of the screen goes past the X to 2, then 3, then 4 before going back to the top of the screen to X. ![]() Last edited by Anesos#5916 on May 7, 2025, 2:31:53 PM Last bumped on May 7, 2025, 2:42:42 PM
|
![]() |
Fixed 2nd picture in the first post.
Here's my latest confusion. The blue line is where I _thought_ the path was going. The red seems to be where it's actually going, but there are still several unclear paths along the way. ![]() |
![]() |