Messages

I can confirm. I play on a 1920x1200 Laptop screen and had to scale UI as well (1.5x size, pixel based scaling is not ideal, I hope Tynan can do better).

-> Rimworld tends, maybe in entering a new game, to set resolution to 1280x800.

The tutorial should work. Could you please give us more details? Why wasn't it possible to build a cook stove? Can you reproduce this bug?

Now I tried a second time, placed it as before and it was built. Also cooking was possible. Cannot tell why it wasn't built before. So, let's forget my report. :-|

I tried the tutorial in A16. It wanted me to create a stove in the house. For some reason it was not possible to build. But tutorial only wants me to make a meal and allows nothing else. So I couldn't undo the planned construction and construct somewhere else - had to stop tutorial.

Don't even need to create a temporary storage, just ignore the workshop folder, that's the temporary storage. Just read the mod versions for updates.

Now this is interesting. I was thinking about manually syncing the workshop folder (Steam\steamapps\workshop\content\294100\) with Rimworld\Mods. So I tried it.

- In Rimworld you see both, workshop and nonworkshop mods - workshop mods have to be disabled via UI
- Even though the folders are named like "705924057" - Rimworld UI shows the mod name properly
- Rimworld\Mods does not like empty folders
- Rimworld\Mods does not like the folders with the .rsc files (Scenarios)

So for me, I see a 1-click syncing whenever I decide to update mods. And still have the convenience of the workshop. PS, xcopy /s does not copy empty folders IIRC

But that doesn't change that Valve shouldn't take away the control from the user.  Both parties (developer and user) should have a say as to when an update happens.  The developers get this say by publishing an update, the users should get a say by whether they choose to update.

Exactly this. User should be able to decide for a per-application or global update setting (do, don't, use recommended). Modders should be able to transport a recommended auto update setting with any release. It's correct, modders cannot always know that they break saves. But they still are the ones who recommend an update strategy, because, who else.

Haha, transgender again, it's a thing I heard.
Can we discuss "violence is not a solution IRL and ingame"? The Munich attacker played Counterstrike, our minister of interior will put computer games on the agenda.

Please Tynan, hurry up, make Rimworld a teletubby land for distribution in Germany. With purple ponies please. And as we are morally so inferior, for anybody on earth. TIA, scnr

Hey guys, thanks. So it's like in ArmA (there old/saved variables etc. would have to work in the new mod code): I have to weigh it up. Persistent gameplay, long-term saves-> more conservative modding, i.e. manually.  No important saves: workshop is possible.

All in all workshop + mods is generally useless for me. I wish Steam sometimes had more proper ideas. They have so much money. E.g. a UI where you can stop mod auto updating. Or a per-mod option. Or mod developer can make initially set a prefered update setting for his mod. Or something even deeper...

OK, maybe I find the discussion/the result of it.

Hi guys, especially those deeply into Rimworld, I am not... While I like the Steam workshop integration, I'd like to know if the auto updating of mods is a problem for savegames. Never? Sometimes? Often? Always?

I have only deep knowledge about modding in the ArmA world, and there it is necessary to rather choose a semi automatic update way. I.e., has to be reviewed by me. There I will never choose workshop for mods, savegames are in danger.

TIA

When will AAA companies will understand that players want quality games and diversity, not marketing campaigns ?

Well it least I hope decreasing numbers of players get blinded by cutscene marketing. I think more and more companies understand, fancy cutscenes will not help them if they have bad products.
Rimworld is well done and hit Steam at the right time.