NokiMo
Never Sink
Never Sink

patreon


Identified Trouble

With 3.0 GGG has added the ability to filter magic/rare items by mods. This system is a godsend and a curse combined.

It's a fairly simple system.

You can list one or multiple suffixes and the filter will highlight an item with AT LEAST ONE item in the list (OR connection). You can also add multiple lines to one ruleset. Each line needs to be satisfied. This is an AND connection. 

Example:

HasExplicitMod A B

HasExplicitMod C D

For the item to get highlighted, the item needs to fulfill the following conditions:

(A OR B) AND (C OR D)

 This makes the system absolutely sufficient for magic items that have at most 2 mods. You just need 1 line with all acceptable suffixes and 1 line with all acceptable prefixes. 

So where's the problem? Permutation.

It's easy to tell "At least fire resist or cold resist". It's hard to design the least 2 resistances out of 3 statement. In fact it's possible, but for that you'd need 3 rules, each containing the same lines and conditions and only different in the 2 HasExplicitMod lines.

This becomes much more problematic as the number of desirable mods grow. 

To create a rule that handles: "At least 3 of the following: "FireRes, ColdRes, LightRes, Dex, Int, Str, All Res, Crit Multi, All Attributes" one needs nPr(3,10) = 720 rules, This would double the size of the filter, which would lead to a whole series of problems and this only covers some of the ring suffix mods. A "full" permutation set of useful mods would likely weigh several terabytes. Does that mean SetExplicitMod-filtering for rare items is not coming?

Nope it doesn't. Luckily we don't have to bruteforce everything and can be quite smart about what combinations are truly worth considering and which ones are not.

The first version of it will be included in the upcoming update.

NeverSink


Related Creators