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

Allow aggregation of Artifact Upgrader data per artifact #2316

Open
frzyc opened this issue Jul 15, 2024 · 0 comments
Open

Allow aggregation of Artifact Upgrader data per artifact #2316

frzyc opened this issue Jul 15, 2024 · 0 comments
Labels
needs more thought Needs more thought to flesh out the solution

Comments

@frzyc
Copy link
Owner

frzyc commented Jul 15, 2024

Currently, the artifact upgrader works per character loadout. For every new artifact, users tends to have to check several loadout builds to see if it would be an feasible upgrade. What if this process can work in reverse? For any artifact, users can check if its a viable upgrade for any of their existing builds?

At the very minimum, I would imagine a UI where, per artifact, we can have a list of upopt graphs, like in the artifact upgrader, but across all loadout/builds.

There are a few concerns:
Technical

  • Would need to create a whole calculation for a character/loadout/build for every build on the account. this can be a lot, since it has to calculate both the base build and the upOpt Build. This will likely need to be heavily cached.
  • would likely need to migrate the upOpt calc to a webworker, due to the above this calculation will be unlikely be fast.

Feasbility/Logic

  • Even if an artifact may not be an immediate upgrade for all the builds, it may still be a possible "good" artifact if the builds use a different set/off piece.
  • the comparable metric, of % chance x % increase, may not be universally comparable, since increase in one loadout target may be different in "perceived value" than another.
@frzyc frzyc added the needs more thought Needs more thought to flesh out the solution label Jul 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs more thought Needs more thought to flesh out the solution
Projects
None yet
Development

No branches or pull requests

1 participant