Ring of Brodgar Wiki

[ricky]

Azrid is always the first to post new content. he probably has like 500 pictures, maybe he can lend a hand.

[MagicManICT]

Well, the question then becomes: how does this affect our FEP Table?

I'm working on a prototype layout on my user page on the wiki. http://ringofbrodgar.com/wiki/User:MagicManICT
Second or a third material can be added in if need be. Other option is to lay it out like the FEP Table, but that may be wide for an item page.

[tirioll]

I am eager to help with variable ingredient foods.

Indeed people have posted pictures of new foods, usually in announcement threads. But many foods changed with addition of Will, so those older screenshots need to be verified.

As for format, I would propose keeping infobox as it is and having there FEPs that show up in tooltip: kind of average FEP one can expect from this food, which will go into aggregated table. And each food page should have specific table. Here's my idea of the format (yes, maybe too wide...):
http://ringofbrodgar.com/wiki/User:Tirioll

[MagicManICT]

Yeah, tirioll, that's exactly what I'm thinking of as the other method from my suggestion. I'm not sure which is best.

As far as the infobox... not sure how this will fit.

[ricky]

I've wrestled with the idea, but to be quite frank, the nature of the variable FEP makes it nigh impossible without _extensive_ testing by players to match all the proper FEP variables, and as the community stands, we can barely get players to help out on the wiki as it is

For instance, Tuber Mash.

It requires 3 of any mushroom and 1L(?) of milk.

we start by documenting each mushroom type at 100% of one mushrom and 100% of one milk type, already we're at 20+ combos from three types of milk and 6 types of mushrooms
From there we could start evaluating each 100% mushroom value with 50% milk values, which is another 40+ combos from the 6 different milk combos
From that point we could start evaluating different mushroom combinations (!!!)

as it stands, we should probably keep the infobox with the base FEPs, and perhaps try and pinpoint what each food type does, but judging by some Recent evidence, even trying to ascertain even one base variable could be very tedious.

[Glorthan]

Yeah after seeing that thread my enthusiasm to map the different recipes was rather stifled

[Ysh]

I've wrestled with the idea, but to be quite frank, the nature of the variable FEP makes it nigh impossible without _extensive_ testing by players to match all the proper FEP variables, and as the community stands, we can barely get players to help out on the wiki as it is

For instance, Tuber Mash.

It requires 3 of any mushroom and 1L(?) of milk.

we start by documenting each mushroom type at 100% of one mushrom and 100% of one milk type, already we're at 20+ combos from three types of milk and 6 types of mushrooms
From there we could start evaluating each 100% mushroom value with 50% milk values, which is another 40+ combos from the 6 different milk combos
From that point we could start evaluating different mushroom combinations (!!!)

as it stands, we should probably keep the infobox with the base FEPs, and perhaps try and pinpoint what each food type does, but judging by some Recent evidence, even trying to ascertain even one base variable could be very tedious.

This do not need to be done all at one. Build it, and they will come.

[tirioll]

I didn't know that (bat, chicken) is not the average of (bat, bat) and (chicken, chicken). In this case these data are really massive. Some kind of automation is needed to make this viable.

Maybe some of the inhabitants of the Wizards tower could code up an extension button that would allow to click on food item, and have it's parameters converted to q10 level and appended to a log file in some standardized format? The most boring part of it is not to craft all possible combinations of food, but to calculate q10 equivalent and to manually write values somewhere.

[MagicManICT]

Not a bad idea for making it easier. A simple CSV file with a parser is plenty.

There has got to be some underlying algorithm to the design. I don't think they hand-coded every single food item in the game and combination. We demand !!SCIENCE!!.

[tirioll]

There has got to be some underlying algorithm to the design. I don't think they hand-coded every single food item in the game and combination. We demand !!SCIENCE!!.