About the 'flat' table, what causes me a trouble is that there's no limit to the amount of items returned by a recipe, successfull or not,
So basically, we have 10 fields only for the components, with a flag saying if the item is returned on failure/success (typically, for the tools). (say 10 more fields, or even 20) : 20 or 30 fields for the components.
then we have the products, lets start with a maximum of 5 returned products, a field for the item_id : 5, a field saying how many items are returned on success, another field for the failures : 5+5 fields, for a total of 15.
Added : other skills, trivial,skill,id,neededskill.... again a few fields : ~10
we're yet at around 45/55 fields, and are limited to 5 returned items.
To this, we still have to implement the race/class/god/town limits, as we won't have any lookup troubles with this, the table i suggested still works in the case of a flat table.
All this is why i didnt suggested a flat table. My opinion is that we should avoid to implement stuff if yet when we do it, we see where the limits could be. This will prolly allow to create all the live recipes but limit custom ones.
|
Threaded Mode
