When nzb-file is added to queue and it has a category the scan-scripts are chosen from CategoryX.Extensions (if it's not empty). In new implementation the scan-scripts work on per-category basis. Unified option "Extensions" tries to be per-nzb (and per-category) whenever possible, which the exception for service-script mentioned above. In v17 scan-scripts are selected globally. Such extensions are activated once and cannot be overriden per category or per nzb. Does it work well with the general concept of option "Extensions" providing defaults for new downloads? I hope to cover this with the note from description:Ĭertain extensions work globally for the whole program instead of per-nzb basis. Upcoming service-scripts ( #318) will not be selectable per-nzb and will rather run globally. Only script developers need to know differences. #SCHEDULER NZBGET INSTALL#So, now to install a new script the user have to select it in option "Extensions" no need to think about which option to use, regardless of script kind, be it a post-processing script, scan-script or queue-script. That's almost one setting, if we don't count overrides and scheduler.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |