Originally Posted by
Zanoab
Instead of releasing a new EZ_DLC_Install.exe every time new DLC is released, how about split DLC data from the EZ_DLC_Installer. The DLC data can be packaged as separate .bin, .dat, .dll, .dlc, or whatever file type and the new data just needs to be downloaded and moved into the folder with the other DLC data. After opening the save data for the town, you then locate the folder where you store all the DLC data. This may lead to hundreds of small 16KB files but it is better than downloading the entire new EZ_DLC_Install.exe every month (or maybe even week) for a single DLC that the previous version didn't have. If HDLC creation becomes much more popular and widespread, then there will be a lot of trouble trying to keep up with all the new DLC data. I would rather download individual new HDLC data from people I trust instead of waiting for a new EZ_DLC_Installer.exe in hopes that the new HDLC I want is added. The file name could be "HEX# - Item Name" where "HEX#" is the original/default hexcode and the item name is self explanatory. Note: File name won't actually change the actual hexcode or item name.
The EZ_DLC_Install.exe can still be updated but instead of for new DLC, it is updated for new features, bug fixes, better error checking/reporting, DLC compatibility, DLC modification (such as change hexcodes in case there is a conflict), etc.
Hopefully this will bring new ideas to be set into motion before HDLC creation takes off.