Looting profiles, item filters, are somewhat on hold while a guide is put up on the new, improved, OMG SHINIES, item filtering interface/api. Once that is up you can expect to see some community driven item filters put up. WIMM
The current item filtering system will stay as it is. It's "what we're providing". The only thing that needs to be done with the guide is adding a warning about the changes to implicit/explicit stats, and how they are no longer accurate. The API itself has a lot more things devs can take advantage of (DPS, mod strings with exact values, armour / damage values), but trying to extend or modify the item filtering system we provide isn't possible by design. It'd be much better for devs to write a better system from the ground up, as our stuff has to remain closed source. Users aren't forced into our system though. The design of things are such that devs can easily implement their own IItemEvaluator implementation, and replace the current IItemEvaluator instance with theirs, and everything will use that instead, aside from the GUI, which is type locked to our DefaultItemEvaluator implementation. If you check ExampleBot, you'll see the basics of this: Code: /// <summary>The item evaluator the bot should use.</summary> public IItemEvaluator CurrentItemEvaluator { get; set; } ... CurrentItemEvaluator = new DefaultItemEvaluator(); ... // We need to set this to avoid some hard dependencies. ItemEvaluator.GetItemEvaluator = () => CurrentItemEvaluator; For your own item evaluator, you'd not use DefaultItemEvaluator and instead your own type. The ItemEvaluator.GetItemEvaluator re-assignment is important in actually replacing the filter system used by everything else.
