Open RoyalFox2140 opened 12 months ago
Weird. It logically should be doing this for comestibles if they have different calorie values, but not for non-comestible items full-stop.
Also, foods made with different ingredient spoil times even by a few hours don't stack, and I think ingredient temperature matters too. Stacking has so many problems.
could you make this a separate issue as well? the primary reason is that freshness comparison is too strict. could make its laxness configurable but maybe it could slow down things
Items made with such recipes have the NUTRIENT_OVERRIDE
flag added to them, and merging is only allowed when 2 items have same flags (merging is irreversible, so it must be careful about accidentally erasing information).
Maybe we could get rid of this flag on items entirely, only only allow it on recipes? The flag would make it so the recipe does not record components when creating the food item, and food items would calculate their nutritional value from components only if they had components, otherwise they would use the default value defined in JSON?
but not for non-comestible items full-stop.
The NUTRIENT_OVERRIDE
flag should not be applicable to non-comestible recipes in the first place.
Describe the bug
Ever since recipes can ignore ingredients, items made from a recipe that overrides the ingredients does not stack with items found naturally even if the ingredients are ignored. Here's an example for testing purposes. I believe that the metadata on the item must still be recognizing what it is made out of somehow, but I have no idea.
Steps To Reproduce
Screenshots
Versions and configuration
Additional context
Also, foods made with different ingredient spoil times even by a few hours don't stack, and I think ingredient temperature matters too. Stacking has so many problems.