New script: prioritize - monitors job creation and boosts priority for configurable job types #317
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The prioritize script sets the
do_now
flag on all of the specified types of jobs that are currently ready to be picked up by a dwarf. This will force them to complete the jobs as soon as possible. This script can also continue to monitor creation of new jobs and automatically boost the priority of newly created jobs of specific types.This is most useful for ensuring important (but low-priority -- according to DF) tasks don't get indefinitely ignored in busy forts. The list of monitored job types is cleared whenever you load a new map, so you can add a line like the one below to your
onMapLoad.init
file to ensure important job types are always completed promptly in your forts:This implementation uses the
eventful
plugin to hook the creation of jobs so it can automatically modify new jobs. It cleans up after itself and unregisters the callbacks when no tracked job types remain (or when a map is unloaded).