whist wrote:So let me get this straight, the in-game filter is a far cry from d2stats because you can't simply grab a config file from another tool that isn't maintained by us and drop it in as is? Also, the .json config isn't meant to be edited manually as text, as you've already found out it's gonna contain some codes that aren't easily human-readable, you're meant to use the in-game config UI.
Yeah, I'm planning to make a simple conversor that changes regex based hide rules into single item code based hide rules. It's gonna be long and not what the new one is intended for. The new UI allows for finer filtering and defined (but not publicly specified) group based filtering. The only way to convert from the old to the new is to take all the item codes and to throw the lines to see which items would be hidden, and to create singular hide rules for all of them to then paste at the end of the json array. Not pretty but usable so that people finally are able to transition I guess?
I agree that having shows for important items like rare jewelry and all TU/set/SSU/SSSU or quest items and then a blanket hide, or area/item level based progressive hides and then a blanket hide would fit 99.99% of demands, but some people are set on their ways of hiding stuff, so if I can make a simple conversor, if ugly, I think it would help them.
Also, I'm more of a fan of editing files than UIs but I agree that the file having item or class codes is better for maintainability. In any case, it's not gonna be pretty.