I don't know how to distinguish between the two options you mention.
Option 1:
- You run the command
- DF crashes immediately
Option 2:
- You run the command
- DF does not crash immediately
- Later, maybe when the MUTATE_RAT_TO_GIANT reaction occurs, DF crashes
The difference is that in the first case, modtools/reaction-trigger is crashing, and in the second, modtools/add-syndrome is crashing.
Anyway, thanks for the save - hopefully it'll help us fix the issue. I've reported it on the tracker, although 0.43.05 is taking priority for now.
It crashes fairly regularly if Roses' attack.lua is used on a spawned creature in 0.43. I circumvented the need for that script in my mod and things seem better, but I still get the occasional crash a few seconds after a creature is spawned. The attack issue might be an anon that changed between 0.42 and 0.43, but the remaining crashes sound to me like an uninitialized value somewhere that is only relevant sometimes. Unfortunately it's a crash-to-desktop so it doesn't leave behind much to troubleshoot. There is nothing in stderr.log after the call to create-unit.
Does attack.lua succeed on non-spawned creatures? And are you saying create-unit crashes even without attack.lua?
No script should be
touching anon fields (although apparently create-unit is one of the few that does). Is attack.lua on Github anywhere? It could be an issue with either script, or both.
(Also, information about crashes in stderr.log is very rare. The last command you ran is probably there, and relevant, but of course you would know that already.)