how_datvault_works
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
how_datvault_works [2022/07/27 17:35] – johnsanc | how_datvault_works [2024/07/11 14:48] (current) – [Why do some No-Intro DATs say Discontinued when they are not?] johnsanc | ||
---|---|---|---|
Line 15: | Line 15: | ||
| Emulators | | Emulators | ||
| FruitMachine | | FruitMachine | ||
- | | NoIntro | + | | NoIntro |
| Others | | Others | ||
| Pinball | | Pinball | ||
Line 24: | Line 24: | ||
| Tosec | | Tosec | ||
- | |**ⓘ NOTE:** \\ * No-Intro DATs are sourced from the Daily Pack which is generated once per day on the No-Intro | + | ===== Why do some No-Intro DATs say Discontinued when they are not? ===== |
+ | |||
+ | No-Intro DATs are sourced from Dat-o-Matic. There are occasions where a DAT is locked for editing or database cleanup. When a DAT is locked it is not available for download so it is marked as Discontinued until the download is available again. | ||
+ | |||
+ | <WRAP tip> | ||
===== What are the DATVault JSON files? ===== | ===== What are the DATVault JSON files? ===== | ||
Line 30: | Line 34: | ||
DATVault works by detecting special JSON files in your DatRoot. Each DAT you would like to manage has its own corresponding JSON file. Each file provides info about the DAT version you currently have. | DATVault works by detecting special JSON files in your DatRoot. Each DAT you would like to manage has its own corresponding JSON file. Each file provides info about the DAT version you currently have. | ||
- | |**⚠ CAUTION:** \\ The DATVault JSON files are not meant to be manually edited. Modifying the JSON files may cause DAT updates to not work properly. The information provided is for reference only.| | + | <WRAP important> |
The DATVault JSON files contain the following keys: | The DATVault JSON files contain the following keys: | ||
Line 62: | Line 66: | ||
The information in the JSON file is compared against the DATVault repository to determine if there are updates available to download. If the JSON file you have does not match the latest version available by DATVault, then the corresponding DAT has an update. When you update a DAT, the JSON file is also updated. | The information in the JSON file is compared against the DATVault repository to determine if there are updates available to download. If the JSON file you have does not match the latest version available by DATVault, then the corresponding DAT has an update. When you update a DAT, the JSON file is also updated. | ||
- | |**⚠ CAUTION:** \\ DATVault only manages DAT updates for DATs it has downloaded. It will NOT update DATs you have placed into your DATRoot manually. Its advised to remove any manually managed DATs before having DATVault manage those DATs.| | + | <WRAP important> |
- | |**ⓘ NOTE:** \\ | + | <WRAP info>DATVault will download any updates into the same directory that contains the respective JSON file. Before a DAT is updated, the current DAT you have (which is referenced in your JSON file) will be renamed with a '' |
- | |**ⓘ NOTE:** \\ Some DATs for disc based systems have accompanying cue sheets. DATVault will download cue packs to a folder called '' | + | <WRAP info>Some DATs for disc based systems have accompanying cue sheets. DATVault will download cue packs to a folder called '' |
Now that you understand how DATVault works at a high level, refer to the next section to [[datvault_setup|get started using DATVault]]. | Now that you understand how DATVault works at a high level, refer to the next section to [[datvault_setup|get started using DATVault]]. |
how_datvault_works.1658943345.txt.gz · Last modified: 2022/07/27 17:35 by johnsanc