Legacy talk:Cauldron
Fuel-q
Untill proven otherwise, its presumed the fuel-q used with cauldrons don't matters. For all crafting processes that use a cauldron. --.MvGulik. 16:25, 27 September 2013 (EDT)
Ingredient list
Don't see any need for the "ingredient list per item" in the "How To Use" section. Its not really related to how to use the Cauldron itself. If maintained it should be a some Ask query. So there is no need for manual updating of it. --.MvGulik. 17:09, 29 June 2013 (EDT)
Currently there's no property differentiation between components and tools (as in oven and raw fish beeing the same property category) so i don't readily see a way to make such dynamic list. On the other hand i'm thinking of modyfing metaobj to accomodate for that. Need a clear head and some testing for this thou, because it's been a while since i've done anything like that. --Rook 14:30, 30 June 2013 (EDT)
Hi Rook. :)
Mmm. I'm not sure if adding more features to the metaobj template would be a good thing. I mean its already a bit complicated for most (including me, unless I really put some effort in it.). Would this also need a general change to the metaobj include part in the data/object pages?, or do you think this can be done by only changing the metaobj template itself.
Related to the list on the main Cauldron page, are you sure it can't be done by using two linked-up Ask queries. Just something I remember seeing about using a template(with second Ask query) inside a(the first) Ask query (but I did not studied it in detail). Will look if I can find the related pages again. --.MvGulik. 18:11, 30 June 2013 (EDT)
Right, i've been trying to do that right now but unfortunatly it parses only the first value and i can't find a way around it. As for querring using #ask the problem here is that it includes cauldron and clay cauldron in the results, which is not realy what we want. I'll be looking into it next now that i can't figure out neat way for metaobj.(and Hi MvGulik :) ) --Rook 18:20, 30 June 2013 (EDT)
- Ok, here's "semi-dynamic" table. I call it that because every page to be properly displayed in it requires forced objectsreq property assignment, just as i did in the ones i modifed with "cauldron hack" description. Advantage over the current main page list is obvious in spotting which are missing (like river pearl or death's head chrysalis), disadvantages are ugly display (no satisfactory formatting option for multi-valued properties that i could find) and no specific numbers for requirements (like 0.5l or 2 pices).--Rook 15:40, 2 July 2013 (EDT)
(Note from 2021: removed table. It was blank because the objectsreq property was deleted Phaen (talk) 19:08, 5 January 2021 (UTC))
Nice. Even though it has its limitations, it shows some useful potentials to. Will try to take a closer look at this. (Mmm, I probably should put in some time in how to use the mediawiki API.) --.MvGulik. 05:07, 3 July 2013 (EDT)
- Request to others not to try to directly implement this in other sections too at the moment. --.MvGulik. 05:07, 3 July 2013 (EDT)