Dakota

If there's anything I can do to help this initiative, please let me know.

Probably my biggest mistake from last year workwise. Had to work to slowly build back the trust lost, but I know I never quite got there for some folks. You live and learn.

Passed these messages among others to the team. A few reactions: Thank you all so much, it means a lot.

Sure. KSP2 threads are currently split between three subforum categories: While KSP1 is under one category (with technical support and mods WITHIN the KSP1 parent category): It's a minor difference but could be important to some so I put it as an option.

Move discussion to this thread.

As mentioned here, letting the community decide how this forum will look moving forward. I've added this poll to a widget on the front page as well. Feel free to use this topic to discuss the decision.

I'll put this up for a vote at the end of this week.

The moderators know nothing more than you already know. Please avoid attacking other members of the community.

Creating that human connection has always been one of the biggest goals of mine as a CM. Fans of the game only become fans of the studio by developing that sort of connection with the team. In my opinion, too many CMs act as some kind of wizard behind the curtain, when really a CM should just feel like another community member. Glad to hear I left an impression and kept you engaged with the community. Thanks for playing our game

This week we'll be miniaturizing, aggressively. You're to build and fly the lowest-possible-mass craft you can that can deliver a kerbal to and return them from one of the following locations: The surface of the Mun The surface of Duna The surface of Tylo The surface of Moho The kerbal must plant a flag and return safely to Kerbin. Make full use of low-mass parts like the grumble seat, Oscar-B tank, Ant engine, and your kerbonaut's RCS pack to perform the maneuvers you need. Screenshot the mass of your vehicle before launch and show everyone how looooow you can goooooo!

we're continuing to look at this as part of the UI/UX developments mentioned in Nate's post.