Multiple Atlas Passive Trees
I´m sure this was already discussed multiple times but i couldnt be bothered to search. Plz GGG give us at least dual atlas trees,theres is nothing more frustrating then having to waste 1 ex everytime i want to play a diferent character that does diferent content. I would argue let respeccing the atlas tree be free but i can understand why its not. I just think atleast Dual Atlas Tree would make sense since mostly ppl either map or boss.
Last bumped on Jun 29, 2022, 9:05:07 PM
This thread has been automatically archived. Replies are disabled.
|
![]() |
This was suggested quite a few times ever since they gave us this enormous player agency and control over the atlas passive tree (Really, really well done here GGG), and I wanted to support this again, as I feel a system like that, would allow for someone to make more characters taht specialize for different things.
Just at the top of my head of things I enjoy playing (and then dying, hello HC ;D), usually troughout the game ever since we had Maven's first introduction with the ability to shape our atlas in meaningful ways was: -- A white / yellow tier map MagicFinder -- A harvest craft seeking speed junky -- Maven invitation rusher -- Alch and Go relaxed content play -- A heister / lab runner (Sadly none of that this league because of the cruelty of AN mods, but that's another topic) -- Alva Runner for some sweet temples -- A slow and steady safe bosser That's 7 characters, not counting re-rolls, which I've ever only played this much in Ultimatum (right after Maven introduction, where I fell in love for both the Maven's crucible and the good ol' trial master), and Siege of the Atlas (First introduction of the massive atlas skill tree + the new bosses were fun to me). Now, as different as their builds are in the passive tree, they'd benefit more from different atlas passives, but respeccing back and forth was such a pain, that I ended up having a template of "one size fits all" with little specialization. Would love to have the atlas passive tree build be tied to each character, while progression to be tied to the account |
![]() |