Filtering the quick trivial lists by race?

[greebmushroome]

Would it be possible to filter the quick trivial lists by race, please? We have so many cultural recipes these days (particularly for smithing and tailoring) that it's harder to use the quick trivial list as a tool to find recipes for skilling. One form this might take is a drop-down menu at the top that says "Show only cultural recipes for: " and then lets us choose a specific race (and maybe defaults to "All races" so that it's like the current page). Once someone selects a race, the list would show all the normal recipes plus the cultural recipes for the race selected, filtering out all the cultural recipes for the other races. That's my idea, anyway. Maybe it would only be useful for the smithing and tailoring lists, though....

thanks for listening!

-greeb mushroome

[Secone]

if you need skill up advice:

Complete Tradeskill Guide 2.0

But skill a good idea with the cultural filter on quicklist.

[Ngreth Thergn]

no-one wants a "quick" list anymore!

will think about it.

[KyrosKrane]

The problem with the quick trivial list is that it's just huge nowadays. I imagine the number of recipes has grown exponentially since it was first implemented, and many more recipes now have an exact trivial (making them appear on the list). The problem is huge bunches of those recipes aren't usable for a particular character.

[mewkus]

while you're thinking...

It would also be nice if we could specify a minimum (and maybe maximum) range of trivials too.

[kadasi]

It would also be nice if we could specify a minimum (and maybe maximum) range of trivials too.

I disagree with the statement that nobody wants quick trivial anymore. I have relied on the quick lists many times on my skilling up in each of the tradeskills, and my kids use it alot also. However, it would definitely be nice to specify a min and a max range so we don't have to scroll through trivs of 1 to 100 when we are looking for higher stuff.

[Lothay]

However, it would definitely be nice to specify a min and a max range so we don't have to scroll through trivs of 1 to 100 when we are looking for higher stuff.

Clicking on a heading sorts the list by that heading. So you can already sort the list up or down by the trivial.

[greebmushroome]

i think what ngreth is saying is that smarter lists, like what i requested, aren't so "quick" anymore (quick to implement, quick for the web server to generate).

[Flehmen]

Personally I liked having the simple "quick" list. Unfortunately... or fortunately... smithing has a ton of recepies that are all repeats of each other. (IE Dyes, Sizes, and I believe some DoN although I can't check from work... the list is too long and gets smacked by my firewall)

The point being that the quick list isn't quick any more. I think that is what people are trying to get to when they want filters by race, or max/min.

As a side note, the only other quick list to get smacked by my firewall is Tailoring another TS with sizes, and etc.

How do we solve this? I can think of three ways:

1. split the quick list into three along the lines of skill. (But of course we have such a handsome and intelligent house orge he'll put some magic in and just let us filter by skill level )
2. remove parts of the information, for example dyed armours, or DoN from the quick list and set up their own quicklist
3. combine chunks of info, like items with different sized but same skill level into one entry. This is by far the most complex and difficult and I am sure server and people intensive. But it's a neat idea. I'd love to keep all the info at a click of the button away sorted by a quick trivial list.

Although I still use the quick trivial for Brewing, baking, etc. I've learned enough of smithing to attempt to find solutions on my own.

Anyhow, just my take on things! Thanks for looking into this big guy!

[Ngreth Thergn]

Making "custom" sorted lists kills the caching on the site, making it MUCH less effective, and harder on the server.

Also, it generates more bandwidth for the server having to do an aditional page request, serve another page with still alot of info.

So making the filtering will cost us more money, and is no longer "quick"

I will still think on it, and I am not refusing to do it yet. Just fully considering the impact.

[greebmushroome]

thanks for thinking about it

(i don't know enough about how the site is set up to argue reasonableness, so i'll just leave it at that!)

well, okay... i don't know the numbers, but one way to look at it is that the full list has, say, 1000 items on it. for the DoN cultural recipes, there are 7 armor slots + 4 bar/sheet subcombines for each tier of DoN armor for each race. so that's 44 recipes per race, and how many races? 10-15? excluding 9-14 of those would cut out a big chunk of the page when it's generated a second time. there would also be old-style and BD cultural cut out, as well, so maybe the bandwidth increase for quick trivial pages would be less than half again as much, maybe less than a quarter again as much (and only for smithing and tailoring).

OR if "show recipes for all races" isn't an option (and certainly not the default -- i think i'd be fine with that), the server would never have to send all the recipes, just the common recipes + one race's cultural. that might actually cut down on the bandwidth of loading recipe quick lists, even if it defaults to the race i'm not interested in, and i have to load another race (so, would 2X a filtered list be less bandwidth than one full list showing all races' cultural armor?). maybe there could be a link on the side that was to the really full quck trivial list, showing recipes for all races, for the rare occasion someone wanted to see that (or maybe "all races" could be an option, but not the default). maybe the best default would show NO cultural recipes at all until someone picks the race they want to add to the list (so, the quick list would be, by default, just the common recipes everyone can do).

okay, enough hair-brained ideas!

-greeb

[Flehmen]

Not that you haven't already thought about this but... once a day pre-sorted lists, heck, once a week.... Put a caveat that you must check the link to the DB to ensure info is current?

To my mind the quick list isn't for the most up-to-date info, but rather a quick check of what might be your next best move or to look for something that might be interesting to make at your level.. so the tried and true combines not the latest breaking new stuff...

Not trying to press the issue, just thinking out loud to watch the little rubber idea balls bounce off the sounding board....

Take care!

[Arfyak Reflux]

Making "custom" sorted lists kills the caching on the site, making it MUCH less effective, and harder on the server.

Also, it generates more bandwidth for the server having to do an aditional page request, serve another page with still alot of info.

So making the filtering will cost us more money, and is no longer "quick"

I will still think on it, and I am not refusing to do it yet. Just fully considering the impact.

Since custom filtered lists would be a bandwidth killer, how about just add a 3rd column as "Combinable by Race/Deity".

example:

Item			|Trivial|	Race/Deity
Brell's fake item	|  126  |	all/Brell Serilis
Human fake item		|  126  |	HUM/all
Generic fake item	|  127  |	all/all
Happy Elf fake item	|  127  |	ELF/Tunare

I know it would be more work adding the column, probably several months worth, but would not eat up the bandwidth. 2cp worth...

I love the quick trivial list and use it often. Thanks for the great work.

[greebmushroome]

Since custom filtered lists would be a bandwidth killer, how about just add a 3rd column as "Combinable by Race/Deity".

they have this. well, not a separate column, but a note by the trivial about race restrictions.

such as:

grandmaster's moonglade greaves 386 HIE

[Arfyak Reflux]

they have this. well, not a separate column, but a note by the trivial about race restrictions.

such as:

grandmaster's moonglade greaves 386 HIE

Ah, I see that, thanks. The problem though is the items made based on deity are not listed as such. Also, though I did not mention it before, but you could then make the Race/Deity list a one click sortable just like the recipe lists. There by solving the problem that originally started this thread (to a lesser extent).