GDLauncher
GDLauncher copied to clipboard
gorilla-devs
[BUG] Modpack Zip Export Not exporting mods correctly
Describe the bug The Curseforge Modpack export isn't assigning the mods their project ID inside the manifest.json it just dumps all the mods that are downloaded from cf into the overrides folder.
To Reproduce Steps to reproduce the behavior:
- open gdl
- try export a modpack
- huge 500mb file exported with all jars as overrides
Expected behavior Export the modpack with all mods in the manifest
Operating System:
- OS: Windows
- Version: 11
- Java Version: 16
- Minecraft Version: 1.16.5
- Mod Loader: Forge
Additional context Add any other context about the problem here.
It is "Export ZIP" and not "Export to CF" after all
I see is this due to the API changes it would no longer be possible? I thought the whole idea of the "Export Instance" was to export modpacks that would be able to be reimported on gdl/curseforge system
Actually it's still possible
I've just tested with another pack and it seems to export that one fine, is it possible somehow my mods have been unsynced with curseforge?
They are treated as CF Mods if they have the little CF Icon
I've never seen them display a CF Icon and it was working before :s
Update: - Copying all the mods back in via the main GUI letting it re-sync seems to have fixed the issue, Could we potentially get a "Re-Sync Mods" option incase this happens in the future?
I am seeing this same issue currently. I am trying to export a pack that I created in GDL via the Add Mods. It almost seems like for some reason it decided to desync the mods from the mod pages. A way to resync, even if it was manual, would be greatly appreciated. I am trying to export a modpack that I created and upload it to Cureforge, but quite a few files were only exported as overrides instead of being put in via the manifest.json file. I am running Linux Mint 21.1.
Problem still continues and the fix of re-adding them manually in the mods UI doesn't always seem to work.
