You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think defining search terms is not sustainable. It's too many specially when you add in mods from Uniques.
Search for mods from uniques is important as the range values for those can be very impactful.
A syntax similar to name="" is probably a good way to go. For this to be effective, the mod choices should be presented (an in-textfield dropdown popup maybe) instead of burdening the user to remember/type in the right mod.
Since there are numerous mods, I think the dropdown should be context sensitive and know if the user is search for boots, or str gloves, or queen of the forest - and should show mods only for those.
Or maybe use a tab (or ctrl+space) auto-completion like what you have in IDEs. This would at least show you the search terms. I think that's a better way. Or probably the feasible way.
The text was updated successfully, but these errors were encountered:
I think defining search terms is not sustainable. It's too many specially when you add in mods from Uniques.
Search for mods from uniques is important as the range values for those can be very impactful.
A syntax similar to name="" is probably a good way to go. For this to be effective, the mod choices should be presented (an in-textfield dropdown popup maybe) instead of burdening the user to remember/type in the right mod.
Since there are numerous mods, I think the dropdown should be context sensitive and know if the user is search for boots, or str gloves, or queen of the forest - and should show mods only for those.
Or maybe use a tab (or ctrl+space) auto-completion like what you have in IDEs. This would at least show you the search terms. I think that's a better way. Or probably the feasible way.
The text was updated successfully, but these errors were encountered: