nome

This is something that's on our todo list, but not near the top I'm afraid.

@CharlesB says they should be fixed already (pretty recent), can you confirm they're not @GorilaInvisible / @Marco BR?

Nope, probably just a bad deploy.

Add one more baby and get rid of the tie and it's not far off my actual family.

People who logged in during a very short window a little over 24h ago had multiple accounts created, and a subset of those then randomly got the wrong one when the bad code was removed. We've introduced new code to try to pick the right account for people, and we'd appreciate it if everyone afflicted could confirm.

Not quite random. People who logged in during a very short window a little over 24h ago had multiple accounts created, and a subset of those then randomly got the wrong one when the bad code was removed. We've introduced new code to try to pick the right account for people, and we'd appreciate it if everyone afflicted could confirm.

There was a period after the PS4 build went live where the skins weren't weaveable, because the server side that lets you weave didn't go live until after, to make sure people had access to the new build with the new art before we started giving them the new skins. That said, right now as far as I know it's live for everyone on all platforms. If you do a reboot now and _still_ can't weave it then something's wrong. We're able to weave on our end using the production build. Please let us know, if it's still broken for you we'll definitely look into it further! Edit: OP says it's fixed, guess that's what it was.

Actually that particular hurdle is one we cleared recently, when we introduced the Klei Accounts page that you can log into via PS4/Xbox (this was the big blocker that kept us from doing it earlier). Thanks to @YormanA it's now just a regular difficulty todo item.

If one of the meme-makers doesn't post the nome-signal shining a potato cup into the sky soon I'll be very surprised.

We had a process that was upgrading older accounts to a new format in the background. It was set to a very low priority and @Diabu watched it carefully for the first few days to make sure it wasn't impacting users. Sadly it appears that it was running just an infinitesimal smidgen over the capacity we had to spare, causing secondary indexes to fall behind just a little each day. Finally that exceeded a limit and requests to those indexes started to fail. To make it worse, since it happened in the middle of the night and nobody had done anything dangerous lately nobody was actively watching it, and our automated systems did not catch it because sadness. Luckily @YormanA happened to notice it and brought it to my attention, I disabled the background process and we then waited for the secondary indexes to catch up. Big thanks to @Zillvr who pushed the emergency-wake-up-nome button! Sadly it was a few minutes after I saw Yorman's message but had that not been the case he'd have been the guy that saved us all from a whole night of DST downtime!

Should be fixed now, sorry for the inconvenience folks!

It takes effect the next time you launch DST. No, we don't control steam, we can only do what their APIs allow.

We've been getting a lot of people turning on inventory hiding and then sending support requests asking why their inventory is not visible on steam. Can you tell me, do you know how we could make this easier for people in the future? Is it not clear what that checkbox does, and we need to improve the language?

50s is ridiculously bad. Is it consistently exactly 50s, or occasional spikes of that bad, or what? If it's occasional the culprit is likely packet loss/bufferbloat, which comes from your network being congested. That could be your wireless (if you're using wireless) or your internet itself (if other programs are maxing out your bandwidth). There are a lot of resources available to diagnose this kind of issue if that's the case.

Go to https://accounts.klei.com and make sure the "Hide inventory" button for DST is unchecked.