Define "Build Directives" to refine calculations and improve reports

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'd like to filter and refine calculations to better plan my build, but the current calcs tab - albeit wonderfully detailed - gets bogged down by details about things my build does not care about. Likewise, features such as the trade calculator could be made more precise if the program had some way to understand what the player is trying to achieve with their builds.

Describe the solution you'd like

There could be a feature (either as part of the Configuration tab or all by its own), where the user could toggle flags, which I tentatively call "Build directives", that tell the program what calculations are more or less important for that specific build. Those directives could start as a small set, and further expanded/defined by the community with time. For example: suppose I'm trying to create a Cold DoT build. I could toggle directives such as:

• This build doesn't use criticals;
• This build does not care about melee damage;
• This build does not care about hit DPS;
• This build prioritizes cold damage over other sources;
• This build prioritizes damaging ailments;

Now that I've set those directives, the PoB can better understand my build, and provide better-tailored information, such as:

• Hide all non-relevant calculations from the Calcs tab (critical hit data, hit DPS, melee DPS, etc.).
• Change the node power calculations so nodes focusing on cold damage have higher weight over less interesting nodes, and deprioritize things that would convert cold damage to other types, even if the raw calcs would follow a different route;
• Formulate more precise predictions and guess the best possible options for trade search.

Describe alternatives you've considered

I appreciate that the example above is already covered in part by the Configurations tab and how the system calculates, well, everything. My point is not to remove features already in place, but simply that the user could get more focused feedback, and potentially more precise insight into how to make their build better by removing the clutter (which varies from build to build), by having a way of telling the program "Hey, for this thing I care about this and this, and I don't care about that and that". Also, I imagine it would be tempting to automate some of those toggles based on things like nodes taken, skills or gear in use. While that could be cool down the line, I assume it would be easier to design and implement manual toggles, and on later revisions explore things like automatic settings.

Additional context

No response

Das Issue nennt den Configuration tab, Calcs tab, node power calculations und trade calculator als betroffene Einstiegspunkte, aber keine Dateien oder Tests. Beginne damit nachzuverfolgen, wie diese Bereiche derzeit Build-Einstellungen verwenden, definiere anschließend einen kleinen anfänglichen Satz von Direktiven und überprüfe, dass jede Direktive die vorgeschlagenen fokussierten Berechnungen und Handlungsanleitungen für Trades erzeugt.