https://github.com/peterix/dfhack/blob/master/plugins/autoSyndrome.cpp#L331"\COMMAND" Every SYN_CLASS after this will be a dfhack command. Except for a few special arguments, each SYN_CLASS will be one argument.
Special \COMMAND arguments
"\LOCATION": The next three arguments passed to whatever command are the x, y, and z coordinate of the work tile of the building which triggered the reaction.
"\WORKER_ID": The next argument passed to whatever command is the id of the worker who did the reaction.
"\REACTION_INDEX": The next argument is the index of the custom reaction, as used internally by DF.
Special arguments that must be given BEFORE \COMMAND, (or without any \COMMAND at all)
"\WORKER_ONLY": When present, add the syndrome to (at most) the worker. Still check if the worker can be affected based on SYN_AFFECTED and SYN_IMMUNE stuff. When absent, try to add the syndrome to all units in the workshop.
"\PRESERVE_ROCK": When present, do NOT delete the rock that was created by the reaction. When absent, do delete it (prevents it from being inhaled conventionally).
"\ALLOW_MULTIPLE_TARGETS": When absent, any number of targets may be affected by any syndrome (as long as they are influenced according to the SYN_AFFECTED, SYN_IMMUNE, and WORKER_ONLY rules). When present, at most one unit can be affected by the syndrome.
Allow multiple targets bug: if you don't have WORKER_ONLY, it could plausibly affect both the worker and somebody else in the workshop.
Allow multiple targets design flaw / bug sort of: Leaving out allow multiple targets basically means that only one syndrome per the entire reaction can affect anybody. This is probably not what people would want in the case that they want to affect exactly two units
, or make one thing happen to every unit, and one to just the worker, etc.edit: It's only a problem if you have two or more syndromes that leave out allow multiple targets.
Author
Topic: DFHack 0.34.11 r3 (Read 1457876 times)