You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When applying a new shared loadout, show the intrinsics associated with the shared loadout's class item (eg. the Hunter cloak with Spirit of the Assassin, Spirit of Synthoceps).
How does this fit into your workflow?
Class items exotic intrinsics are a pretty integral part of the loadout. When i'm applying a loadout that was shared with me, i'd want to match both if not at least one, depending on the build.
In addition, if this information was added to the Share API, I could use builders.gg to filter known shared loadouts on the class items I have.
At a first glance, this looks similar to our lockedExoticHash. In practice, lockedExoticHash is not used by consumers of loadout shares since it's much more reliable to simply check the equipped armor for an exotic.
lockedExoticHash is used in Loadout Optimizer.
We could have something like lockedExoticTraits in our Loadouts structure and even let users select traits in Loadout Optimizer
This is not particularly interesting for Loadout Optimizer since class items all have the same stats
It also wouldn't guarantee that these show up in loadout shares unless the share creation code took care to populate them
An alternative might be simply storing them as socketOverrides.
Proposed change
When applying a new shared loadout, show the intrinsics associated with the shared loadout's class item (eg. the Hunter cloak with Spirit of the Assassin, Spirit of Synthoceps).
How does this fit into your workflow?
Class items exotic intrinsics are a pretty integral part of the loadout. When i'm applying a loadout that was shared with me, i'd want to match both if not at least one, depending on the build.
In addition, if this information was added to the Share API, I could use builders.gg to filter known shared loadouts on the class items I have.
/cc @robojumper
The text was updated successfully, but these errors were encountered: