Hello everyone! Yesterday me and CrystalTwoK (developer of Arsenal) met and deliberated about a new manifest that would satisfy us both. In short: We are bumping up the version to 2 and adding some features that Arsenal requires and MM can handle. Such as tags and categories. Since it is always a pretty big deal to change a standard there have been some changes in my time table. Most notably of which is the delay of MM 2.0 in favor of an end of life update for the current one, intended to be called "MM 1.3 (End of life)". This update aims to address all of the inconsistencies with manifests and will provide sufficient feedback if a manifest is of a unsupported version. The update will not add support for the V2 manifest, as this is reserved for MM 2.0, but it will add guards to prevent issues should you try to add it.
So this is where we're at right now. I know this may be disappointing to some hoping for news on the 2.0 only to find it delayed again but I've determined to the "End of Life" update to be more important as of the changes to the manifest.
Thank you for your attention and understanding! See you soon with more info about the MM 1.3 End of Life.
This preview is to test the new UI and profile system
With all that out of the way, here it is (Linux build will come later today). Thank you for your patience! And a special thank you to everyone who supported me on Ko-fi!
Potential fix for recent crashes (for version 1.2.1.0) Should you see something like this: JsonReaderException: '0x00' is an invalid start of a value. LineNumber: 0 | BytePositionInLine: 0. in your log file. This means that one of your mod manifest.json files is completely empty. I'm currently still looking for the cause.
To solve this You go to %localappdata%\Helldivers2ModManager\Mods and go through your mods manifest files and find the ones that are empty. You then just delete the respective mods folders.
NOTE: Your paths may vary based on your settings. This example uses the default paths.
I was doing some mod updates and had a crash in HD2MM when deleting an old mod. When this happened, the old mod was gone from the shown list but a updated mod couldn't be added. (wouldn't show up on list when added.) Deleting mod from (above) dir allows for the mod to be added to hd2mm again.
I'm getting this even with no mods installed. I have uninstalled the launcher and the game multiple times and the launcher will not open past the initial logo.
Copying the creator's latest announcement from the modding Discord:
"Potential fix for recent crashes A lot of crashes have occurred with the recent version of the manager (1.2.0.1), which has been experiencing many crashes that have been happening with the recent version of the manager (1.2.0.1).
One of the potential causes has been discovered!
Should you see something like this: DirectoryNotFoundException: Could not find a part of the path 'C:\Users\<User Name>\AppData\Local\Temp\Helldivers2ModManager\<Mod Name>\<image>.png|.jpg|ect in your log file this could be the cause. Currently there is a bug that causes the manager to write an absolute path to an icon into the manifest during the adding process. To solve thisYou go to %localappdata%\Helldivers2ModManager\<Mod Name> and open the file called manifest.json. In there you delete the part "IconPath": "<image>.png|.jpg|ect" also remove the comma (,) after it.This issue only happens with mods that do not supply a manifest. NOTE: You're paths may vary based on your settings. This example uses the default paths."
I install a mod using the manager, it crashes, then when I try to install the mod again, it just doesn't show up there. This is very frustrating to deal with...
are the mods you're trying to install older than July? For me atleast this crash issue has only been caused by mods post Control group, or whenever the last major update was my suggestion is just to keep to mods updated at earliest July
for those guys who have the helldiver 2 mod manager logo appear and the mod refused to start
some of the mod are having issue atm and gave me this warning warning image
a specific mod might cause the mod manager to refuse to open, go to C:\Users\name\AppData\Local\Helldivers2ModManager\Mods and delete only that mod folder and it should open your mod manager again
for me the mod that cause the issue was the "Insurgency Sandstorm Apache pilot replaces Eagle-1" here's hoping the mod author fix the mod cause i really love it and i can't use it atm
downloaded new update today and now no matter how i start hd2 from steam or hd2manager it gives me "Unexpected error while loading game files. Check for any data that might of been modified or corrupted from initial install. (Error Code: 0x44415441)". i tried purging it and launching from steam, like in tutorial i found, and it worked, but i want to play with mods. What should i do?
*Update* Just found out that it's not the first time happening to people and that it is happening after updates
instead of deleting your entire HD2 game you just need to browse the files and delete your data folder. Then validate your files. Easier to download 30GB than 100GB. That is if you're still getting that error.
I'm having the same issue. I have uninstalled and reinstalled the game, move folders, uninstalled and reinstalled the mod manager, removed all mod files/folders... nothing has worked so far.
675 comments
Hello everyone!
Yesterday me and CrystalTwoK (developer of Arsenal) met and deliberated about a new manifest that would satisfy us both.
In short: We are bumping up the version to 2 and adding some features that Arsenal requires and MM can handle. Such as tags and categories.
Since it is always a pretty big deal to change a standard there have been some changes in my time table. Most notably of which is the delay of MM 2.0 in favor of an end of life update for the current one, intended to be called "MM 1.3 (End of life)". This update aims to address all of the inconsistencies with manifests and will provide sufficient feedback if a manifest is of a unsupported version. The update will not add support for the V2 manifest, as this is reserved for MM 2.0, but it will add guards to prevent issues should you try to add it.
So this is where we're at right now. I know this may be disappointing to some hoping for news on the 2.0 only to find it delayed again but I've determined to the "End of Life" update to be more important as of the changes to the manifest.
Thank you for your attention and understanding! See you soon with more info about the MM 1.3 End of Life.
Feel free to add your questions to this post.
So it's here, manager 2.0 preview.
First things first:
With all that out of the way, here it is (Linux build will come later today). Thank you for your patience!
And a special thank you to everyone who supported me on Ko-fi!
Do not report bugs for a preview build!
If you want to report a bug, please include the latest log file.
If your issue is more specific, feel free to join the Modding Discord.
Should you see something like this:
JsonReaderException: '0x00' is an invalid start of a value. LineNumber: 0 | BytePositionInLine: 0.in your log file. This means that one of your modmanifest.jsonfiles is completely empty. I'm currently still looking for the cause.To solve this
You go to
%localappdata%\Helldivers2ModManager\Modsand go through your mods manifest files and find the ones that are empty. You then just delete the respective mods folders.NOTE: Your paths may vary based on your settings. This example uses the default paths.
"Potential fix for recent crashes
A lot of crashes have occurred with the recent version of the manager (1.2.0.1), which has been experiencing many crashes that have been happening with the recent version of the manager (1.2.0.1).
One of the potential causes has been discovered!
Should you see something like this:
DirectoryNotFoundException: Could not find a part of the path 'C:\Users\<User Name>\AppData\Local\Temp\Helldivers2ModManager\<Mod Name>\<image>.png|.jpg|ectin your log file this could be the cause.Currently there is a bug that causes the manager to write an absolute path to an icon into the manifest during the adding process.
To solve thisYou go to
%localappdata%\Helldivers2ModManager\<Mod Name>and open the file calledmanifest.json. In there you delete the part"IconPath": "<image>.png|.jpg|ect"also remove the comma (,) after it.This issue only happens with mods that do not supply a manifest.NOTE: You're paths may vary based on your settings. This example uses the default paths."
For me atleast this crash issue has only been caused by mods post Control group, or whenever the last major update was
my suggestion is just to keep to mods updated at earliest July
some of the mod are having issue atm and gave me this warning warning image
a specific mod might cause the mod manager to refuse to open, go to C:\Users\name\AppData\Local\Helldivers2ModManager\Mods and delete only that mod folder and it should open your mod manager again
for me the mod that cause the issue was the "Insurgency Sandstorm Apache pilot replaces Eagle-1"
here's hoping the mod author fix the mod cause i really love it and i can't use it atm
*Update* Just found out that it's not the first time happening to people and that it is happening after updates
edit : i tried the other mod manager that one works