Update:
Four hours of game play and it's going along fairly well. I suspect that an autosave from a previous edition may have been the culprit. I usually only name a file once it's got to a point of surviving most of the difficult raids. So I rely heavily on autosaves for my colonies. It could be that once the game autosaved over a 254a copy the glitch would appear. Thus the confusion over the game version and the error in general.
If that is the case, next time there's an update it might be an idea to include a 'how to remove saved files' readme for those not entire aware of where Rimworld saves to. Or a general 'easy to avoid mistake' file haha.
Anyways seems to work out fine now!
Cheers for the hard work guys/gals
Four hours of game play and it's going along fairly well. I suspect that an autosave from a previous edition may have been the culprit. I usually only name a file once it's got to a point of surviving most of the difficult raids. So I rely heavily on autosaves for my colonies. It could be that once the game autosaved over a 254a copy the glitch would appear. Thus the confusion over the game version and the error in general.
If that is the case, next time there's an update it might be an idea to include a 'how to remove saved files' readme for those not entire aware of where Rimworld saves to. Or a general 'easy to avoid mistake' file haha.
Anyways seems to work out fine now!
Cheers for the hard work guys/gals