Adjust the /q download
command to allow downloading QuestPackages
and QuestTemplates
also from nested folders
#2498
Labels
Feature Request
New feature or request.
Requirements
The strict restriction to only allow downloads from the root folders
QuestPackages
andQuestTemplates
lead to limitations that cause prescribed repository structures, that does not fit all use-cases, especially in Archives used by the Community/multiple Users.It is required to be able to have a prefix folder, like the user who made it and a folder what project it is, before forcing the structure into the folders
QuestPackages
andQuestTemplates
(dont limit, that this folders could contain a folder with the same name again).With this change it would also be more usable to provide an setup with e. g. Daily Quests, based on Templates, and Download booth with one command.
TODOs
QuestPackage
andQuestTemplate
?default
quest?New Command Structure
The Current Structure
Use Cases:
Repository Layout
There are multiple layout choices that can be (independently) choosen:
/path/package.yml
vs./path/QuestPackages/package.yml
or/quest/package.yml
vs./QuestPackages/quest/package.yml
)/path/package.yml
vs.package.yml
or/path/QuestPackages/quest/package.yml
vs./QuestPackages/quest/package.yml
)/path/quest/package.yml
vs./path/package.yml
or/QuestPackages/quest/subquest/package.yml
vs./QuestPackages/subquest/package.yml
)Selected Packages:
quest
package even though there's also atutorial
package)/quest/package.yml
)Target Location:
Possible new structure
The New Structure (v1, does not fulfill the requirements)
The text was updated successfully, but these errors were encountered: