Timeless Jewel finder improvements: Multi socket select and Node maximum

[Crazy-KSK]

Check for duplicates

• [X] I've checked for duplicate issues by using the search function of the issue tracker

Is your feature request related to a problem?

It is currently quite tedious to find the best timeless jewel for a build because every jewel socket has to be checked individually.

Sometimes one might only care to have one of a certain node.

Describe the solution you'd like

I would like to be able to search multiple jewel sockets for a Timeless jewel simultaneously.

It would be nice to specify a maximum quantity per node type.

Describe alternatives you've considered

No response

Additional context

No response

[QuickStick123]

You can set the slider all the way to right to set it to required this will ensure all results have that node. I can't think of other reasons you would want to limit the results to say 3 of a given node.

Searching multiple jewel sockets would be nice but would require a fair amount of work to the UI.

[Crazy-KSK]

There are at least 3 nodes that do little to nothing if you have multiple of them:

Elegant Hubris: Gain 1 Endurance Charge every second if you've been Hit Recently Militant Faith: Immune to Elemental Ailments while on Consecrated Ground if you have at least 150 Devotion Gain Arcane Surge on Hit with Spells if you have at least 150 Devotion

[Regisle]

all 3 of those are something you are unlikely to have automatically weighted, what you could do is set it to a very low weight and make it required, but I do see the use case for a maximum

[Lothrik]

The main reason filters like this weren't implemented is simply because you rapidly run out of valid seeds. Each jewel only has a few thousand possible combinations, and out of those maybe 20% of them are actually available on trade at any given point in time. Even moderately complex search parameters already filter out over 98% of the possible results.

Filtering out a seed that has more than one "Gain 1 Endurance Charge every second if you've been Hit Recently" for example doesn't really make any sense, as you're already able to find which seed is best simply by assigning each possible node you're interested in a weight, and leave the node you only need one of at a low weight but set to required.

This will cause those "multiple copies of a node I only need one of" seeds to be deprioritized and show up later in the list, without outright hiding them from you.