Poll on Quick Trivial List

[Ngreth Thergn]

I will NOT make a "switch" for the quick trivial list to turn off or on including race/class specific tradeskill combines from it.

So

Alchemey, Poison Making, and Tinkering would not change at all

For the rest...

Would you like to see me

1. Leave it as is
2. ALWAYS turn off race/class specific tradeskills.

There are no other options

[Neebat]

I think it's useful as is, with the race/class restrictions shown on the right. It would be LESS useful if it left out all those recipes. I just looked at the fletching list. It's bloated with many identical recipes too and cultural filtering wouldn't help it at all.

If you want to upgrade the quick trivial to make it more useful, here's my recommendation. List extremely similar recipes only once. Add a database column to each recipe to list which "recipe group" it was in. All recipes in each group would be similar with the same trivial. The quick trivial list would leave out recipes that were part of a group and list a link to the group instead. Examples of some groups for a few tradeskills....

fletching - class 2 wood hooked arrow group - trivial 102
class 2 wood hooked arrow (small groove)
class 2 wood hooked arrow (medium groove)
class 2 wood hooked arrow (large groove)

tailoring - journeyman's swatch group - trivial 62
journeyman's duskwoven swatch
journeyman's stargazer swatch
journeyman's longstrider swatch
journeyman's driftwalker swatch
journeyman's sagacious swatch
journeyman's runeseeker swatch
journeyman's vah anima swatch
journeyman's starglow swatch
journeyman's metalofiber swatch
journeyman's reaver swatch
journeyman's lorekeeper swatch
journeyman's bloodpact swatch
journeyman's moonsilver swatch
journeyman's mistwoven swatch
journeyman's brambleborn swatch
journeyman's shadowrise swatch

smithing - Plate Armor Dye Group - trivial 36
Way too many recipes to list. Even if you broke this down to individual armor slots, it would still decrease the size a LOT.

There's some data entry/generation to do for that and some new SQL, but I'm sure it's possible. Up to you to decide if it would be worthwhile. I'd find it very useful.

If that's not what you want to do, please leave the list as is.

[Amaruk]

I would say turn off the race/class specific ones but you would need to be carful with spell research. Those are ALL class specific expect for the hybrid/wis spells.

That or go with Neebats idea. The smithing quick trivial list is just about useless and I would hate to see how much work it generates for the server.

[Lanthorny]

found the quick trivial list to be the most useful way to find recipes to help with skilling up - and being able to see my cultural options much faster than in other ways was much better and more convenient. (especially smithing and tailoring)

So for my 2c keep as is

[Ngreth Thergn]

I would say turn off the race/class specific ones but you would need to be carful with spell research. Those are ALL class specific expect for the hybrid/wis spells.

That or go with Neebats idea. The smithing quick trivial list is just about useless and I would hate to see how much work it generates for the server.

Actually Neebats way is MORE work Both for the server and for us mods to go in and modify 15k recipies...

[Konjure]

I went with keep as it is, I think it's great.

That said, might be useful to have two "Quick trivial lists". One for generic recipes, and one with only deity/race restricted recipes.

[Neebat]

Actually Neebats way is MORE work Both for the server and for us mods to go in and modify 15k recipies...

I hope I was clear on that, but it's possible some folks missed it. My suggestion does mean some work. There's 3 specific considerations:

1. Database load would be bigger than the current query. A well structured query should make it fairly light on the database, but regardless, it WILL mean a bit more load on the DB.

The quick trivial list has ONE parameter, the tradeskill. That means the result can and should be cached. I always hoped it wasn't redoing that query every time the page displays. If it's only happening once every 10 minutes, that's not a big deal. In fact, if the results aren't cached now, add a cache and you may find the quick-trivial list returns 100 times as fast, even with a query 10 times as complex.

2. Coding it will take some time. There's two new queries. There's a new page or a new mode for the search page which searches by Group. Programmer time is always more expensive than CPU time.

3. The group field needs to be set. You don't need to do all the groups at once, especially since some recipes don't even fit into a group. (Some items even have unique trivials.) Eventually, for the new code to have any benefit, many recipes should be put into groups. That's data entry work, though you can probably do some clever scripting to do many of these en masse.

[Elyssanda]

Id prefer without racial recipes.. those can be found under the racial lists can't they? with so very very many new racial things, it would make life ALOT easier for general tradeskilling quicklist o be something that is ACTUALLY Quick and not 7 pages long with 3-4 of those pages be somethign I cannot use.

[Taadieri]

The main reason I voted to exclude cultural is that all the old-world cultural are identical for everything in a set.

It is easy to look those up under cultural listings and really clogs up the smithing and tailoring lists with dozens of identical items that the player can't even make.