03.10.2006, 09:00:56
1. Author generates executable installer (single file) via Install-Maker (or other install-maker package of their own choice). CSFs and MIXes are generated on author's computer, not the end users'.
2. User installs mod - Executable installer unpacks files to appropriate subfolder within Launch Base directory. (Files are now unpacked and ready to copy)
3. User can launch [already unpacked] mod by opening Launch Base and selecting the desired mod from the list.
I planned to generate the audio.bag file on Launch rather than on install - this is because the user may not want the extra space taken up by several audio.bag files. This is why I planned on the option of saving audio.bags, so that after they were generated, Launch Base retained them for later use. This is a user option, not an author option.
2. User installs mod - Executable installer unpacks files to appropriate subfolder within Launch Base directory. (Files are now unpacked and ready to copy)
3. User can launch [already unpacked] mod by opening Launch Base and selecting the desired mod from the list.
I planned to generate the audio.bag file on Launch rather than on install - this is because the user may not want the extra space taken up by several audio.bag files. This is why I planned on the option of saving audio.bags, so that after they were generated, Launch Base retained them for later use. This is a user option, not an author option.
Ever wondered what the hell is going on?
Believe me friend you're not the only one.
--Lysdexia
Check out Launch Base for RA2/YR - http://marshall.strategy-x.com
Also home to the Purple Alert mod, 1.002 UMP, and the YR Playlist Manager.
Believe me friend you're not the only one.
--Lysdexia
Check out Launch Base for RA2/YR - http://marshall.strategy-x.com
Also home to the Purple Alert mod, 1.002 UMP, and the YR Playlist Manager.