Nobody expects from you to use it. You need just one guy with unbanned Switch that will dump it and put it somewhere for everybody to use (like me). And this tool won't ban anybody.Le sigh.
DBI has this in ToolsAlso about that. Switch stores locally info about every newest game update available, excluding DLCs.
Just made a tool for dumping it in the form used by titledb's "versions.txt" here:
I'd still need to rely on others.Nobody expects from you to use it. You need just one guy with unbanned Switch that will dump it and put it somewhere for everybody to use (like me). And this tool won't ban anybody.
That seems like totally overengineered solution. At that point you would be honestly better rewriting the functionality on base of some existing installer.would a sys module that reads the screen and displays translated lines over the original russian app without actually modifying it be feasible?
it would be, if someone with the know how is actually willing to do that. people are very obsessed with using specifically dbi thoughThat seems like totally overengineered solution. At that point you would be honestly better rewriting the functionality on base of some existing installer.![]()
Well because it works the best out of the things I have tried. However if you (or someone else) was going to spend time developing such elaborate translation system, you might be better learning and reversing how to write the installer yourself.it would be, if someone with the know how is actually willing to do that. people are very obsessed with using specifically dbi though
I assume that this info comes by default with every firmware update (even minor ones?) so we'll get all available updates up to that point even if the firmware update is done offline which explains how some games know there is a newer update available and ask for it before launch?Also about that. Switch stores locally info about every newest game update available, excluding DLCs.
Just made a tool for dumping it in the form used by titledb's "versions.txt" here:
https://github.com/masagrator/versionDumper
So getting info about newest game updates is not an issue (as long as you don't have banned Switch).
I'm personally storing dump here:
https://github.com/masagrator/version_dump/blob/main/version_dump.txt
But maybe someone can automate this process somehow since I'm pushing this manually.![]()
Yes.I assume that this info comes by default with every firmware update (even minor ones?)
I really doubt. This would introduce new hash to whichever file stores it, and that can be problematic when it comes to version tracking to have hundreds/thousands of FW update variations.In theory if the physical comes out some time after the latest available firmware that hasn't seen an update since, new versions info could be found on the physical dump?
I only tested that going to eshop -> back and launching game was enough to get it updated. Maybe it's possible to reduce those steps. Definitely it's done in background, but because we don't have any indicator when that happens it would be nice to figure out one trick to be sure that enough time has passed to get it updated.And to get refreshed info from the point on of the latest firmware update, would just need to go online for the app to connect to the official servers (as long the Switch isn't banned)?
So this will only work from within the Switch itself and not via some desktop app I guess.I only tested that going to eshop -> back and launching game was enough to get it updated. Maybe it's possible to reduce those steps. Definitely it's done in background, but because we don't have any indicator when that happens it would be nice to figure out one trick to be sure that enough time has passed to get it updated.
Don't you need to direct DBI to use a known database such as titleDB first?DBI has this in Tools
Yes, it downloads file from titledb.Don't you need to direct DBI to use a known database such as titleDB first?
; URL with title versions in format <id>|[rightsId|]<version>
;VersionsURL=https://raw.githubusercontent.com/16BitWonder/nx-versions/master/versions.txt
VersionsURL=https://raw.githubusercontent.com/blawar/titledb/master/versions.txt
;VersionsURL=sdmc:/versions.txt
According to GitHub, the latest change to versions.txt was made on August 4, 2025 (commit 73d736a).Worth noting that DBI uses titledb and nx-versions which also relies on titledb as a source for searching title updates and just so happens that titledb has been outdated for months and the author @blawar is MIA therefore don't count on accurate reports from it.
I guess perspective matters. For me that month was enough to miss 9 updates about games I track.According to GitHub, the latest change to versions.txt was made on August 4, 2025 (commit 73d736a).
That means the file is still quite up to date.

Also about that. Switch stores locally info about every newest game update available, excluding DLCs.
Just made a tool for dumping it in the form used by titledb's "versions.txt" here:
https://github.com/masagrator/versionDumper
So getting info about newest game updates is not an issue (as long as you don't have banned Switch).
I'm personally storing dump here:
https://github.com/masagrator/version_dump/blob/main/version_dump.txt
But maybe someone can automate this process somehow since I'm pushing this manually.![]()
It's nice to have options. ^^ Thanks, guys. I was looking to replace nx-versions I've used so far for tracking game updates. Cheers! Too bad that there's a no way to get DLC info as well.DBI has this in Tools
DLCs don't have separate updates, they are just one file with with different version numbers. That function I am using only tracks separate update files which are available only for base games.I'm curious about the missing DLC info. Is it that it doesn't have data about which DLCs are available for a given title, or is it that it doesn't have data about updates to DLCs?
(This is getting a bit offtopic, might be a good idea to move to a separate thread).
