Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Requirements to be fullfilled before a Northstar 2.0 #600

Open
3 tasks
GeckoEidechse opened this issue Dec 14, 2023 · 2 comments
Open
3 tasks

Requirements to be fullfilled before a Northstar 2.0 #600

GeckoEidechse opened this issue Dec 14, 2023 · 2 comments

Comments

@GeckoEidechse
Copy link
Member

GeckoEidechse commented Dec 14, 2023

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

Problem

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:

  • Version number checks for mods:
    At the moment, server required mods need to match on their major version. As Northstar.Custom is required by virtually every server this means bumping the version number to 2.0 would result in 1.X clients being unable to join 2.0 servers and vice versa. Even if we decide to not have any breaking features in there. 4
    So we might want to consider adding an exception to Northstar.Custom or removing version checking entirely and replacing it with a warning in order to allow for a smoother transition from 1.0 to 2.0 as while clients tend to update pretty quick, servers are usually on the slower side of things.
  • Content:
    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 releases 👀

Footnotes

  1. thanks @RoyalBlue1 for the foundations and @Zanieon for carrying on the torch as well as everyone else involved

  2. whatever you wanna call it, I think we change the naming every other day xD

  3. See also

  4. Note that while we adhere to semantic versioning for the most part we don't strictly follow it so a 2.0 doesn't necessarily have to be breaking. See also https://r2northstar.gitbook.io/r2northstar-wiki/modding-and-development/development/releases#version-numbering

@ASpoonPlaysGames
Copy link
Contributor

Honestly I'd like to get the mod format rework done for 2.0, current system is Not Good ™️ and consistently causes problems and hacky workarounds for things.

Invalidating everyone's mods would also be less of a kick in the balls if its a big 2.0 release

@GeckoEidechse
Copy link
Member Author

GeckoEidechse commented Dec 15, 2023

I'm totally up for an improvement in our mod loading system. Maybe create an issue or discussion for it so that we can hash out the details :D

The only challenge I see is that I'm not sure if we can get it out in time for Northstar anniversary on January 8th.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

2 participants