![blade and sorcery mods blade and sorcery mods](https://images.gamewatcherstatic.com/screenshot/image/6/60/301576/52-1557923380-1717872091.jpeg)
This may not seem like a big deal right now, but if in the future KospY would decide to implement mod dependencies (which I predict will happen), he will be forced to start using the manifest to define these dependencies and rely on the manifest's name property to check for said dependencies and ensure backwards compatibility for older mods - this obviously will only work if the mod's folder name matches the manifest's name property - and I can see that many mod authors have opted to have these mismatched which is unfortunate.
![blade and sorcery mods blade and sorcery mods](https://i.ytimg.com/vi/LENlC-qb5Zs/maxresdefault.jpg)
From what I understand the mod authors still get a chance to modify the name property which is the root cause of this issue as the asset paths and the manifest are mismatched. Hi Grospolina, our understanding of the mod bundler for 8.4 was that it automatically generates a manifest file for you with the correct name property inside the manifest. The fix changed it such that manifest mod name was no longer being modified. Before the bug was marked as fixed, it was also removing the spaces and punctuation from the manifest mod name. Right now, it's taking the mod name from manifest.json, which is not necessarily the same name. The folder is required to exist in the archive, or it won't work even when installing manually. The folder name of the mod should be taken from the folder contained within the archive itself. I have resubmitted this bug report (Issue #8440), as it was marked as fixed, but it wasn't fixed properly.
![blade and sorcery mods blade and sorcery mods](https://static2.srcdn.com/wordpress/wp-content/uploads/2020/04/Blade-and-Sorcery-Star-Wars-Mod.jpg)