Originally Posted by Dolgubon
Maybe it goes off the ## Name field. However, with the changes to addon detection it would be possible to have the same addon hidden in a folder.
|
It was always possible to have a manifest in a nested folder, but the game wouldn't load the files.
e.g. this configuration:
Code:
addons/LibAddonMenu/manifest.txt
addons/SomeAddonWithALetterAfterL/LibAddonMenu/manifest.txt
One would expect that LibAddonMenu is loaded from addons/LibAddonMenu, but the game searches all nested folders and then picks the last manifest it found (it's actually a bit more complicated since dependencies also play a role). Because of that it would decide to load the nested manifest in SomeAddonWithALetterAfterL and in the past the standalone version of LAM wouldn't get loaded at all since the paths in the manifest would get treated as relative to the addon root folder.
Now with the changes applied to addon loading, the paths in the manifest are treated relative to the manifest file, which allows us to load nested addons correctly. The AddOnVersion directive comes into play when the game sees more than one version of the same addon. When no version is supplied, it will just pick the last file as explained before, but when we add a version it will always prefer the one with the highest number.