RELEASE NSC_Builder. Nintendo Switch Cleaner and Builder. (Game+updates+dlc in a single xci)

@darkseekerliu Some people had that issue before with 64 bits versions while the 32bits worked fine for them. I'd suggest to try the x86 version first, i don't know why the issue happens it has to be something related to the 64bits python or pyinstaller.
https://github.com/julesontheroad/NSC_BUILDER/releases/download/1.00d/NSCB_100dx86.zip

The loop happens basically because the python compiller fails since is used to parse the files to avoid issues with special characters.

 

Yeah is supported on the beta and master but still adding some changes beofre the next release. I also added a backup saves for only intalled games since dbi supports it now.
Will include the install xci from google drive that was in the beta since a while back too and sd scans are now limited to the folders set in a mtp_xci_locations.txt
Is on a little hold to add a few changes + testing but the DBI >155 part is solved. It will support old and newer versions of dbi.

 

I plan to add upload options directly onto the google drive api, for downloads the drive mode can download currently single files converted, trimmed, etc... but should be expanded to create multis.
The other system that also works with the program is to use a tool to mount google drive as a system unit, and then it will work as a normal drive, is slower than the api but it works.

My recommended tool for that matter is raidrive https://www.raidrive.com/ but rclone or google filestream will also work.
In my experience rclone requires more tinkering and is a little slower than raidrive and filestream is the faster but you need a gsuite or an organization account (education, company, ...), also filestream tends to make files and flders go over quota because it reads several chunks of data at the same time and those seem to count as a download, is the more seamless though.

 

NSCB 1.01 release with support to DBI>=155 and other stuff.
https://github.com/julesontheroad/NSC_BUILDER/releases/tag/1.01

1. Support for DBI 155 and 156 new mtp setup
2. Added option to backup saves for installed games only
3. Added xci and xcz installation from google drive remotes
4. Added fixed xci location configurations for mtp mode
5. Added option to MTP - AUTOUPDATE DEVICE FROM LIBRARY to check from game registry instead of installed
6. Fix issues installing certain files from google drive because of special characters
7. File Selector now allows to select multiple files at once
8. Added additional information on the "Files" tab on the interface
9. Corrected patched multiprogram files VERIFICATION
10. Ability to not autoupdate DATABASES
11. Other changes and bugfixes.
* Updated keygeneration strings to FW 10.2.0
* Tickets that don't follow the proper standard now issue a warning instead of preventing titlerights removal on some functions.
* Fixed hang on interface when a buildid is not readable on certain situations.
* Added better representation of xci certificates on nut info.
* Faster library calls on python version which should speed up the batch menus.
* Fix for #169 where some language combinations break correct language tag addition due to change on python semantics.
* Other small bugfixes

 

NSC_Builder v1.01 (corrected)
https://github.com/julesontheroad/NSC_BUILDER/releases/tag/1.01-crr

Seems i forgot to add the bin folder on the x64 and x86 builds so mtp mode will crash or run with the older exe from 1.00, is recommended to redownload for thos using x86 or x64 releases.

 

I just tested and it's working fine. Did you add the credentials.json to zconfig/credentials?
That json is the one with the data from your own app, the generic one can be gotten here:
https://developers.google.com/drive/api/v3/quickstart/python
1.- You press enable google api:
2.- Add the name for the app you want
3.- Press yes to agree with the google tos
4.- Press next
5.- Select desktop app in type
6.- Press create
7.- Press download client configuration

You'll get a credentials.json you need to add to zconfig/credentials this can be used with different google accounts but is recommended to use it with the one you enabled the api into. If you use it with others you need to accept that the application wasn't send for verification.
If you want to have other credentials.json files it also accept them as remote_name.json. So if you name your remote drive it'll search for drive.json or credentials.json
Then when you register it in configuration the domail will be something like:
https://accounts.google.com/o/oauth2/auth?response_type=code&client_id=XXXXX.........

I think the localhost thing may be due to the json file missing.

Basically that json file represents the app you use to access google drive, is made that way so it's your own app and no one can see your drive statistics or anything. So no issue to repurpuse it on several drive accounts if you want, outside the warning.
The second thing you'll get every time you add a remote is a token. The token is named with the name you input and that name will be like a drive letter in NSCB.

 

Do you have master_key_0a in your keys.txt inside ztools? Is the one that game uses, it seems it wasn't able to retrieve the data from the cnmt.
Just in case run the keys checker that's on the configuration.

 

Yeah it finds them at first, i changed the retrieve system because of a similar issue and that may be the reason.
Basically before it requested all the files in the library, then added to the text file the filepath and search for it in the drive.
It seemed that drive search for filenames couldn't find certain characters so now it adds the file id too. What that message means is that google drive isn't returning a positive answer to the request, i have to try with that usercase, but it may be due to quota, depending on the case.
Still i'll test with mine, to discard something outside of quota.

— Posts automatically merged - Please don't double post! —

Yes but ther's no fw 10.9.0 i think you're looking at a SDK number. It also isn't a sure thing, it depends on the game, if it uses newer sdk functions normally it fails.
Anyway between 9.1.0 and 10.2.0 the masterkey doesn't change so for games you plan to install is enough to use an installer that patches RSV like tinfoil, dbi, awoo or goldleaf. For xci you need to patch it trough NSCB, though.

 

Yeah but even with high sdks it may work on fws older than the sdk, it will depend on the functions that are being used by the program. Still when you see an old sdk in the game data is a sure thing, if the sdk is pretty new it has a high probability to fail.
Also from the meta sdk version is not relevant, that's added when the game or update gets uploaded to the CDN so it's always newer, the one relevant is the program sdk number in games|updates or data sdk number in dlcs.