Dear IPACS team,
What are now the allowed folder structures in the external user-defined folder?
As already stated the aim is to replicate the ADDON structure, which is optimal for scenery management as illustrated below : all elements of a same scenery are gathered in a specific folder and substructure:
The ADDON structure works well on the default game folder, but it's on the C: drive which is to be avoided.
The same ADDON structure works well also in the Steam Library, which is not intended for home-made or manually installed sceneries.
How can we successfully declare it on the external user-defined folder? What are the allowed structures and syntaxes?
So far I was only able to replicate the SCENERY structure of the default game folder, which spreads constitutive parts of various sceneries into common folders, leading to a quickly growing mess :
To remove or deactivate a scenery, you'll have to search for bits and pieces in various sub directories.
Could you please provide a quick guideline of possible/allowed structure and syntaxes?
Last but not least, have you considered a de-activating prefix as proposed by Lenidcamper? something like :
!package
___elevation
___ images
___...
or
#package
___elevation
___images
___...
Thanks in advance
Cheers
Antoine