Problem is that those variables won't be stored. Recommend using pchar.old_food instead and once you're done with it you can do DeleteAttribute(pchar, "old_food"); .I don't want food consumption disabled entirely for Hornblower, just while he's in prison. And not necessarily for the whole time, just around where the "WaitDate" commands are doing their stuff. For preference, define a new variable somewhere in "quests_reaction.c", then do something like this:That ought to prevent any long term side-effects as well as preserving the player's choice of whether food consumption is enabled normally.Code:old_food = FOOD_ON; food_setting = false; WaitDate("", 0, 0, 1, 0, 0); FOOD_ON = old_food;
Though if you do it within a single quest case, it should work.
Fair enough.That should not be necessary. The ship has enough food and rum to get to where it's going, unless you divert from plot and go off in search of loot and side-quests. In that case you're effectively taking over the ship and may as well take over the responsibility of feeding it.