Add warning for non-unique file name schemes (#233)
* Add warning for non-unique file name schemes * Update README with warning
This commit is contained in:
@@ -178,6 +178,8 @@ Each of these can be enclosed in curly bracket, `{}`, and included in the name.
|
||||
|
||||
At least one key *must* be included in the file scheme, otherwise an error will be thrown. The folder scheme however, can be null or a simple static string. In the former case, all files will be placed in the folder specified with the `directory` argument. If the folder scheme is a static string, then all submissions will be placed in a folder of that name. In both cases, there will be no separation between all submissions.
|
||||
|
||||
It is highly recommended that the file name scheme contain the parameter `{POSTID}` as this is **the only parameter guaranteed to be unique**. No combination of other keys will necessarily be unique and may result in posts being skipped as the BDFR will see files by the same name and skip the download, assuming that they are already downloaded.
|
||||
|
||||
## Configuration
|
||||
|
||||
The configuration files are, by default, stored in the configuration directory for the user. This differs depending on the OS that the BDFR is being run on. For Windows, this will be:
|
||||
|
||||
Reference in New Issue
Block a user