Update Drive instructions, readme

This commit is contained in:
J-D-K 2021-12-15 20:21:33 -05:00
parent b2be2a26fb
commit 2f34ddd3ba
2 changed files with 15 additions and 13 deletions

View File

@ -2,6 +2,8 @@
**Google only allows unverified apps to have up to 100 test users. Not only would this limit be filled within minutes, but each user has to manually added. People have been asking for some kind of cloud support since I wrote JKSM on 3DS and this is my way to support it while getting around Google's restrictions.**
**Note: Due to Google's restrictions on unverified apps, you will be required to login once every seven days. There is nothing I can do about this at the moment.**
1. Go to https://console.cloud.google.com/, if this is your first time, accept the terms and you should now have the dashboard in front of you.
2. Click `CREATE PROJECT` on the next screen.<br><center><img src="https://i.imgur.com/42Wruo4.png" /></center>
@ -22,13 +24,10 @@
17. On the left under APIs and Services, click Credentials.<br><center><img src="https://i.imgur.com/iWD1GTk.png" /></center>
18. On the next screen, click `+ CREATE_CREDENTIALS`. Select `OAuth Client ID`.<br><center><img src="https://i.imgur.com/ri3tuB7.png" /></center>
19. On the next screen, under `Application Type`, select `Desktop App`. Click `Create`.
20. You now have your Client ID and Client Secret. Copy and paste these somewhere for later. Almost done!
21. You're going to need to login and get an authentication code for JKSV to exchange. This is only needed once. Afterwards, JKSV will use a refresh token so you do not have to log in every time you want to upload or download something. Replace `YOUR_CLIENT_ID_HERE` with your client ID obtained in the previous step: `https://accounts.google.com/o/oauth2/v2/auth?client_id=YOUR_CLIENT_ID_HERE&redirect_uri=urn:ietf:wg:oauth:2.0:oob&response_type=code&scope=https://www.googleapis.com/auth/drive`.
22. At the end, you will be presented with a code. You will need this for the final step.
20. You now have your Client ID and Client Secret. Almost done!
23. On your Switch's SD card, go to JKSV's config file and open it. `SDMC:/config/JKSV/JKSV.cfg`.
24. Add these lines and save. You should be good to go now:
24. Add these lines and save. The next time you open JKSV, you will need to login to Google on your Switch:
```
driveClientID = YOUR_CLIENT_ID_HERE
driveClientSecret = YOU_CLIENT_SECRET_HERE
driveAuthCode = YOU_CODE_FROM_STEP_22_HERE
```

View File

@ -14,24 +14,27 @@ This started as a simple, straight port of my 3DS save manager I publicly releas
* Dumping this data is always enabled, but writing back needs to be enabled from the options menu. Writing to this can be very dangerous.
* Processes can be terminated from the Extras menu allowing you to open even more of these and explore more.
6. Export save data to folders like the orignal or compressed zip files to save space.
7. Create save data so the user no longer needs to boot games to import saves.
7. Upload and download save backups to [Google Drive](https://github.com/J-D-K/JKSV/blob/master/GD_INSTRUCTIONS.MD) if it is configured.
8. Create save data so the user no longer needs to boot games to import saves.
* Titles can be rescanned from the Extras menu. For example, if you insert a game card while JKSV is open, rescanning will load and add it to the save creation menu(s).
8. Export and use SVI files to create save data for titles not installed on your system. For games that detect other game saves to unlock content.
9. Export and use SVI files to create save data for titles not installed on your system. For games that detect other game saves to unlock content.
* SVI files are simply the title ID, NACP, and icon packed into a file. Placing them in `JKSV/svi` will load them as if they are any other game on your switch. They will appear in the save creation menus with the rest.
9. Extend save data containers to any size the user wants or automatically if the save cannot fit into the current one.
10. Delete save data from the system.
11. Reset save data as if the game was never launched.
12. Display stats and information about the game/save: Play time, launch count, title ID (TID), save ID(SID)/name of save file on user nand partition, etc.
13. Open and explore bis storage partitions via the Extras menu
10. Extend save data containers to any size the user wants or automatically if the save cannot fit into the current one.
11. Delete save data from the system.
12. Reset save data as if the game was never launched.
13. Display stats and information about the game/save: Play time, launch count, title ID (TID), save ID(SID)/name of save file on user nand partition, etc.
14. Open and explore bis storage partitions via the Extras menu
* BIS Storage is opened inside a basic filebrowser. The partition's listing is on the left. Your SD is on the right.
* Only copying to SD and file properties work on BIS partitions. Writing to and deleting are disabled unless enabled like system save data.
14. Misc Extras:
15. Misc Extras:
* Ability to remove downloaded firmware updates from NAND. This is located under Extras.
* Terminating processes by [ID](https://switchbrew.org/wiki/Title_list#System_Modules). Allowing you to dump normally unopenable system archives.
* Mount by System Save [ID](https://switchbrew.org/wiki/Flash_Filesystem#System_Savegames). Normally used when the terminated process makes JKSV unable to rescan titles without the Switch crashing.
* Mount and open RomFS of process the homebrew menu takes over (if launched as NRO).
* Hold R while opening a game or applet with Atmosphere so the homebrew menu loads. Open JKSV and press minus and select **Mount Process RomFS**. The romfs of the app should appear in the browser along with your SD on the right.
**NOTE: Some features may require building JKSV from source. I am extremely picky and only release when I am satisfied and sure things work 100% as expected.**
## Quick Guide
1. Main/User Menu
* A Selects the currently highlighted user and allows you to browse their titles.