Restructuring "Train" addons folder
Currently, the way the trains folder is set up is rather cumbersome, and in some cases, can take up a lot of disk space, for example if you have multiple setups of the same train
A better way of reading these files is having its own config folder and its resources moved to its proper locations:
- Train (using R-16 as an example)
- Configs (Train Folder > Config > R-16)
- ats.cfg
- extensions.cfg
- panel2.cfg (or panel.cfg)
- sound.cfg
- train.dat
- train.txt
- Plugins (Train Folder>Plugins)
- OS_ATS1.dll and other supported train/route enhancement plugins
- Textures (Train Folder > Textures > R-16)
- All supported image file types
- Models (Train Folder > Models > R-16)
- .b3d, .csv, .x, .animated files
- Sound (Train Folder > Sounds > R-16)
- All supported sound file types
- Configs (Train Folder > Config > R-16)
This setup would allow a modular design, and easier management of train setups without consuming too much disk space, simular to how the route folders are managed.
I started separating the config files from the resources in my train add-on by simply using relative paths in the config files to reference files stored in a another folder. https://github.com/joeyfoo/alstom-metropolis-for-openbve
This can be simplified to omit or de-emphasise folders that contain only resource files.
Having the proposed folder structure makes it hard to manage and delete add-ons, because instead of deleting Train/trainname, you now need to delete each folder under multiple sub-folders.
(On a side note, is this project in active development and are you still seeking developers?)
When i made this issue, i had an idea to give it a similar structure to how Source engine game files are structured.
Might scrap this idea.