Description
At the moment, it's quite hard to debug patrols, especially when there's an issue with an outcome and that outcome has a low weighting. debug_ensure_patrol_id helps a lot with this, but I'd like to propose an expansion:
debug_ensure_patrol_outcome - allowing you to force success/fail and optionally which outcome you specifically want. Probably should only work if debug_ensure_patrol_id is active.
debug_override_patrol_stat_requirements - allowing you to ignore the location/season/trait/skill requirement checks for debug_ensure_patrol_id so you could force it more often. Wouldn't suggest allowing you to override the age, status and relationship requirements as that could mask or even introduce errors.
Some sort of debug-only patrol suite that aren't present in the main patrol pool, but can be requested using the debug_ensure_patrol_id setting. This would be great for unit testing, as well as general patrol-related debugging. I don't know what this would look like but it'd be super useful if we could have it.
Description At the moment, it's quite hard to debug patrols, especially when there's an issue with an outcome and that outcome has a low weighting.
debug_ensure_patrol_idhelps a lot with this, but I'd like to propose an expansion:debug_ensure_patrol_outcome- allowing you to force success/fail and optionally which outcome you specifically want. Probably should only work ifdebug_ensure_patrol_idis active.debug_override_patrol_stat_requirements- allowing you to ignore the location/season/trait/skill requirement checks fordebug_ensure_patrol_idso you could force it more often. Wouldn't suggest allowing you to override the age, status and relationship requirements as that could mask or even introduce errors.debug_ensure_patrol_idsetting. This would be great for unit testing, as well as general patrol-related debugging. I don't know what this would look like but it'd be super useful if we could have it.