\WORKER_ONLY is not a recognized command.
\WORKER_ONLY is not a recognized command.
\WORKER_ONLY is not a recognized command.
\WORKER_ONLY is not a recognized command.
These are harmless, but I should get rid of them. Autosyndrome now *only* targets a workshop user unless instructed otherwise. In fact, the new autosyndrome is *really* sweet, because you can do things like 'only target units inside workshop', so we could do things like replace the existing field-of-view interactions with the stables with ones which only interact with stable inhabitants.
Realistically this means we should also sanity check all the workshops as part of dfhack4 integration.
...ess-unified\Dwarf Fortress\hack\scripts/itemsyndrome.lua:32: attempt to index
local 'material' (a nil value)
stack traceback:
...ess-unified\Dwarf Fortress\hack\scripts/itemsyndrome.lua:32: in funct
ion 'getMaterial'
...ess-unified\Dwarf Fortress\hack\scripts/itemsyndrome.lua:272: in func
tion 'checkAndAddSyndrome'
...ess-unified\Dwarf Fortress\hack\scripts/itemsyndrome.lua:307: in func
tion <...ess-unified\Dwarf Fortress\hack\scripts/itemsyndrome.lua:306>
As Putnam mentioned, this is probably due to dwarves stripping naked when transforming. And on that front, I've integrated Putnam's new itemsyndrome.lua into unified, so if you update these errors should disappear.
~ T