An option the hide items from FG and or AoM would be useful I think.
Youāll be able to do that very soon via advanced search. Currently the only way is either to use browser search in item db or you can open calc, select item slot and search there, itās limited to selected slot+type.
Thanks. Most of these, except for item skills will be coming in the initial version of adv. search.
In adv. search youāll be able to select categories.
Yeah, youāll be able to do that in advanced search.
I also wanted to say that in future Iām planning to introduce a sort of āglobal filterā based partially on adv search. Basically thereās a global filter already, but it includes only one property - rarity. In future youāll be able to include other āglobalā props in there.
Advanced search is now available. You can now find almost anything you need. Currently searching through granted skills/procs isnāt supported, but this will be added in future.
thx for advanced search
i also get the message with the chrome browser today, all grim tools, all 6 page says in the chrome browser:
not safe and the https symbol in the bar is red
Edit:
Google Chrome ist auf dem neuesten Stand.
Version 74.0.3729.131 (Offizieller Build) (64-Bit)
Well, I think there are some problems with searching for certain +skills on preffixes and suffixes.
This is my example:
I am looking for all pref/suff with Demo skill: Stun Jacks
So, I have checked following check-boxes:
Item prefixes, Item suffixes, skill bonus to: Stun Jacks.
All the rest check-boxes are unchecked.
The search result is 500 random (?) affixes.
So I asume that smth might go wrong in the code? Try for yourself.
Or am I doing smth wrong?
Take Care,
GP.
ps. Oh, I might find the problem - I should put min/max also. When I put min=1 max=1ā¦ Everything comes into place.
SO FALSE ALERTā¦
Yeah, in current implementation you should always specify min or max or both, otherwise the field will be ignored. I probably should provide some hit for that.
Hello there !
It seems that there is a bug in the search engine for the Bysmielās Desert Barb augment (I donāt know if it happens for others).
When searching with āpierce resistanceā or even ā*% pierce resistanceā (without quotes), the augment does not appear in the results, see https://i.imgur.com/afFttNH.png .
However, it is found if using ā12% pierce resistanceā or āBysmielās Desert Barbā.
Not really a bug per se. but rather unusual filter order + search result count limit. It just doesnāt get included in the resulting set, due to 500 item limitation. Iām not sure though, why exactly this particular item is excluded and others are shown instead.
You can check that itās possible to actually find this specific item, e.g. via āpierce resistanceā āaugmentā.
On a side note if you use advanced searchm youāll find it without any issue.
Donāt know if you know about it, āspiritā is not being searched: https://youtu.be/I3zeZkkwHII
Doesnāt find āspiritā, but inserting āspiā does find stuff:
Working as intended. This field is called ānameā for a reason, you can use it to filter items by names. If you want to search by spirit - thereās a field for that in character attributes section. If you want to search the old-fashioned way using pseudo full-text search, you can do that using old search field.
Huh, didnāt think about it this way. Thanks for explaining.
Doing a normal search for āconvertedā leaves out several belts (maybe more, but the belts are what I noticed it for). Specifically:
Boneweave Girdle (Mythical version is displayed as expected)
Gladiatorās Distinction (Mythical version is displayed as expected)
Mythical Cord of Violent Decay (Non-mythical version is displayed as expected)
Mythical Pack of Treacherous Means (ditto above)
Mythical Storm Shepherd (ditto)
Mythical Murmurās Kiss (ditto)
Mythical Sash of the Bloodlord (ditto)
Interestingly, searching for the full āconversion stringā (e.g. āVitality Damage converted to Physical Damageā or āAether Damage converted to Lightning Damageā) will return the respective belts as expected.
Edit: I can confirm itās not just belts. There are several items with normal/empowered/mythical versions that seem to only return one version when searching for āconvertedā.
Iāll quote myself from 2 days ago:
Not really a bug per se. but rather unusual filter order + search result count limit. It just doesnāt get included in the resulting set, due to 500 item limitation. Iām not sure though, why exactly this particular item is excluded and others are shown instead.
You can check that itās possible to actually find this specific item, e.g. via āpierce resistanceā āaugmentā.
On a side note if you use advanced searchm youāll find it without any issue.
Ah, didnāt know about the 500 limit. Sorry to make you repeat yourself!
How does this work exactly?
When I specify Weapon Damage = Lightning Damage and donāt enter a min/max value, I get results of items without Lightning Damage as the base damage type.
However, if I enter a min of 1 and a max of 500, for example, I get back items with base Lightning Damage.
The, if I add in an Offense filter of ā[X] Lightning Damageā and NO min/max values, it doesnāt filter return what I expect it to. Adding in a min/max returns no results.
If you like I can provide a step-by-step repro. Maybe Iām just using it incorrectly.
You specify a filter, e.g. weapon damage = lightning famage in your case, and at least min/max value or both, thereās no trickery there, itās supposed to be obvious, but perhaps not so much.
All filters are combined via AND, so the search returns items that match all selected filters.
I would have thought that leaving the min/max blank, it would search across all ranges.
Anyway, Iāll DM you an example tomorrow of why I was confused about the results.
I have a super important request that might change the general life purpose of every creature in the world.
Make the keyboard button āenterā trigger āsearchā button in advanced search.
I just found advanced search a few days ago. The days of needing intricate regex incantations for simple things are now a thing of the pastā¦
or not.
But at least it lets me search faster and apparently skip the database building step.