Modders

Translations and creative content

Hey all. Version 1.0 is now content-locked. That means we'll only be changing it if there's a serious bug to address.It's on the Steam unstable branch. Please, everyone who wishes, take it for a test run! It should be less buggy than Beta 19. We focused on bugfixing, so the only notable new feature is the food restrictions, which you can use to control what people are allowed to eat. If you do find a bug, please report it in the Bugs forum To enable the unstable branch, open your Steam library, right-click RimWorld, click Properties, go to the Betas tab, and select 'unstable' from the dropdown menu.Modders, it'd be great if you could update your mods and make a version for 1.0. In general mods should require few to no changes to work for 1.0 - mostly just a recompile if you're using code.The Beta19 release caused a lot of anger as some mods were updated in-place, while other mods weren't. So a lot of people had their savegames broken, often irrevocably. Heartbreak and anger, and it was pretty justified. As a player I certainly don't expect updates to trash a treasured save with no warning. Even going back to the old version didn't help if a mod was updated in-place to the new version.That's why this time I'm placing the game up content-locked for a period before release, and recommending that moddersIt would be better to upload them separately onto the Workshop, to prevent breaking peoples' games when they change versions. (Many modders already do this but if everyone does, the mod version confusion disaster will be solved).I won't enforce this in any way, of course. It's a request, motivated by a desire to not break that implicit "we won't trash your game" contract with players.(EDIT: Backstory and reasoning why I'm requesting this).I'm still working on selecting an exact release date. But the day is coming closer.Though I hope to not update the code if possible, to preserve compatibility, I will be continuing to update the translations and creative content both before and after 1.0 release. This kind of content doesn't break compatibility. So translators and people entering creative content can continue to enter content without worrying that it'll be left out.