Closed cvuchener closed 4 years ago
If you're able to test easily, is this still an issue? (Note that I have no idea if this has been touched since you opened this issue, although I did poke around at the justice screen on linux64 recently in case that's relevant)
Yes, it is still happening with fd4b705e36d8b90bf8380849fd074672fd6d6f0d.
I don't seem to have a world with spoils handy, but I confirmed the second issue (with crime.reports) as of 8427f518c941f8e5734e98f2ff56648522f1281b.
I found this issues using this save from PatrikLundell.
In crime
, the two integers around the three convicted_hf*
int32s are actually just padding. This may also be the case around victim_hf*
. Not sure what the proper layout is, but I will continue experimenting.
I found this issues using this save from PatrikLundell.
Wow, check-structures-sanity is picking up a lot of issues in this save. Most of them appear to be minor. I'll just focus on spoils_report
for now, but this will be useful for testing (thanks @PatrikLundell!).
The spoils_report issue was an unknown field that was actually just padding, so it didn't exist on i386: https://github.com/DFHack/df-structures/blame/9bf18dfc6647e1ff51deddac9da042baa1655987/df.world.xml#L329 This dates back to 2018, so this was a really old issue - nice catch!
Forgot to link in a106b5e98381184004fa9dfff44072239755e554, but this is fixed now
Tested on linux32 using DFHack/dfhack@e267876 and c0edb62
spoils_report
contains invalid vectors (4 bytes too far?):crime.reports
is invalid (no valid vector visible nearby):