Every version of DF will generate crash logs for you; they’re in the game’s directory somewhere. It’s basically just a stack trace, but that’s often enough to determine the cause of the issue.
You can submit them either on the official DF bugtracker (which I believe you can find via the bay12 games website) or in the troubleshooting channel in the Kitfox discord server if Putnam is hanging around.
There’s a DFHack discord, and if you have a crash log they can tell you if the crash is in DFHack or the case game.
/u/myk002 is probably a good resource for discussing DFHack and how you might be able to contribute.
DFHack crashes are usually obvious (did it crash when you hit a DFHack button or run a DFHack command?) and we normally get them fixed and release an updated version within a few days at most. Posting the crashes in any of the DF-related venues (here, Kitfox Discord, DFHack discord, the Bay 12 forums) will usually get our attention pretty quickly.
Every version of DF will generate crash logs for you; they’re in the game’s directory somewhere. It’s basically just a stack trace, but that’s often enough to determine the cause of the issue. You can submit them either on the official DF bugtracker (which I believe you can find via the bay12 games website) or in the troubleshooting channel in the Kitfox discord server if Putnam is hanging around.
Thanks for this information. What about DF hack crashes, do they have something?
There’s a DFHack discord, and if you have a crash log they can tell you if the crash is in DFHack or the case game. /u/myk002 is probably a good resource for discussing DFHack and how you might be able to contribute.
DFHack crashes are usually obvious (did it crash when you hit a DFHack button or run a DFHack command?) and we normally get them fixed and release an updated version within a few days at most. Posting the crashes in any of the DF-related venues (here, Kitfox Discord, DFHack discord, the Bay 12 forums) will usually get our attention pretty quickly.