Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Match single sets to loadouts more effectively #7846

Merged
merged 4 commits into from
Jul 25, 2024

Conversation

deathbeam
Copy link
Contributor

Instead of assigning 1 size sets to existing loadout links, just check for this when the loadouts are being matched instead. Its more reliable and do not relies on links to be filled (in case of name match sets for example).

Link to a build that showcases this PR:

Loadouts with groups: https://pobb.in/u/thedeathbeam/pf-poison-scourge-arrow
Default loadout with names: https://pobb.in/u/thedeathbeam/pf-poison-spark
Abc loadout with config being "Default": https://pobb.in/jdpxU9ADNlGF

@Paliak Paliak added the bug: behaviour Behavioral differences label Jul 23, 2024
@Peechey
Copy link
Contributor

Peechey commented Jul 24, 2024

What about for a single Tree? I don't think this is supported in live even now with group Loadouts and I don't see a huge need for it but if we're not going to, the third condition in Help should be updated to say so

@Wires77
Copy link
Member

Wires77 commented Jul 24, 2024

Found an issue, but I'm not sure it's caused by this PR or if it's just a side effect:

  1. Using your 2nd example build
  2. Create a new config set and swap to it
  3. Notice loadout dropdown doesn't change, and clicking on the loadout doesn't swap the config set back (you have to click on "Loadouts:" and go back to "Default" for it to do so

Instead of assigning 1 size sets to existing loadout links, just check for this when
the loadouts are being matched instead. Its more reliable and do not relies on
links to be filled (in case of name match sets for example).

Signed-off-by: Tomas Slusny <slusnucky@gmail.com>
Signed-off-by: Tomas Slusny <slusnucky@gmail.com>
@deathbeam
Copy link
Contributor Author

Found an issue, but I'm not sure it's caused by this PR or if it's just a side effect:

  1. Using your 2nd example build
  2. Create a new config set and swap to it
  3. Notice loadout dropdown doesn't change, and clicking on the loadout doesn't swap the config set back (you have to click on "Loadouts:" and go back to "Default" for it to do so

This was also problem on master, loadout selection wasnt resynced on active set change. Pushed commit that will fix it here

Signed-off-by: Tomas Slusny <slusnucky@gmail.com>
@deathbeam
Copy link
Contributor Author

What about for a single Tree? I don't think this is supported in live even now with group Loadouts and I don't see a huge need for it but if we're not going to, the third condition in Help should be updated to say so

Updated te help file

@Wires77 Wires77 merged commit 89dca9b into PathOfBuildingCommunity:dev Jul 25, 2024
2 checks passed
@Wires77 Wires77 changed the title Explicitely check for 1 size sets for loadouts Match single sets to loadouts more effectively Jul 25, 2024
@deathbeam deathbeam deleted the use-explicit-match branch July 25, 2024 07:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug: behaviour Behavioral differences
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants