videogame_asset My games
Notifications
notifications_off
No unread notifications right now
You're up to dateYou're up to date
Notification Settings
Show notifications for:
Tracking preferences
No unread notifications right now
You're up to dateYou're up to date
Notification Settings
63 comments
Manually download the archive file
Open Vortex
Navigate to "Extensions" on the side bar
Drag the file to the designated box (or manually navigate to file location) on the bottom RHS
Confirm Vortex restart
Valheim should now show up in your managed games list
Edit: For those mentally challenged among us. Move the downloaded unextracted file as instructed.
Log:
Error: not an extension, info.json missing
at extractFull.then.catch.err (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:2491:108)
at tryCatcher (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\util.js:16:23)
at Promise._settlePromiseFromHandler (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:512:31)
at Promise._settlePromise (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:569:18)
at Promise._settlePromise0 (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:614:10)
at Promise._settlePromises (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:689:18)
at Async._drainQueue (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:133:16)
at Async._drainQueues (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:143:10)
at Async.drainQueues (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:17:14)
at <anonymous>
Which I manually installed, but then Vortex somehow magically reset it to 5.4.11.
Is there a trick to manually updating in such a way that Vortex won't blow it up?
I find in the Valheim dir a file, "vortex.deployment.unstripped-assemblies.json", which says...
"instance": "c37b977d-9197-48de-bdec-8dfcb870630a",
"version": 1,
"deploymentMethod": "symlink_activator",
"gameId": "valheim",
"deploymentTime": 1634244875518,
"stagingPath": "D:\\Vortex Mods\\valheim",
"targetPath": "D:\\SteamLibrary\\steamapps\\common\\Valheim",
"files": [
{
"relPath": "unstripped_corlib\\Mono.Security.dll",
"source": "denikson-BepInExPack_Valheim-5.4.1600",
"target": "",
"time": 1612478936000
Okay. So 5.4.16. I go into that D:\Vortex Mods\valheim dir and find a directory named, denikson-BepInExPack_Valheim-5.4.1600".
Okay, so it should be loading 5.4.16.
And Thank You for keeping this package updated! [EDIT: Nevermind, I take that back.}
But...
The Valheim "player.log" says this...
[Message: BepInEx] BepInEx 5.4.11.0 - valheim
And...
[Warning: BepInEx] Plugin [PlantEverything 1.8.4] targets a wrong version of BepInEx (5.4.15.0) and might not work until you update
[Warning: BepInEx] Plugin [Build Camera 1.6.1] targets a wrong version of BepInEx (5.4.15.0) and might not work until you update
[Warning: BepInEx] Plugin [Equipment and Quick Slots 2.0.14] targets a wrong version of BepInEx (5.4.15.0) and might not work until you update
[Warning: BepInEx] Plugin [SailingMapReveal 1.0] targets a wrong version of BepInEx (5.4.16.0) and might not work until you update
[Warning: BepInEx] Plugin [Useful Trophies Mod 1.0.1] targets a wrong version of BepInEx (5.4.15.0) and might not work until you update
At this point, I'm still digging in to it. Will update if I figure it out.
https://forums.nexusmods.com/index.php?/topic/10036523-republish-valheim-unstripped-assemblies-on-nexus-thunderstoreio-has-trojans/
So...um...
I guess this is no longer needed? It was originally created by Nagev but has been uploaded by BigBizKit. Maybe because peeps were asking for it?
To quote The Critical Drinker: "Don't know."
No, it's needed.
If I uninstall it in Vortex, then run Vortex, it doesn't show the game. If I select Games and search for Val, it shows Valheim. If I select the game Valheim, Vortex tells me it needs the extension and downloads/installs/restarts and there is Valheim with all the mods I had already installed.
BUT - it's still running BepInEx 5.4.11.
Even though I have manually updated my BepInEx to 5.4.17 and even though denikson's BepInEx Pack for Valheim is up to 5.4.16.
Here is HowTo fix it:
(BE ADVISED: Vortex's Valheim Extension (this mod on this page) WILL OVERWRITE your Valheim/BepInEx/core directory if you run Vortex. DO NOT RUN VORTEX while doing this fix until you reach that step in the HowTo.)
1. Exit the game.
2. Close Vortex.
3. Install the latest BepInEx in your Valheim game dir. I use aedenthorn's BepInExUnityInstaller which is just a little .exe that you place IN YOUR VALHEIM GAME DIR and then double-click to run it. It will grab the latest BepInEx and install it. https://www.nexusmods.com/site/mods/287
4. Manually (NOT the "Mod Manager Download" button - the "Manual Download" button) download the .7z file of the Valheim Extension for Vortex (this mod on this page).
5. Unpack the .7z to a directory of the same name as the file ("Valheim Support-210-1-0-12-1622456568").
6. Go into the directory "Valheim Support-210-1-0-12-1622456568/BepInExPayload/BepInEx" and delete the "core" subdirectory.
7. Goto your gamedir "Valheim/BepInEx" and right-click and copy the "core" dir.
8. Go back to the "Valheim Support-210-1-0-12-1622456568/BepInExPayload/BepInEx" directory and paste. You should now have a new "core" subdir with the latest files.
9. Move back up to the "Valheim Support-210-1-0-12-1622456568" top level directory.
10. Hit CNTL+A to select All Files.
11. Right click on any file and select "7-Zip" then select "Add to Valheim Support-210-1-0-12-1622456568.7z".
You now have a Valheim Support-210-1-0-12-1622456568.7z with the latest BepInEx core files in your "Valheim Support-210-1-0-12-1622456568" directory.
12. Run Vortex. (This will overwrite the newly installed latest version files in "Valheim/BepInEx/core" with the old 5.4.11 files - but that DOESN'T MATTER.)
13. Go into Extensions and delete the Valheim Extension. Vortex will prompt you to restart. Okay that and restart Vortex.
14. Go into Extensions. Find your new "Valheim Support-210-1-0-12-1622456568.7z" in File Manager, drag and drop it into the box in Extensions. It will install and prompt to restart. Restart Vortex.
Viola!
Now when you run Valheim, you should see this in the log:
[Message: BepInEx] BepInEx 5.4.17.0 - valheim (5/14/2021 12:42:05 PM)
(or whatever the latest version is that you just installed)
KEEP IN MIND - Vortex WILL overwrite "Valheim/BepInEx/core" EVERY TIME you run Vortex.
So if you now go into that dir and check the files, you will have the latest core files.
BUT - You'll have to do this Step by Step every freakin time you update your BepInEx to the latest version or else Vortex will overwrite your core files with whatever version was in the extension that you just packed.
Cheers Mates!
For anyone wondering, Vortex stores extensions by default at:
"C:\Users\<User>\AppData\Roaming\Vortex\plugins".
This is where your "Valheim Support" or "Game: Valheim" extension ends up. They're stored as loose folders and files (not archives), so you can update BepInEx by driectly dragging the new files into the "BepInExPayload" folder there.
EDIT: Forgot to mention I'm using 1.0.8
When i have Valheim Support enabled as well, I get an error that Valheim Support can't find/access changelog.txt in Valheim folder.
This error occurs on every deployment of mods. But the file is there.
If I disable one of these extensions, no error to see. What is the "correct" extension to use?
Updated that extension as it got improved, then Vortex updated on day (27th of March?). And I got Valheim Support 1.0.4 and Game:Valheim 1.0.4. In the prosess of troubleshooting, I cleared out all Valheim related stuff from Vortex, and installed Valheim Support 1.0.4 by the Vortex link at Nexus.
Still got the error so I disabled Valheim Support, and didn't think more about it. But then I didn't get notified about updates to Valheim Support, of course. :) Valheim and modding worked just fine.
By accident I saw that Game:Valheim was at 1.0.4 and Valheim Support was at v 1.0.6 (the disabled version was 1.0.4), so I updated it. And got reminded about the error, once again. This time I disabled / enabled as shown at the picture.
My modding for Valheim still works, and can add, remove, update, etc with no problem.
Just thought it was a bit odd... Could it be, that there is a glitch when Vortex is checking for modding support for the game? (Just guessing here)
Edit: Forgot to mention; I'm using Vortex 1.4.9 and have enabled Beta version for Vortex client.
And it is not a big deal, everything is working, even with the annoying red error in the Notification bell :)
Soon as I disabled one of them, no error to see.
I have a requests:
Can you please allow us to manually install bepinex? Because the current version you provide is (once more) outdated and I would prefer to be able to just download it, do a "install from file" and set "Mod Type: BepInEx Installation" and not have it overwritten every time something else changes, including then getting the "unstripped dll's" message. The tight coupling between this extension and the mod loader is really frustrating.
Regarding the unstripped dlls - the latest version of the extension has full support for both Denikson's package and 1F31A's Full BepInEx package - in both cases, it will not use the BepInEx assemblies, but it will install and use the unstripped assemblies as distributed by those packages rather than the unstripped_managed mod; so as long as you have either of those installed, enabled and deployed, the message should not appear.
I understand the reasoning why it is tightly coupled and am aware that many users are not that experienced with such things, it was just a really frustrating moment yesterday, as I did the update to the newest Valheim version with backuping everything first and then updated bepinex and some mods, update bepinex again (because it was overwritten as it was still on 5.4.8.0 at that point), had some strange problem (probably forgot to copy some file) and redid it all again with starting the game inbetween all those steps to verify everything was working. Typical version update hell.
So while I still would love some possibility to get BepInEx from some external source, I can understand why you don't want to add that.
Mine's still 1.0.3 and when I downloaded 1.0.4 manually and dragged it in it was added separately with the name "Game: Valheim" where as 1.0.3 is named "Valheim Support".
1.0.3's author is Nagev and 1.0.4's is Black Tree Gaming Ltd.
Is there some incompatibility that will prevent the automatic update?
As a use case example: Having one ini for Mod A when playing a local game, but a different ini when playing on Server A.
I think it was v1.02 that had a notes on the functionality of the in-game mod manager. All I recall was F1 to open it, but I can't remember how to 'save' them, and I can't find those notes anymore.
I made changes to mod settings using the F1 interface, found no save button, clicked outside the borders of the manager, it closed. I entered the game, and the changes aren't applied.
Can someone please refresh me or point to the notes? I don't see them on the currently posted change log.
TIA!