Dakota

I know I'm immediately going back on my word here, but hopefully for good reason in y'all's eyes: Making the decision to take the direct action to roll everything in that thread back, unhiding all of the comments, and locking the post to avoid those discussion points spinning more out of control.

Heya, just going to share that I made a comment over here addressing the moderation concerns from this thread: I've gone ahead and unhidden all of the previously-hidden comments and undone all of the snipping that was done. I'm going to lock this thread as to not spark this any further. There were rules broken in the above discussion, but there were also a lot of genuine and fair criticisms that were caught in the crossfire. If you have any concerns about this action, a moderator's action, or a community member, my DMs are open on every platform.

It's definitely hard to address misunderstandings like that once they've spread, so I appreciate the apology. Thanks to you (and others) for coming to me with your concerns about the thread.

(in context of the forum responses to last week's dev blog and the resulting moderation actions) I replied to @moeggz over on Discord, but I'll also just say here - I'm talking with the moderation team here. I do not think that thread was handled well, but I also think the moderator(s) were given a very difficult task considering the many concurrent topic points people were discussing. Just remember that the moderators here are all volunteers and actively spend their time day-to-day working to make this community a better place. Just to clear somethings up: 1) the moderation team (here or anywhere else) have never been "instructed" to keep things positive. I would hope that last year is proof of that. 2) The IG Community team does not take any direct moderation actions and only very rarely weighs in to moderation decisions. 3) The moderator(s) did not delete any of my comments in the thread, as some have stated they did. I think everyone involved is feeling a bit uneasy afterwards, so I'll take responsibility. I should have stepped in and handled it, moving discussion to the proper places, and addressing concerns that were brought up by you all. I did not see any of your responses as malicious or trolling - just frustrated - which is completely fair. Everyone who participates here cares about Kerbal - we know that, so we're working to address your frustrations in a very direct way right now. I know that that's not as solid of a guarantee as many of you are looking for, but we've got a lot of plans - and I'll point towards what I said last June when community frustration became a massive discussion point (much of which is still relevant): I think we made a substantial leap with For Science! and we're working to do the same with Coloines - both in-game and out. Appreciate ya all, Dakota

Just going to repeat that taking branch updates as any sort of sign is a bad idea. We're already trying to set expectations correctly, don't get yourself hyped up because Gwen broke something on one of the builds and we had to throw another one up for today's playtest.

we know! we're eager to share all the awesome stuff we're working on too

They actually reached out to us about doing some things related to the eclipse. The nerds over there are just super excited for Monday and love to spread the news with interested communities. CommNet definitely deserves a solid answer from the team, I agree. Chris (Nertea) shared some of his thoughts last year, but it's become a major pain point for a small portion of the community. I'll see what I can do.

Every communication is met with positive and negative responses. The share varies, but there's always going to be contrasting voices. Each platform has its biases, but also remember that the majority of players don't actively engage on the forums/reddit/discord/etc. We have to take that into consideration when judging sentiment response to actions as well. I told Mike earlier today that I guessed that this dev blog's sentiment would have be 40% positive, 30% mixed, and 30% negative - and I think I was right. Definitely agree with this. Would rather there be critical responses to our work than nothing at all. Y'all care about Kerbal and the future of KSP2 and it shows! --- Mike and I are working on it and we think you're going to like the changes we plan to make. But keep telling us what you want - what you want to know about, who from, in what form, etc. It really helps

If you're all hyped up about eclipses, check out our latest Weekly Challenge:

Weekly Challenge 51: Capture an Eclipse Total Kerbolar eclipses happen on Kerbin every day, but have you seen one anywhere else? Your mission is to go capture some eclipses from around the Kerbolar system! The occluding body and vantage point are up to you, and the eclipse can be total or partial.

She did not. Mixture of both? We have deadlines and goals and thresholds to reach, like every other game.

yes, i'll get this fixed.

ahh uh don't trust this.

I've admitted before that the K.E.R.B. is not a perfect system. Upon launch last year, there were like 5 avenues for bug reports and no workflow for actually processing them for internal use. The system we have today was built as a stopgap between then and some point in the future when we can either do K.E.R.B 2.0 or some other new system. It has its problems, but the high quality bug reports submitted have helped production a TON during the bug fixing process. I hear your concerns and am working on it! also yes the search sucks, can't do much about that...

Sure. Courtesy of @The Space Peacock Standard_Banana.json

Just giving you all a heads-up that there is a Dev Blog planned to go out on Friday! Am going to set the expectation that it's not about colonies, but we should have news to share about colonies soon.

April Fools from all of us at Intercept

Alright, we hear you - imperial isn't as precise as you'd like it to be! We've gone ahead and changed our plans in accordance with your concerns. Our imperial units will now be calculated up to 20 significant figures. Unfortunately this has led to a 50% reduction in overall performance.... But we know that it'll be worth it for you all Hope that helps!!!

I went ahead and created a new subforum to organize discussion about this project - but I'm going to make it opt-in. If you are interested in contributing, please say so here or via DM and I'll give you permission to see the subforum. I've done ahead and added a few of you who have already shown interest, you should be able to access it here.

For those of you looking to contribute, I'd recommend adding to the Fandom wiki for now - and then once we have a plan in place we can move everything off of Fandom. Re: mediawiki extensions, we can look at anything y'all think would be helpful. -- To help get organized, would it be useful to start a subforum here on the KSP forums?

pls

This week we're going to be pushing jet engines to their limits! You'll be trying to set the highest speed (surface) and highest altitude (above sea level) records for aircraft powered by each of the jet engines: the Whittle, Wheesley, Panther, Goliath, and Whiplash. No rockets, no boosters, and yes, no Rapier allowed (not even in jet mode). Your record-setting vehicle must: Carry at least one kerbal pilot, Take off horizontally from the runway, and Land on the runway and be recovered intact after its mission for the record to be valid. The altitude and speed records are not limited to level flight! You may climb or dive to attain higher values... just remember to pull up in time!

I agree, didn't really mean locking it down and making it read-only. I'll see what I can do about this.

Bugs are still a focus. At an undecided date in April.

Hi all, When we first released the K.E.R.B. we talked a good deal about how it was to be an experimental project - wanting to iterate and improve the usefulness both to the internal team and to you all over time. Being so focused on Colonies development, the team has decided to move K.E.R.B. reports, for now, to a monthly cadence instead of the biweekly you've been used to. Post any release the K.E.R.B. has been incredibly useful for helping us identify top issues and steer our bug fixing priorities, while also communicating about those issues that mean so much to you all. We may return or change to a different cadence in the future, but this is what we believe is best for now. The K.E.R.B. has acted as one source of truth for many of you and we know that this probably feels like us taking away another source of information about KSP2's future. As we move into Spring here in Seattle, we will be sharing more about Colonies' development progress, bugfixes, and potentially some other things you can look forward to. o7 Dakota