PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding
Build price checking on historical or current data.
Personne n'a encore pris cette issue.
- Langage dominant
- Lua
- Étoiles
- 5.4k
- Forks
- 2.4k
- Merge moyen
- 1 j 12 h
- PR mergées (30 j)
- 26
Description
Check for duplicates
- I've checked for duplicate issues by using the search function of the issue tracker
Is your feature request related to a problem?
I would like to suggest adding a way to see an estimated price on an imported build (overall & per item), to see a build price before starting it.
I feel searching for prices of gear on a build could rather be automated instead of the user searching one by one (sometimes for many builds)
Describe the solution you'd like
I was thinking how nice it would be to see an estimate of what a build could cost. At the very least the pricing on uniques (as they are a lot more consistent.)
I was thinking about this a bit and 2 ways I thought of that could be a good way to go is either:
- Use a third party API (There is a project "poe-api-wrappers" which seems to be useful)
- Give an option to import a dump file from a specific league (current or past) from the poe.ninja dumps.
The idea I had is to create a bit of space to the right of the item to display the price (depending on the method of getting the data as mentioned above).
And then just a drop down of ["day 1", "week 1", "week 2", "end of league / current"] (these dates could be the end of, as id end of week 1.)
The main reasoning behind this is so that users (especially newer) can have a better idea of the costs of a build, see if it could be a potentially viable league start or should rather be an ult.
Given there might be some issues with the logic (of mine) of the feature, but I have no problem brainstorm together.
But I do believe this to be a solid idea and would add major quality of life.
Describe alternatives you've considered
No response
Additional context
No response
Guide de contribution
Ouvrir le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Piste de recherche
L’issue ne nomme aucun fichier, test ou point d’entrée. Commencez par localiser les zones d’importation de build, d’affichage des objets et de chargement des données, puis déterminez si les prix proviennent d’une API tierce ou de dumps de poe.ninja. Le travail serait considéré comme terminé s’il permettait d’obtenir des prix globaux et par objet estimés avec des données de ligue actuelles ou historiques.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- lua
- Domaine
- data, desktop
- Type d'issue
- Fonctionnalité
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 25/100