Homebrew RELEASE NX-Update-Checker

[8BitWonder]

1) When using a 'DLC unlocker' is it needed to use a new updated 'DLC unlocker' every time a new version of the same DLC comes out or a regular game update will simultaneously update the main game and the DLC to its latest version?

From what I've seen DLC unlockers tend to just be for a license type DLC where it tells the game to allow usage of content already in the game.
So if an update is released for the base game it likely updates the content the faked license DLC unlocks, but not the faked DLC license title itself.

2) There are cases where instead of an 'unlocker' a full fledged DLC file is released instead which I imagine happens when the DLC content is not already embedded in the base game waiting to be unlocked or will not come attached later on in a new game update (unlike what appears to happen when you use a 'DLC unlocker' as described above).
Same question here, will new regular game updates keep the DLCs up to date in this situation or only a new updated DLC file will do that?

If the DLC title itself is more than just a license and actually contains new content, my rule of thumb is to update the DLC title if a newer version is known to be available.
I can't say for sure if it's necessary but following that rule hasn't led to any issues on my end so far.

 

[mspy]

From what I've seen DLC unlockers tend to just be for a license type DLC where it tells the game to allow usage of content already in the game.
So if an update is released for the base game it likely updates the content the faked license DLC unlocks, but not the faked DLC license title itself.

So if I understand correctly we can get reports of outdated DLC versions despite them being already up to date with any new content changed in a new version of the DLC, meaning that NX-Update-Checker will not detect the new content because it only looks for the DLC license which remains the same even after you update your base game to get the newest DLC content thus those reports may not correspond to the reality of the situation (basically it's only reporting on the license version and not whether the content itself is up to date or not).

If the DLC title itself is more than just a license and actually contains new content, my rule of thumb is to update the DLC title if a newer version is known to be available.
I can't say for sure if it's necessary but following that rule hasn't led to any issues on my end so far.

When that is the case, do you know if DLC updates are cumulative like regular game updates as in you only need the latest version and can skip any older one even the initial DLC v0 ?

 

[8BitWonder]

So if I understand correctly we can get reports of outdated DLC versions despite them being already up to date with any new content changed in a new version of the DLC, meaning that NX-Update-Checker will not detect the new content because it only looks for the DLC license which remains the same even after you update your base game to get the newest DLC content thus those reports may not correspond to the reality of the situation (basically it's only reporting on the license version and not whether the content itself is up to date or not).

Correct, if a DLC that is strictly a license is updated you'll be told its out of date despite the base game updates handling the actual content being updated.
This is because the DLC title's version is separate from the base game's.

When that is the case, do you know if DLC updates are cumulative like regular game updates as in you only need the latest version and can skip any older one even the initial DLC v0 ?

You should always be fine to use the latest version of a DLC that's cumulative like that.
They don't rely on previous versions being installed since installing the newer binary will just delete the previously installed one.

 

[mspy]

Correct, if a DLC that is strictly a license is updated you'll be told its out of date despite the base game updates handling the actual content being updated.
This is because the DLC title's version is separate from the base game's.

You should always be fine to use the latest version of a DLC that's cumulative like that.
They don't rely on previous versions being installed since installing the newer binary will just delete the previously installed one.

OK thx for the explanation.

So basically we just need to keep an eye whether or not what NX-Update-Checker is reporting regarding new available DLC versions matters or not in terms of being able to fully access/play any new content of the new version of the DLC it detects because we already had it unlocked before albeit with an older version of the unlocker which makes NX-Update-Checker report it as outdated when in practicality it may not be the case.

Isn't it possible for NX-Update-Checker be more precise knowing if we truly need to update the DLC to the new version or do you know of any other easy way to spot if the DLC despite being reported as an 'older' version already is up to date with any new version that gets released afterwards which should happen when the DLC gets automatically updated via a regular game update?

 

[8BitWonder]

Isn't it possible for NX-Update-Checker be more precise knowing if we truly need to update the DLC to the new version or do you know of any other easy way to spot if the DLC despite being reported as an 'older' version already is up to date with any new version that gets released afterwards which should happen when the DLC gets automatically updated via a regular game update?

Personally I don't think there is.
I'd have to be able to detect a DLC is strictly a license, which is a can of worms I don't feel like tackling.
That and if I ignored version updates for strictly license DLC there may be oddball titles that require the updated license DLC, and then I need to make some kind of white list.

Much easier to just update your stuff if you can and know that there's a newer version available.
But if it's just a license DLC you'll probably be fine not updating it. (But I personally would)

 

[aleking10]

Hello there
I have a problem with this great utility:
I run the hb for the first time and it gives me the list of the title to update/with dlc.
Great: I update those games with tinwoo from pc and everything is fine.
After some weeks I run nx update checker again and it gives me the same results from the last time.
I tried to delete the delete the .txt file but it didn't solve the problem.
Of course I tried to delete and install again the hb but same results.
I always have the same results list like the first time, even if the games are all updated.
Any solutions please? Thanks

 

[8BitWonder]

Hello there
I have a problem with this great utility:
I run the hb for the first time and it gives me the list of the title to update/with dlc.
Great: I update those games with tinwoo from pc and everything is fine.
After some weeks I run nx update checker again and it gives me the same results from the last time.
I tried to delete the delete the .txt file but it didn't solve the problem.
Of course I tried to delete and install again the hb but same results.
I always have the same results list like the first time, even if the games are all updated.
Any solutions please? Thanks

When convenient please enable logging and then submit the produced files in a bug report over on the repository;
https://github.com/16BitWonder/NX-Update-Checker#logging

I'll take a look at it when I can.

 

[ShinRaikdou]

Does list with missing titles updated manually? I've noticed some new updates/dlc appears with delay. For an example, update for 010039D015FE2800 still won't show up, but in "Switch library manager" on PC it's there.

 

[duckbill007]

Does list with missing titles updated manually? I've noticed some new updates/dlc appears with delay. For an example, update for 010039D015FE2800 still won't show up, but in "Switch library manager" on PC it's there.

Are you using the same info source?

 

[8BitWonder]

Does list with missing titles updated manually? I've noticed some new updates/dlc appears with delay. For an example, update for 010039D015FE2800 still won't show up, but in "Switch library manager" on PC it's there.

The app pulls from https://github.com/16BitWonder/nx-versions, I update it manually occasionally.

However that title looks like it's already listed in there, update v65536 (or v1 if you shorten).

Are you sure you don't have it already, or is there a v2 out that isn't in nx-versions yet?

 

[ShinRaikdou]

Are you using the same info source?

Can you change them? I use default ones for both.

However that title looks like it's already listed in there, update v65536 (or v1 if you shorten).

It appears my Switch can't download updated list anymore, I had to do it manually. I'll have a look at it later, but it's probably related to my connection, not the app.
Thank you.

 

[Milenko]

I've been getting "[6] Couldn't resolve host name" for the last year when trying to download versions.txt, just switched from 90dns to ams serial blanking and now it works fine