User talk:Eliza Dane

From A KoL Wiki

Hey, I think the 'consistency' we're seeking is the opposite of what you've done to a couple consumable pages.

Having the min and max adventure range can let use automatically calculate average adventure gains (ever since Jick revamped how consumables worked to be sane.) No doubt there are places on the wiki that use the old way, but I think the goal is to switch everything to using separate fields. This might not be properly codified anywhere, so if there's a "standard" somewhere that says otherwise let me know!  :) --Starwed 20:19, 5 December 2010 (UTC)

One of the two forms contains more information than the other (from the point of view of wiki-parsing) so it seems silly to eliminate it. If you really want to change it, maybe bring it up on Discussion. (Especially because, if its decided that a change is desirable, it can probably be done with a bot.) --Starwed 01:14, 7 December 2010 (UTC)


I have read the discussion you are referring to now. To be honest: at this moment I lack the patience required to understand it all. I will avoid to make any more changes of the type that started this discussion, although I think my arguments are still valid: there are literally thousands of range indications on the WIKI of the form "4-6". When I suddenly see "4-6 (average 5)" on just a few of the food pages, that looks silly to me and inconsistent and that was my motivation to change it. In fact, I did not see them, but a computer program that was parsing the WIKI food pages. Eliza Dane

  • This conversation is splitting up a bit over talk pages (and time a bit), but the min/max is part of a larger project to vastly improve the power of the data pages and templates. In particular, the adventure range of a consumable is duplicated in MANY places on the wiki. Not just the item page itself. And any time someone discovers something new about the range, or everytime a change in the game alters a range, we have to update not one page, but potentially dozens to reflect the new information. But by eventually storing advmin/max on the data page, we can pretty much completely eliminate this. One just updates the data page, and then the new data will propagate to all of the other pages. Much simpler, much more effective, and will vastly improve the readability of pages such as the Best Foods pages. The "inconsistency" is just because the project isn't coming out of the gates at full speed. The data pages were recently restructured, and making full use of this requires a lot of data be moved to them and also for a lot of templates to be almost completely rewritten. Rewriting the templates is the big pain. Moving data is something a bot can do, but rewriting major templates in a major way is a touchy business. --Flargen 09:50, 11 December 2010 (UTC)

Thanks Flargen. I am a programmer and I would be able to automatically change all food datapages from adv: x-y to advmin: x/advmax: y and other simple tasks like that. There is one requirement: I need an account that is not bothered by the question "please type the words you are seeing" when a page contains external links. Provide me with such an account and a clear definition of what change you want to be made and I can probably work for the WIKI (it will not always be ready the next day though)