Atlas passives management is fun until it isn't. Please add a templating mechanism.

The atlas passives tree is relatively new and there's been some great iterations on it. Yet, I'm burnt out on having to re-roll the atlas passives tree over and over and over AND OVER to work on tedious time grind challenges or switch over to farming something totally different. So much, that most of my challenges are left at 3/4 and 5/6 because: it's just not fun and I just don't care after running n-thousand maps anymore.

I didn't see anything about making the management of the atlas passive tree a better experience in the 3.19 patch notes. Anything from being about to template up (sentinel-controller-style) a tree to splitting the tree into 2 new trees to adding more atlas passive points or reducing some of the atlas passives fluff.

Ultimately, I don't want to keep having to reroll the tree OR I want the re-allocating of the atlas passives tree to not be a constant micromanagement chore (give me like, 3 slots to save a tree template with). It really, really, really gets tiresome. Can you make this a highlight for 3.20+?

And if this does get addressed, please don't make this an api-external thing. In-game is the way to go. Api-external is just a lazy way of faxing me a gif of a middle finger.

Edit: Oh, and I'm fine if there needs to be a resource cost (currently orbs of unmaking), but again another nice piece of tech from the sentinel controller would be the concept of charges over consuming change currency.

Thinking about this, if I could itemize my atlas passive tree and then socket that itemization-thing into the map device.. THAT would be slick and give the choices "weight".


Thanks.

This is a reasonable suggestion.

I think that while the atlas tree provides a lot of value to the game it encourages certain unfun play loops by encouraging players to stockpile encounters of specific types before re-allocating their atlas passives for improved rewards in those encounters.

I don't think the atlas tree should have a re-spec cost at all but either way a method of saving optimal trees would be a welcome addition.