Right now, regardless of the errors, the game does run fine with no noticeable issues aside from that one awn that got corrupted/duplicated somehow. Even that isn’t a major issue. I just have to change one of his jobs to 1 after every restart and that’s what he does. He makes a good maintenance guy. When I made this list, I got no red errors on startup. The errors came after many hours of play. Currently I’m really enjoying this play-through, so I don’t want to start a new list just yet. Eventually, when this run ends or something breaks beyond fixing, I will start over. I have been taking notes which mods I will most likely cut from the list in the meantime. And I will definitely take your advice into consideration. Some of the current errors I have a pretty good idea how to address or at least where the conflict comes from. This duplicate thing though, I can’t figure out…maybe you’re right in that a clean list will solve that. Thanks again.
By generated and not used, I mean randomly generated pawns that you rejected, for example by re-generating a new pawn. These are explicitly not the same as pawns stored as ‘world pawns’, or those still in the list.In generating pawns, Prepare Carefully requests work priorities (I’m still not sure why), which then triggers Work Tab to create those priorities and keep track of what pawn they should belong to. Prepare Carefully subsequently discards those pawns, but never marks them as deleted – it just removes them from the games’ list of pawns.Upon saving, Work Tab saves it’s priority data with a reference to these pawns, but the game doesn’t save them. On the next load, Work Tab tries in vain to resolve the reference, but the pawns are gone forever.The problem here is that Prepare Carefully assumes that it’s the only mod that needs to know what pawns are active, and doesn’t conform to the standards set by the game (i.e. marking pawns as despawned/deleted).
could you post a screenshot or two? I’m not sure what you mean. The tab should take all available horizontal and vertical space if needed, and add scrollbars if there is no more space available. Note that you can selectively expand individual columns by CTRL+Clicking the column headers. Ok, so the yellow warnings and null-refs upon the first save/load are a conflict with Prepare Carefully, and this happens because prepare carefully doesn’t correctly dispose of pawns that are generated but not used. I have not encountered the second effect you describe; ‘The bug is so huge it will delete all pawns left behind and other pawns generated in the world.’. If true, that would really be a bigger deal. I don’t really see how this would be possible, as work priorities are saved separate from pawns (which is why the first problem exists in the first place), but if you can reproduce the issue I’d love to have a save game and/or detailed reproduction steps.