Intro
We have been on 1.X forever. Initially we said, Frontier Defense would be 2.0 but while there has been massive progress1, it seems that Verified Mods / Mod-auto-download 23 is gonna be the defining feature of 2.0.
In fact given the recent progress, we might even be able to get it in before the next Northstar anniversary
So turns out Frontier Defense also made a huge jump recently with jump links in navmeshes being fully reversed. While there's still finishing touches to be done on jump link generation, we are getting really close.
At the same time, there's a few other changes happening that will result in some form of breakage compared to previous releases.
This means we can combine both the big feature release (Frontier Defense) with the breaking changes to get a true 2.0 :D
Upcoming changes
Roadblocks
Before we can consider a bump to 2.0 we need to figure out and eliminate potential issues that could interfere with the version bump. This includes:
Other
We might also wanna already consider if we need to do anything else for a 3.0 when Frontier Defense releases
Intro
We have been on1.Xforever. Initially we said, Frontier Defense would be2.0but while there has been massive progress1, it seems that Verified Mods / Mod-auto-download 23 is gonna be the defining feature of2.0.In fact given the recent progress, we might even be able to get it in before the next Northstar anniversarySo turns out Frontier Defense also made a huge jump recently with jump links in navmeshes being fully reversed. While there's still finishing touches to be done on jump link generation, we are getting really close.
At the same time, there's a few other changes happening that will result in some form of breakage compared to previous releases.
This means we can combine both the big feature release (Frontier Defense) with the breaking changes to get a true 2.0 :D
Upcoming changes
Big rpak loading refactor NorthstarLauncher#766->v1.28.0Roadblocks
Before we can consider a bump to
2.0we need to figure out and eliminate potential issues that could interfere with the version bump. This includes:At the moment, server required mods need to match on their major version. As
Northstar.Customis required by virtually every server this means bumping the version number to 2.0 would result in1.Xclients being unable to join2.0servers and vice versa. Even if we decide to not have any breaking features in there. 4So we might want to consider adding an exception to
Northstar.Customor removing version checking entirely and replacing it with a warning in order to allow for a smoother transition from1.0to2.0as while clients tend to update pretty quick, servers are usually on the slower side of things.For mod-auto-download to make a "splash" we need some content for it. This means we should try to get a bunch of mods verified before the public release of the feature.
Other
We might also wanna already consider if we need to do anything else for a 3.0 when Frontier Defense releasesFootnotes
thanks @RoyalBlue1 for the foundations and @Zanieon for carrying on the torch as well as everyone else involved ↩
whatever you wanna call it, I think we change the naming every other day xD ↩
See also
- https://github.com/R2Northstar/NorthstarLauncher/pull/545
- https://github.com/R2Northstar/NorthstarLauncher/pull/595
- https://github.com/R2Northstar/NorthstarMods/pull/761
↩Note that while we adhere to semantic versioning for the most part we don't strictly follow it so a
2.0doesn't necessarily have to be breaking. See also https://r2northstar.gitbook.io/r2northstar-wiki/modding-and-development/development/releases#version-numbering ↩