I have concluded that VersionChecker will take considerable work to update for Subnautica 2.0 Living Large, mainly due to the fact that mods for 2.0 will be moving from QModManager to BepInEx.
This changes the way that VersionChecker will need to work under the hood, so it will require a redesign of some of the technical aspects.
I plan to begin work on these changes after Christmas, but please be patient as they may take some time to perfect.
In the meantime, you may still use VersionChecker on the legacy branch as normal.
--- ATTENTION ---
The Subnautica Living Large update - also referred to as the Subnautica 2.0 update or Modpocalypse update - has been released.
This update adds many cool new things to the game, but it also breaks the vast majority of mods, including QMM itself.
At the moment, my main focus is updating my most popular mod - SnapBuilder - for the update. I expect to have it released within the next 48 hours if not sooner.
After that, I will be going through each of my mods and assessing how viable they are in Subnautica 2.0, and how much time it will take to release an updated version. I will post updates here when I can give more information.
In the meantime, if you play on Steam, you can continue playing Subnautica with all of your QMM mods by switching to the legacy branch - i.e. downgrading your Subnautica to the last version which QMM still worked for. You can find the option to switch to the legacy branch under the Betas section of the game Properties in your Steam Library.
Until the new release is ready, I will be locking the comments here.
Most issues are resolved by carefully re-reading the installation instructions or stickies above, but if you have stumbled on a bug, please file a bug report on the Bugs tab with as much information as possible to help us find the cause of the issue so we can get it squashed in an update. Useful information includes examples, screenshots, and steps to reproduce the issue.
I recently updated Tweaks and Fixes to the latest version, v1.30 released July 2. However, the mod.json that ships with this version of Tweaks and Fixes has its version listed as "v1.3". This causes a false report from Version Checker that it's not up to date, as the current version is "v1.30" and that I'm running "v1.3".
I don't know if there's anything that can be done from Version Checker's end for this (T&F needs to properly put the version number in their mod) but I wanted to make you aware of the issue.
As a feature request, is there anyway we can have the update messages saved to a text log somewhere? Sometimes if I get multiple update messages I can't note them all down before they disappear. It'd be nice to have a text file that I could check as a backup.
Hi, unfortunately there isn't anything VersionChecker can do about that - if the version number is entered incorrectly by the mod, it will appear incorrectly in VersionChecker, and 1.3 is a valid version number so it has no way to know that this was incorrectly entered. You could edit the mod.json yourself to say 1.30 as a workaround.
As for a text log, right now you can get this information from your qmodmanager log file and doing a search for the text "VersionChecker" (by for example using Ctrl+F in notepad).
I will note this request for an update to VersionChecker.
Can you try to be more specific? New update? VersionChecker's last release was a year ago. It says that something's wrong? Why don't you write out what specifically it says.
If I had to guess, this is probably an installation issue.
Can you make a mod that, according to the information received from Checker, would update everything that is needed by itself? Or add such a function to Checker?
Not easily, no. It's something I planned for some time, but it's a big job - to get it right is rather complex. And on top of that, it would require each user who wants to make use of the update feature to have Nexus Premium, because they restrict access to download links behind this, unless you visit the site directly.
I may eventually get something like this working, but it's not something I'm actively working on at this time, I'm afraid.
The irony is, I want to release an update that allows you to ignore specific version update messages... But that would be releasing an update too soon... xD
Apologies, I've had to release another update today as a user found a bug in the latest that was informing some users an update was available when it was not.
But yeah, I'm working on a very very big update coming soon, and other than bugfixes, I don't intend to release another VersionChecker update until its fully tested and done.
doesn't work. there's an update to Building Tweaks and Version Checker didn't inform me. seems there's a lot of mod updates i wasn't aware of in spite of this mod installed.
A breaking change was introduced by the Subnautica devs sometime in the last few months, rendering VersionChecker incapable of checking your mods were up-to-date. I'm really sorry I didn't notice sooner, but I hadn't loaded the game in sometime and nobody reported this to me until very recently. I have now released a fix in the latest version, available from the files tab. Sorry for the inconvenience!
This is usually down to a mod author changing mod versions on Nexus mods prematurely, and isn't a fault with VersionChecker which is just reporting the latest version. You'll want to contact the author of the mod directly and they'll be able to take care of you.
As usual, can't do anything without logs. Do you have compatible mods installed? Were those mods up to date? Bc if they're up to date, you're not going to see anything happen anywhere except in the log. It only notifies you in-game if there's an update to a mod compatible with VersionChecker and you're on an old version, and it's not always instant even then due to cache. If you want faster answers, read the stickied post above and go to the Subnautica Modding Discord and provide your log file.
Is there any way that a log file could be created that tells me which mods need updated? I definitely get notified that there is an update but I have no way of telling what needs updated. Obviously not a big deal just curious:)).
When the update pops up in-game, it does tell you what mod needs to be updated as the very first, colour-coded part of the notification.
See the following example where "CustomTunes" is the mod that needs updating.
If you want to see logs, they are in the qmodmanager_log-Subnautica.txt file - if you do a Ctrl+F search for ":VersionChecker]" you should find everything logged by VersionChecker.
Give Feedback
40 comments
Comments locked
The author has locked this comment topic for the time beingI have concluded that VersionChecker will take considerable work to update for Subnautica 2.0 Living Large, mainly due to the fact that mods for 2.0 will be moving from QModManager to BepInEx.
This changes the way that VersionChecker will need to work under the hood, so it will require a redesign of some of the technical aspects.
I plan to begin work on these changes after Christmas, but please be patient as they may take some time to perfect.
In the meantime, you may still use VersionChecker on the legacy branch as normal.
--- ATTENTION ---
The Subnautica Living Large update - also referred to as the Subnautica 2.0 update or Modpocalypse update - has been released.
This update adds many cool new things to the game, but it also breaks the vast majority of mods, including QMM itself.
At the moment, my main focus is updating my most popular mod - SnapBuilder - for the update. I expect to have it released within the next 48 hours if not sooner.
After that, I will be going through each of my mods and assessing how viable they are in Subnautica 2.0, and how much time it will take to release an updated version. I will post updates here when I can give more information.
In the meantime, if you play on Steam, you can continue playing Subnautica with all of your QMM mods by switching to the legacy branch - i.e. downgrading your Subnautica to the last version which QMM still worked for. You can find the option to switch to the legacy branch under the Betas section of the game Properties in your Steam Library.
Until the new release is ready, I will be locking the comments here.
Thanks for reading,
Tobey/toebean
Most issues are resolved by carefully re-reading the installation instructions or stickies above, but if you have stumbled on a bug, please file a bug report on the Bugs tab with as much information as possible to help us find the cause of the issue so we can get it squashed in an update. Useful information includes examples, screenshots, and steps to reproduce the issue.
I don't know if there's anything that can be done from Version Checker's end for this (T&F needs to properly put the version number in their mod) but I wanted to make you aware of the issue.
As a feature request, is there anyway we can have the update messages saved to a text log somewhere? Sometimes if I get multiple update messages I can't note them all down before they disappear. It'd be nice to have a text file that I could check as a backup.
As for a text log, right now you can get this information from your qmodmanager log file and doing a search for the text "VersionChecker" (by for example using Ctrl+F in notepad).
I will note this request for an update to VersionChecker.
New update? VersionChecker's last release was a year ago. It says that something's wrong? Why don't you write out what specifically it says.
If I had to guess, this is probably an installation issue.
Or add such a function to Checker?
I may eventually get something like this working, but it's not something I'm actively working on at this time, I'm afraid.
But please dont update it every 2 days. Because the only update messages I constantly get is about an update of the version checker :-)
The irony is, I want to release an update that allows you to ignore specific version update messages... But that would be releasing an update too soon... xD
A breaking change was introduced by the Subnautica devs sometime in the last few months, rendering VersionChecker incapable of checking your mods were up-to-date. I'm really sorry I didn't notice sooner, but I hadn't loaded the game in sometime and nobody reported this to me until very recently.
I have now released a fix in the latest version, available from the files tab. Sorry for the inconvenience!
See the following example where "CustomTunes" is the mod that needs updating.
If you want to see logs, they are in the qmodmanager_log-Subnautica.txt file - if you do a Ctrl+F search for ":VersionChecker]" you should find everything logged by VersionChecker.