Due to how important satiations and their management have become, I'm considering adding this page to the sidebar and removing the food satiation table from the FEP Table Page. Thoughts?
--Ricky (talk) 23:05, 25 June 2019 (EDT)
Ricky>"removing the food satiation table from the FEP Table Page. Thoughts?"
It's important knowledge in tables where you can compare results, and i agree that we should consider to make a good tool for that. Current implementation is better than nothing - but for my thoughts, we need to create some index similar to lp\hour, exp\hour, etc, to sort it properly. No idea yet.
Also: Some food depends on few satiations, but not satiate all of them, simple example - sausages. They usually satiate sausages itself or meat, but most of them depends on both.
So the good point is somehow add on pages or somewhere else which sat are work with each food, it's another hell amount of data collection, but i'll find the way.
--Kitsuneg (talk) 07:11, 26 June 2019 (EDT)
How about add columns with attribute like in FEP table? Need more columns for the God of columns. For that? Because is it second thing what i want to see after look food in sat group. Third is FEP/hunger efficiency.
Also Ricky said: 'and removing the food satiation table from the FEP Table Page. Thoughts?' I thing it bad idea. In a FEP table page i can sort food to attribute in one big table without needs to expand each category. thoughts?
--Zadness (talk) 15:48, 27 June 2019 (EDT)
>"how about add columns with attribute like in FEP table"
@Mvgulik: Would it be possible for you to add a "Average satiation per food item" property to your new templates? which would be sat chance * sat effect
For example a food item that has 50(.5) chance and 25(.25) effect would be (.5*.25) = average 12.5 units sated per food item
Would be a wonder addition to the sat tables
--Ricky (talk) 01:05, 28 June 2019 (EDT)
- There are two ways to do something like that. The first, as is used for additional curiosity data, is to save the additional data as property. So it can be included in the basic #ask query itself. The other way is to calculate is on the fly, which involves using/setting-up additional templates (Intro, Outro, and one for row-data processing). Technically you have to do additional stuff that normally is taken care of by the #ask query itself. Was just taking a peek again at how this works (for different reasons). So far it seems a somewhat inflexible process. ... (example case: MvGulik/tmp_row) --.MvGulik. 04:50, 28 June 2019 (EDT)
sat chance * sat effect
I'm kinda wondering if other players find the sat chance * sat effect useful information. The thing is that multiplying a probability with a percentage makes no real sense to me, as such it feels not useful to me. But as I don't play the game itself its kind hard to Judge it potential in-game usefulness. --.MvGulik. 03:41, 30 June 2019 (EDT)
- i'll ask not_a_cat and ppl on discord what do they think. Will report results tomorrow.
- UPD: So people telling me it is good idea and definetly needed - also they suggest another: sat_chance*sat_percent / total_fep for FEP table and leave sat_chance*sat_percent for Food Satiations page - but for my opinion both on both tables would'be useful. Multiply satiations should be just arithmetic product?(not sure how to say this correctly - satch1*satper1+sacht2*satper2/2 i mean)
- ok, recapping ...
- Keep - Satiation table(s) - per satN: sat_chance * sat_percent. Actual used math:
(sat_chance * sat_percent)/100.
- Add - Satiation table(s) & FEP table: sat_chance * sat_percent / total_fep. Presuming actual intended math:
(sat_chance * sat_percent) / total_fep. Probably also divided by some factor of 10.
- or something like:
((sat1.ch * sat1.per) + (satN.cht * satN.per)) / N / total_fep. Presuming N to be sat cases (per item) with data (not blank or zero).
- ... Will first focus on moving the related table-test-code out of user space.
- --.MvGulik. 17:56, 1 July 2019 (EDT)
- Info: Template size overload seems/is mainly related to cell styling. So, for one, the blank cell styling is on the chop-block (no alternative styling solution found yet) ...(Done). --.MvGulik. 02:57, 8 July 2019 (EDT)
Mmm. Looking at Totalfep data. It contains two numbers (fep1 & fep2), Which raises the question which data to use (fep1 only, fep2 only, both(+how?, sum(+), product(*), ..)?. ... (www.mathsisfun.com/definitions/) --.MvGulik. 23:13, 8 July 2019 (EDT)
- Aha, right. Forgot about available code in metaobj. Probably look at cleaning/splitting-off those fep sum calculation codes first. Than see if Totalfep needs some adjusting. Problem with general properties is that they will only store unique data (per page/object). (as can be seen at Bay Bolete page) --.MvGulik. 02:52, 10 July 2019 (EDT)
- Secondary general issue is that there is no guaranteed order to the data pair (Badger Botillo) (underlying reason seems to be data caching behaviour of SMW. (new/updated data is added to end of list)). --.MvGulik. 04:47, 12 July 2019 (EDT)
Fep part added. --.MvGulik. 05:36, 20 July 2019 (EDT)