new tool: autocheese #1374
new tool: autocheese #1374
Conversation
|
pre-commit.ci autofix |
for more information, see https://pre-commit.ci
| ## New Tools | ||
| - `fix/stuck-squad`: allow squads and messengers returning from missions to rescue squads that have gotten stuck on the world map | ||
| - `gui/rename`: (reinstated) give new in-game language-based names to anything that can be named (e.g. units, governments, fortresses, or the world) | ||
| - `autocheese`: automatically make cheese using barrels that have accumulated sufficient milk |
There was a problem hiding this comment.
needs to be moved up to the current version
autocheese.lua
Outdated
| for _,workshop in ipairs(df.global.world.buildings.other.WORKSHOP_FARMER) do | ||
| if | ||
| not workshop.profile.blocked_labors[df.unit_labor.MAKE_CHEESE] and | ||
| #workshop.jobs == 0 and #workshop.profile.permitted_workers == 0 |
There was a problem hiding this comment.
what if the permitted worker is free to take the cheese making job?
There was a problem hiding this comment.
That is a good point. While having a dedicated cheese maker sounds strange to me, the tool should probably not fail if somebody does this, or otherwise assigns dedicated workers to all farmer's workshops. However, unless the dedicated cheese maker is kept on standby, there will be cycles missed; the approach taken inherently requires the unit to be assigned at the same moment as the job is created. But then, I suppose there is no harm in missing a barrel at 50 units and only creating cheese once you have 60 or 100.
Co-authored-by: Myk <myk.taylor@gmail.com>
- check that barrel can be brought to workshop - handle workshops with assigned masters
|
Didn't have a whole lot of time to actually play/test tonight, so only did some minimal testing before pushing. |
|
I'm not sure the merge was necessary, but I merged locally anyway. I also quickly checked that it still works with v51.02 |
2 participants
No description provided.