Marked for crossposting by: books
Message (jump):
<alwinfy> I'd like to ask for some changes to
Campfire.cs's internals. Specifically:
There's a snip of code that goes, display that you eat the meal, roll "tastier than usual" and play a munching sound, bump hunger and apply effects; this recurs about five times. (e.g. lines 1190-1203.) Right now these are kind of scattered and inconsistently written; I'd like this to be factored out into a hook.
Ideally, I'd like to have this snip of code act as a cancellable event (if cancelled, hunger doesn't get reset and effects don't apply; my use case would roughly be adding a 'Kipperware container' that lets you cook a meal and store it for later eating).
If the event was also aware of the ProceduralCookingEffect applied, and context-aware (to differentiate cooked vs recipe vs village meals), that would be absolutely tremendous.I might also ask that when inspired, the "choose an effect" dialog comes up before the "you eat the meal" dialog (right now it appears after 'You eat the meal' does).
This is comparatively minor but (a) it would make a lot more sense for the above 'store a meal' thing, and (b) it's slightly silly to pick the effect of a meal after you eat it, I think.Thanks for your time and consideration!
