What feature would you like on EQTC.

[Doremi]

I'd like to request a way to flag items as having UNKNOWN components, then provide a way to limit searches to items with that flag set. This would let us fill in gaps in the DB more quickly.

[elemer]

Okay well here's my 2cp worth of an idea.

Seeing as there is a forum user database, and then there is the recipe and itme databases.

What about something along these lines:

The ability to add recipes to "Your Recipies Book", a personalized list of favorites.

Combined with the ability to "Print Book" that would create a printer friendly version of your 'book'

Maybe limit the number of recipies that you could have in your book at any one time to keep over head low.

Also maybe have the option to auto-add sub-combines.

Lastly maybe have hot linked site favorites for quick add, say all the recipies needed for the PotC quest in one quick link to add to your book. Or all the ones for the shawl quest for instance.

Anyway, just a thought.

[Krazick]

Elemer,

The thought has some merit. However, the PhpBB Forums that EQ Traders use (where you are reading this post), is a seperate Database from the Primary EQ Traders Recipe Database. The Forums DB is not enough under our control to access a user list, and use it in the way you suggest.

Nor does Ngreth/Niami wish to build a user list that is seperate from the forums and need to worry about managing it seperately.

The idea has merit... but it is very unlikely to be implemented anytime soon.

[Sanna]

I'd like to request a way to flag items as having UNKNOWN components, then provide a way to limit searches to items with that flag set. This would let us fill in gaps in the DB more quickly.

I like this idea a lot, but I think the strain on the DB would lag it a lot if this feature were accessable by anyone. but then, i don't have a good idea on how to restrict things without needing a login system, so... /shrug. seems to be a backburner, unfortunately.

-- Sanna

[Ngreth Thergn]

I'd like to request a way to flag items as having UNKNOWN components, then provide a way to limit searches to items with that flag set. This would let us fill in gaps in the DB more quickly.

decent idea, I am just not sure how to get it done. will think on it.

[Ngreth Thergn]

Okay well here's my 2cp worth of an idea.

Seeing as there is a forum user database, and then there is the recipe and itme databases.

What about something along these lines:

The ability to add recipes to "Your Recipies Book", a personalized list of favorites.

Combined with the ability to "Print Book" that would create a printer friendly version of your 'book'

Maybe limit the number of recipies that you could have in your book at any one time to keep over head low.

Also maybe have the option to auto-add sub-combines.

Lastly maybe have hot linked site favorites for quick add, say all the recipies needed for the PotC quest in one quick link to add to your book. Or all the ones for the shawl quest for instance.

Anyway, just a thought.

The main thing is, I have no idea how to play with the VBulliten login stuff... it is now written by me, and I have a dificult time reading it since I am jsut an amature.

As for just doing something on the site, I am avoiding cookies and logins for the site itself.

[Katydydi]

Tribute?

What would be the possibility of adding tribute values to the items list on EQTC?

[Ngreth Thergn]

I am considering tributr still. (leaning toweards doing it) now that it is probably fairly stable.

[Melinia]

Spreadsheets

I'm not sure if anyone else has posted this...
I've noticed various people (including myself) making spreadsheets for the various tradeskills. Rather than these various spreads be spread out then buried in the various boards maybe a seperate thread could be stickyed under the UI Mod board for Tradeskill spreadsheet submission(s). I'm not sure if this would put to much of a load on the boards or not. Just a thought.

[Hissanhi]

Long time lurker with a new toy..

Not really knowing how the dbase builds pages, and of course not looking to bog you down with a MASSIVE project, but I recently joined the growing number of people with a WiFi enabled PocketPC, and much better than tabbing out for research would be a Dbase template configured for pocketPC's.

[Ngreth Thergn]

unfortunately I do not know what html format I would need for that. Anyone have a good coders reference?

[Kaz]

Vendor-Based Recipes...

Probably the single most useful improvement that could be made would be to enable users to quickly identify vendor-based recipes. Imagine how much easier life would be for players, if they could quickly identify recipes which did not require looting, foraging, or heading off to the bazaar.

And I have a VERY simple way to provide this information, though of course you might come up with some superior alternative:

Color coding.

One would not even need a special option (though that'd be wonderful), but simply for the link to each item name to be colorized based upon whether it was vendor, foraged, dropped, or made. With one extra color for items which had more than one way to be obtained.

But I'd be ecstatic simply to have a quick search that produced items whose recipes were simply vendor based. There are few things, as a casual tradeskiller, that I value more than finding a recipe I can put together without having to pay some lunatic 15pp (300pp per stack) for vegetables, or log in my ranger and stand around jabbing the forage macro I wrote, or go fishing, or kill green mob X in zone Y for six hours waiting for a drop or stack, et cetera.

[Krazick]

Well, color coding to distinguish categories of information might on the surface sound like a wonderful idea. However, it is a bad idea from a web perspective to encode useful information. There might be better ways where it might be italicized, underlined, bolded, or stared (asterick[*]) if vendor sold.

However to actually encode that as part of the Query I doubt is something Ngreth is ready to do. It would require quite a few more queries to get one single recipe out.

Then there is the issue of those recipes that have a "tool" that is returned (regardless of success) that would add further trouble. Not to mention the Recipe Tree where you have lower level combines that "could" be purchased entirely, but it would have to bubble-up the tree the fact that item X3 is made from vendor bought items only, and is used to make item X2... add nauseum.

Yes, on the surface is sounds "nifty"... and to be able to avoid the middle-men/women with their exhoribitant markup fees (15pp per vegetable) would save many of us plat. But think about it, the only reason they charge so much for them, is because people with too much plat buy them for that much.

[Kaz]

Hmmm...speaking as a senior web developer, there's nothing wrong with color coding, from a web perspective. In fact, it's a highly useful interface tool. It's also not nearly so difficult as you imply; it sounds like you're envisioning something much more complex than is necessary.

When a recipe is listed, the name and id of each component in the recipe is listed, as is each sub-recipe in those cute little javascript trees. Surely this means that there is a query of the record for each ingredient, and returning the field(s) that would tell us the source(s) is not that difficult.

Unless it would require bringing in whole new tables, this would require almost no new code at all.

And if it did require including an additional table, that's only a few moments to mentally structure, or not even that if one uses (shudder) a graphical tool to create queries. Unless there's a concern for processor load...the addition of another query in an already multi-table query would increase the load, but only a little, assuming a normal sort of table optimization.

I'd even be willing to help with the coding, if necessary...I've been doing professional web development since 1995, database work since 1991, so it'd be little problem and worth the added information benefit, to me.

As for the pricing, I'm as much an advocate of the free market as you can get...but one thing that makes markets work best is information. As it is, there is no relatively easy way for people to avoid using ingredients which can only (easily and in bulk) be obtained via bazaar. The advent of access to information on alternatives will actually (if we assume enough people use your site, and will tell their friends) drive the price down a bit, as the mass production of alluminum broke the international tin cartel in the seventies, high tin prices simply driving manufacturers to alternative 'recipes'.

Essentially, the prices are so high because ubers, who're going to pay 150k for a single Ornate pattern already, don't care WHAT they pay for ingredients...and so they should't. 29pp for silk is no problem for them, a thousand silk to raise their skill still doesn't dent their overall expenses.

But that doesn't mean that the rest of us shouldn't use whatever alternative means of working on tradeskills we can learn.

[Kaz]

unfortunately I do not know what html format I would need for that. Anyone have a good coders reference?

You would probably write it in WML, which is a sort of subset of HTML with some modification. And, of course, WMLScript, which is a javascript spinoff in the same way. There's also XHTML, but I think WML is considerably more widespread.

I'm not at the machine where I do wireless development, so I don't have quick access to the references I've bookmarked, but here are a couple I googled up that might help:

http://www.devguru.com/Technologies/...wml_intro.html
http://developer.openwave.com/htmldo...ref/qkref.html

BTW: I'd like to second the idea of an obvious link to a spreadsheet (or better still, database) of tradeskill info for people to download if they want to construct their own queries. Heck, that way I can just write a vendor-based recipes query all on my own, and not bug you about it.