TriggerAu

workin on that over the christmas break

The teams gone to town in polishing off the Δv bits for the simulation and display so that's all possible - is why there was the indication last time of giving it some time before modders should hook into that feature. In short you can "adjust" (all right disable) the Simulation and App, there are more hooks to control the simulation and performance, and the UI components all (we think) have overrides in the right spots so the components of the display can be reused by mods as well Hey I ressemble that remark! That cleanup was a great effort all round and helped to focus some important bugs to the top of the pile yeah. It was massively appreciated. Hopefully the reminder of the voting system helps more people to share what they care about to bring things to the top again.

Thanks @taniwha

And I responded, the process gives everyone more time to finish, find and fix things. Please hold the head shaking for a couple of releases and see how we go

Glad your liking em, the art guys will be glad to hear it Unfortunately for your question though thats one of those question that I can neither confirm nor deny - I wish I could, sorry

The Zip file on the store is now updated with the OmegaDeprecated folder removed

On the Store Zip file the ΩDeprecated folder should not be there and is causing some issues If you delete just that folder then things should come good as a workaround - we are working on a new zip as I type

roger, looking

Ones where it was a direct replacement have the same part names yes

The previous mk1Pod is still there in GameData, you could unhide it if you want to return to it, we also stored a number of the deprecated parts in GameData/Squad/zDeprecated for those interested

I think I kinda sorta answered that in one of the previous ones. Its aimed at improving a number of things to give people more time (which includes testers). I know I've had fun trying to do stuff in mods (hacky or not), but its always been good to be able to reach out to a dev to look at/ask questions - its one of the great things in our community for a long while

I didnt quote all the direct posts above as that would probs make this a bit too linky... On the release stuff, for myself the best I can hope for is that you all see improvements as we go in this process - its obviously not something we started this week, but the first release you will see from it Even outside of the number of releases question we've been very aware and careful of API and part changes between releases for a while now to try and not introduce issues that cause pain/work. If you look at 1.4.x there were 6 releases and only one needed mod recompiles in most cases - that was primarily due to the engine version change not API changes. I obviously cant speak to private information, but things like discussions around the best way to implement things always includes whats the impact on existing games, mods etc as part of the decision making process - same as severity and impact are part of bug discussions. Having less frequent releases (which is what this plan gives) means more time for modders, testers, artists, devs... everyone to do any work they need between releases Id be dumb to say that this new process will make things perfect, and I do know theres a lot of history in this game, its releases and mod impact. There is always a risk with any update, but I like to think that with the new processes, the frequnceny and the sharing of our plans its giving more to the community.

There are some very complex mods out there yes. The previous release history was 6+ releases a year, this process is designed to reduce that number and give some more info around timing etc to help everyone. I wrote a bit more on that earlier:

Those are good points for sure's, the second one is one of the reasons we've been working to better this for sure For the first one there's always room for improvement, and its a good note - we do have a number of modders in staff/test team, but you can never have too many

Im a Ninja! - woohoo