This mod should overwrite ANY mod it conflicts with
If it conflicts with another mod, it's because that mod is trying to bundle this mod with it, and they almost certainly bundled an outdated version that is going to cause you issues.
IMPORTANT: If you are using Skyrim version 1.6+, you must install the AE version of PapyrusUtil and Address Library. It DOES NOT MATTER if you don't have the Anniversary Edition DLC; any version past 1.5.97 is considered AE.
Make sure your Address Library and SKSE64 install are fully up to date.
And as always, make sure no mods are overwriting the up-to-date version of PapyrusUtil with an outdated version (such as Simply Knock and Campfire)
If you are still getting an error message somewhere, try running the default Skyrim launcher once from Steam or directly (via SkyrimSELauncher.exe in the main folder) and then go back to launching with skse and/or your mod manager.
The latest release will ONLY ever be compatible with the newest version released on Steam, currently v1.6.1170. Anything other than that is not supported, and you will have to download an older version of PapyrusUtil that matches your installed version.
Obviously, if you have the GoG version of the game at version 1.6.659, install the GoG version.
CACO is causing issues with some mods at the moment. I had bugs and issues with my game, to the point where I wanted to run through a wall, and after testing, I removed CACO, and everything works fine now. It's not this, or Tweaks or Extender or Address Library or File Access causing issues, it's legit CACO causing issues with certain load orders at the moment. I did leave a comment on CACO's page, but for now, if you use CACO, remove it and test again.
Same problem here. Fully reinstalled and it still says it's incompatible. Any ideas?
Edit: overwriting was not the issue (according to vortex) and reinstalling didn't fix, but when I combed through with loot (and corrected the groups/manual load after rules) and made sure all mods were updated, it magically fixed it. I'm guessing there was an overwrite error with an out of date mod or that the load order was messing things up (as always)
Not sure if this will be helpful to anyone else, but I was convinced StorageUtil.dll was referring to this mod, but it was actually referring to Wearable Lanterns. Turning that off got rid of my error.
If someone still having this issue, you got a mod that overwriting papyrus dll. The dll and other scripts should NOT be overwritten by any other mod. That fixed my issue.
I had the same problem. Then I realised that the address library had been disabled. Wondering if the game actually did this. Reinstalled it and now all papyrus items seem to be working fine. Same with MCM.
Still have error messages, even after deleting every mod. Clear Skyrim SE 1.6.1170.0 version only with SKSE 2.2.6 and Address Library installed. Using Mod Organizer 2. Please, help
A little heads up for any SE 1.16.1170 newcomers getting the error message when starting SKSE with this mod.
When you install the extra required mod "Address Library for SKSE";
MAKE SURE you install the "All in One (Anniversary Edition)".
I mistakenly thought the All in One version would include the anniversary edition version, since "All in One" can be misinterpreted and I was rushing through. If you take a second longer to read the other versions, there is a second option, and it absolutely is required for Papyrus to work on version 1.16.1170
Hello everyone, I am wondering if there is a way that I can get a version of this that is for SKSE version 2.2.1, and AE/SE 1.6.640? I think that might be the cause of a few issues I've been running into.
I've been attempting to install Papyrus's latest vr of 4.6, however it only ever installs 4.0 on a fresh download here. I have uninstalled, downloaded a new file, and reinstalled multiple times and had the same issue. Is there a different location from DL from?
If you mean as a value for stuff like SetFormValue() or FormListAdd(), objects that have been destroyed will return as none.
If you mean as the object the variables are stored on for the ObjKey parameter is destroyed, all of it's values will be cleared out on load.
There is a caveat to that last one, however, as there can be a rare scenario where they wrongly stick around. On save load the ObjKey's are validated to see if they still exist, and if they do, if their form type still matches the expected form type. So if the object is destroyed but the engine then re-uses that freed form ID to make a new objectreference and that object has the exact same form type of the reference that was previously using that form id before a validation has had a chance to occur, then it's going to carry over the previous objectrefrences storageutil values.
That should be a pretty rare occurrence, though. If you wanna be paranoid, you can use StorageUtil.debug_Cleanup() to force the cleanup without waiting for a save load to trigger it.
2396 comments
If it conflicts with another mod, it's because that mod is trying to bundle this mod with it, and they almost certainly bundled an outdated version that is going to cause you issues.
Make sure your Address Library and SKSE64 install are fully up to date.
And as always, make sure no mods are overwriting the up-to-date version of PapyrusUtil with an outdated version (such as Simply Knock and Campfire)
If you are still getting an error message somewhere, try running the default Skyrim launcher once from Steam or directly (via SkyrimSELauncher.exe in the main folder) and then go back to launching with skse and/or your mod manager.
The latest release will ONLY ever be compatible with the newest version released on Steam, currently v1.6.1170. Anything other than that is not supported, and you will have to download an older version of PapyrusUtil that matches your installed version.
Obviously, if you have the GoG version of the game at version 1.6.659, install the GoG version.
and after testing, I removed CACO, and everything works fine now. It's
not this, or Tweaks or Extender or Address Library or File Access causing
issues, it's legit CACO causing issues with certain load orders at the
moment. I did leave a comment on CACO's page, but for now, if you use
CACO, remove it and test again.
I have updated Papyrus Util for 1170 but SKSE still says they disabled the DLL because it's not compatible with the version of the game.
Someone pls help.
EDIT: NVM fixed
Edit: overwriting was not the issue (according to vortex) and reinstalling didn't fix, but when I combed through with loot (and corrected the groups/manual load after rules) and made sure all mods were updated, it magically fixed it. I'm guessing there was an overwrite error with an out of date mod or that the load order was messing things up (as always)
When you install the extra required mod "Address Library for SKSE";
MAKE SURE you install the "All in One (Anniversary Edition)".
I mistakenly thought the All in One version would include the anniversary edition version, since "All in One" can be misinterpreted and I was rushing through.
If you take a second longer to read the other versions, there is a second option, and it absolutely is required for Papyrus to work on version 1.16.1170
Cheers!
I've been attempting to install Papyrus's latest vr of 4.6, however it only ever installs 4.0 on a fresh download here. I have uninstalled, downloaded a new file, and reinstalled multiple times and had the same issue. Is there a different location from DL from?
>Doesn't work
>Download weebery clone jutsu
>Works perfectly
I don't know why I even bothered going to the non-weeb part of nexus. Seriously, what did I expect.
If you mean as a value for stuff like SetFormValue() or FormListAdd(), objects that have been destroyed will return as none.
If you mean as the object the variables are stored on for the ObjKey parameter is destroyed, all of it's values will be cleared out on load.
There is a caveat to that last one, however, as there can be a rare scenario where they wrongly stick around. On save load the ObjKey's are validated to see if they still exist, and if they do, if their form type still matches the expected form type. So if the object is destroyed but the engine then re-uses that freed form ID to make a new objectreference and that object has the exact same form type of the reference that was previously using that form id before a validation has had a chance to occur, then it's going to carry over the previous objectrefrences storageutil values.
That should be a pretty rare occurrence, though. If you wanna be paranoid, you can use StorageUtil.debug_Cleanup() to force the cleanup without waiting for a save load to trigger it.