It looks like it does not work with GOG version :/ I mean SSEEdit does not find the INIs with new paths and this plugin does not take command line arguments into account.
The extension ignores additional command line parameters that have been set in the Vortex tools which would allow to setup custom paths for INIs, loadorder.txt etc..
In the event someone else finds this post in a hunt to diagnose this, there IS a silly workaround (currently): In the file %AppData%\Vortex\Plugins\Vortex Extension Update - xEdit Cleaning Extension v1.0.13\index.jsfind the section marked "const xEditParams" Change it to this (AND FOR THE LOVE OF TALOS, PLEASE CHANGE "YOUR-LOGIN" TO MATCH YOUR USERNAME!): const xEditParams = { "quickautoclean": ["{gamePara}", "-quickautoclean", "-autoexit", "-autoload", "-D:\"C:\\GOG Games\\Skyrim Anniversary Edition\\Data\\\"", "-I:\"C:\\Users\\YOUR-LOGIN\\Documents\\My Games\\Skyrim Special Edition GOG\\Skyrim.ini\"", "-P:\"C:\\Users\\YOUR-LOGIN\\AppData\\Local\\Skyrim Special Edition GOG\\plugins.txt\"", "{pluginName}"], "autoloadplugin": ["{gamePara}", "-D:\"C:\\GOG Games\\Skyrim Anniversary Edition\\Data\\\"", "-I:\"C:\\Users\\YOUR-LOGIN\\Documents\\My Games\\Skyrim Special Edition GOG\\Skyrim.ini\"", "-P:\"C:\\Users\\YOUR-LOGIN\\AppData\\Local\\Skyrim Special Edition GOG\\plugins.txt\"", "-quickedit:{pluginName}"], "autoloadall": ["{gamePara}", "-D:\"C:\\GOG Games\\Skyrim Anniversary Edition\\Data\\\"", "-I:\"C:\\Users\\YOUR-LOGIN\\Documents\\My Games\\Skyrim Special Edition GOG\\Skyrim.ini\"", "-P:\"C:\\Users\\YOUR-LOGIN\\AppData\\Local\\Skyrim Special Edition GOG\\plugins.txt\"", "-autoload"] }; Now, why is this a "Silly" workaround? Because if the plugin updates? This breaks. Also, if your game is somewhere else? It won't work (without modification). And if you have another Bethesda game (Like Fallout4, morrowind, etc...) and try to use the plugin? It breaks. And possibly breaks your other game.
A better way might be to manipulate "gameParam" to be an index instead of a string, and stuff all this stuff there, but frankly, I am no good with javascript, and I leave that to smarter folk than I.
Pardon me, I'm hoping someone can help. I cannot get this tool to run; Vortex keeps telling me "xEdit not found."
The problem is this, but I don't know how to fix it: Up until recently (today) I had Vortex pointing to a folder "....\Desktop\Skyrim stuff and mods\SSEEdit OLDER 4.1.3 Experimental\xEdit_4.1.3f_EXTREMELY_EXPERIMENTAL\SSEEdit.exe"
I switched the dashlet to: "...\Desktop\Skyrim stuff and mods\SSEEdit 4.1.5f-164-4-1-5f-1714283656\SSEEdit 4.1.5f\SSEEdit.exe"
I closed Vortex, opened it again, hoping it would work fine. The dashlet does show and retain the new folder, and opens correctly. I ran it, closed Vortex again, and re-opened it.
However, I still get the error "xEdit not found" when trying to clean a plugin.
When I click said error tab "More", it shows me the *old* folder. Why on earth is it trying to look for the old folder when I just changed it and it's working correctly from the dash?
By the way, after changing the folder, I decided to delete this extension, open Vortex to verify it was gone, then closed and opened it again, and re-installed this extension. It's still trying to look in the old "experimental" folder. >_>
Please, any guidance on how to fix this would be appreciated!
Newly installed SSEEdit 4.1.5f and connected it in the tools, but no matter what I do (like disable/enable, reinstalling, manual downloading installing) the extension still points to the old files.
My workaround is now that I pasted a copy of SSEEdit 4.1.5f into the old SSEdit-folder.
Did you make sure that SSEedit is in the tools section of the dashboard? it will not run unless you have sseedit activated in the tools section of vortex
Installing it from Vortex for FO4 installs this extension (validated when I follow it back to Nexus from Vortex). Upon clicking any Vortex xEdit button you get a Vortex error "xEdit not found".
The directions for this extension say to extract "ElminsterAU's xEdit 7z archive" to %appdata%\Vortex\plugins. It's not clear if you are supposed to put the files in the /plugins folder itself or in a subfolder called: "%appdata%\Vortex\plugins\Vortex Extension Update - xEdit Cleaning Extension v1.0.13" which is what Vortex does automatically. I assume this is what is supposed to happen even though the extension author does not specify it.
I downloaded and moved the files from the "ElminsterAU's xEdit 7z archive" into the folder Vortex created and still get the error.
Getting more info from the error message, it is looking for FO4edit which is NOT in the "ElminsterAU's xEdit 7z archive" the extension author offers as a link. I already had FO4Edit, so I moved the FO4Edit files into that same folder and still get the "xEdit not found" error.
I can find no place in Vortex, nor in the Vortex plugin json file where the specific tool on the dashlet is mapped to a specific path and executable so cannot resolve this further until I find another approach. Where is a tool in Vortex mapped to a specific path/executable?
*** Update later that evening.... It appears the executable mappings are done using vortex-api calls from the index.js included with the extension. The extension index.js does not get the configuration for xEdit from the vortex-api and then fails as a result of that. The vortex-api only reports BodySlide and F4SE on my installation as "tools" and does not include the xEdit extension that Vortex installed. I can't tell if the problem is with the api or the getSafe() call from the index.js. I can't find documentation on the getSafe() call on GitHub.
Here are the some debug log statements I put in the index.js to go to the vortex.log to demonstrate this: Thu, 06 Jul 2023 06:51:34 GMT - debug: [xedit-cleaning-extension] let's see what we get from const tools = vortex_api_1.util.getSafe(state, ['settings', 'gameMode', 'discovered', activeGameId, 'tools'], undefined);: Thu, 06 Jul 2023 06:51:34 GMT - debug: [xedit-cleaning-extension] Object.keys(tools) Thu, 06 Jul 2023 06:51:34 GMT - debug: [xedit-cleaning-extension] bodyslide,f4se ;-----------------------------------------------------------------------------------Note that Object.keys(tools) only reports BS and f4se, not xEdit ext which it installed
Thu, 06 Jul 2023 06:51:34 GMT - debug: [xedit-cleaning-extension] let's see what we get from const xEditKey = tools ? Object.keys(tools).find(t => t === xEditData.exeName) : undefined;: Thu, 06 Jul 2023 06:51:34 GMT - debug: [xedit-cleaning-extension] xEditKey Thu, 06 Jul 2023 06:51:34 GMT - debug: [xedit-cleaning-extension] undefined ;------------------------------------------------now everything is undefined
Thu, 06 Jul 2023 06:51:34 GMT - debug: [xedit-cleaning-extension] let's see what we get from const xEditTool = xEditKey ? tools[xEditKey] : undefined;: Thu, 06 Jul 2023 06:51:34 GMT - debug: [xedit-cleaning-extension] xEditTool Thu, 06 Jul 2023 06:51:34 GMT - debug: [xedit-cleaning-extension] undefined ;------------------------------------------------again undefined
Thu, 06 Jul 2023 06:51:34 GMT - error: xEdit not found text=Vortex could not find FO4Edit. Please check the tool in your starter dashlet is pointing to the right place., wrap=true ;------------------------------------------------Vortex throws the error in the UI because it can't find a path to the exe, it's undefined
I'm not sure where you're reading that. This EXTENSION goes in the plugins folder. XEdit can be installed anywhere and you must configure the shortcut under "Tools" on the dashboard. I suspect you're just doing it wrong tbh.
Thank you!!! I had no idea there was that section on the dashboard. And actually I don't use the dashboard for anything and forgot it was even there. Works like a charm. Learn something new everyday!
This extension opens FNIS rather than xEdit. Vortex v1.12.3 xEdit v4.1.5f xEdit and xEdit Quck Auto Clean both work properly from the Vortex Dashboard. When using this extension on the Plugins page to "Open in xEdit" or "Clean with xEdit" or click on the new "Open xEdit" button on the toolbar, the FNIS application is opened instead. Any suggestions?
Update: I removed the FNIS dashlet. What remained was the same dashlet in the same location on my dashboard with the same FNIS icon, but the name changed from FNIS to SSEEdit. So I removed it (the one that said SSEEdit) again and it was truly removed this time. The existing xEdit dashlet still works, as does the existing xEdit Quick Auto Clean.
Now the extension buttons return an error, "xEdit not found" and "More" reveals "Vortex could not find SSEEdit. Please check the tool in your starter dashlet is pointing to the right place."
I am using xEdit.exe. i see the extension is named xEdit Cleaning Extension, but is it looking for SSEEdit rather than xEdit?
I got it working. I removed the xEdit dashlet and added a new one. That solved the problem.
FYI, regarding your statement that "Vortex is probably borked up" I have to agree. When I removed my xEdit dashlet, it did the same thing as I described above about removing FNIS, but in reverse. The xEdit dashlet remained in the same location, but changed the name of the dashlet to FNIS. I had to remove it twice, as described above.
As I then added the new dashlet for SSEEdit, the "Add" menu gave me two named options, FNIS and SSEEdit. Apparently as I have kept the same installation of Vortex for several years and gone through many, many updates, somewhere along the way those named options were added in an update and it messed with what you called a "specific tool ID." Apparently, that update way back whenever didn't go smoothly. That's my best guess, for what it is worth.
Thanks for the extension, and thanks for the rapid reply!
84 comments
I mean SSEEdit does not find the INIs with new paths and this plugin does not take command line arguments into account.
In the file
%AppData%\Vortex\Plugins\Vortex Extension Update - xEdit Cleaning Extension v1.0.13\index.jsfind the section marked "const xEditParams"Change it to this (AND FOR THE LOVE OF TALOS, PLEASE CHANGE "YOUR-LOGIN" TO MATCH YOUR USERNAME!):
const xEditParams = {"quickautoclean": ["{gamePara}", "-quickautoclean", "-autoexit", "-autoload", "-D:\"C:\\GOG Games\\Skyrim Anniversary Edition\\Data\\\"", "-I:\"C:\\Users\\YOUR-LOGIN\\Documents\\My Games\\Skyrim Special Edition GOG\\Skyrim.ini\"", "-P:\"C:\\Users\\YOUR-LOGIN\\AppData\\Local\\Skyrim Special Edition GOG\\plugins.txt\"", "{pluginName}"],
"autoloadplugin": ["{gamePara}", "-D:\"C:\\GOG Games\\Skyrim Anniversary Edition\\Data\\\"", "-I:\"C:\\Users\\YOUR-LOGIN\\Documents\\My Games\\Skyrim Special Edition GOG\\Skyrim.ini\"", "-P:\"C:\\Users\\YOUR-LOGIN\\AppData\\Local\\Skyrim Special Edition GOG\\plugins.txt\"", "-quickedit:{pluginName}"],
"autoloadall": ["{gamePara}", "-D:\"C:\\GOG Games\\Skyrim Anniversary Edition\\Data\\\"", "-I:\"C:\\Users\\YOUR-LOGIN\\Documents\\My Games\\Skyrim Special Edition GOG\\Skyrim.ini\"", "-P:\"C:\\Users\\YOUR-LOGIN\\AppData\\Local\\Skyrim Special Edition GOG\\plugins.txt\"", "-autoload"]
};
Now, why is this a "Silly" workaround? Because if the plugin updates? This breaks. Also, if your game is somewhere else? It won't work (without modification). And if you have another Bethesda game (Like Fallout4, morrowind, etc...) and try to use the plugin? It breaks. And possibly breaks your other game.
A better way might be to manipulate "gameParam" to be an index instead of a string, and stuff all this stuff there, but frankly, I am no good with javascript, and I leave that to smarter folk than I.
Good luck!
The problem is this, but I don't know how to fix it: Up until recently (today) I had Vortex pointing to a folder "....\Desktop\Skyrim stuff and mods\SSEEdit OLDER 4.1.3 Experimental\xEdit_4.1.3f_EXTREMELY_EXPERIMENTAL\SSEEdit.exe"
I switched the dashlet to: "...\Desktop\Skyrim stuff and mods\SSEEdit 4.1.5f-164-4-1-5f-1714283656\SSEEdit 4.1.5f\SSEEdit.exe"
I closed Vortex, opened it again, hoping it would work fine. The dashlet does show and retain the new folder, and opens correctly. I ran it, closed Vortex again, and re-opened it.
However, I still get the error "xEdit not found" when trying to clean a plugin.
When I click said error tab "More", it shows me the *old* folder. Why on earth is it trying to look for the old folder when I just changed it and it's working correctly from the dash?
By the way, after changing the folder, I decided to delete this extension, open Vortex to verify it was gone, then closed and opened it again, and re-installed this extension. It's still trying to look in the old "experimental" folder. >_>
Please, any guidance on how to fix this would be appreciated!
Newly installed SSEEdit 4.1.5f and connected it in the tools, but no matter what I do (like disable/enable, reinstalling, manual downloading installing) the extension still points to the old files.
My workaround is now that I pasted a copy of SSEEdit 4.1.5f into the old SSEdit-folder.
Thank you!!! :3
Installing it from Vortex for FO4 installs this extension (validated when I follow it back to Nexus from Vortex). Upon clicking any Vortex xEdit button you get a Vortex error "xEdit not found".
The directions for this extension say to extract "ElminsterAU's xEdit 7z archive" to %appdata%\Vortex\plugins. It's not clear if you are supposed to put the files in the /plugins folder itself or in a subfolder called: "%appdata%\Vortex\plugins\Vortex Extension Update - xEdit Cleaning Extension v1.0.13" which is what Vortex does automatically. I assume this is what is supposed to happen even though the extension author does not specify it.
I downloaded and moved the files from the "ElminsterAU's xEdit 7z archive" into the folder Vortex created and still get the error.
Getting more info from the error message, it is looking for FO4edit which is NOT in the "ElminsterAU's xEdit 7z archive" the extension author offers as a link. I already had FO4Edit, so I moved the FO4Edit files into that same folder and still get the "xEdit not found" error.
I can find no place in Vortex, nor in the Vortex plugin json file where the specific tool on the dashlet is mapped to a specific path and executable so cannot resolve this further until I find another approach. Where is a tool in Vortex mapped to a specific path/executable?
*** Update later that evening....
It appears the executable mappings are done using vortex-api calls from the index.js included with the extension. The extension index.js does not get the configuration for xEdit from the vortex-api and then fails as a result of that. The vortex-api only reports BodySlide and F4SE on my installation as "tools" and does not include the xEdit extension that Vortex installed. I can't tell if the problem is with the api or the getSafe() call from the index.js. I can't find documentation on the getSafe() call on GitHub.
Here are the some debug log statements I put in the index.js to go to the vortex.log to demonstrate this:
Thu, 06 Jul 2023 06:51:34 GMT - debug: [xedit-cleaning-extension] let's see what we get from const tools = vortex_api_1.util.getSafe(state, ['settings', 'gameMode', 'discovered', activeGameId, 'tools'], undefined);:
Thu, 06 Jul 2023 06:51:34 GMT - debug: [xedit-cleaning-extension] Object.keys(tools)
Thu, 06 Jul 2023 06:51:34 GMT - debug: [xedit-cleaning-extension] bodyslide,f4se
;-----------------------------------------------------------------------------------Note that Object.keys(tools) only reports BS and f4se, not xEdit ext which it installed
Thu, 06 Jul 2023 06:51:34 GMT - debug: [xedit-cleaning-extension] let's see what we get from const xEditKey = tools ? Object.keys(tools).find(t => t === xEditData.exeName) : undefined;:
Thu, 06 Jul 2023 06:51:34 GMT - debug: [xedit-cleaning-extension] xEditKey
Thu, 06 Jul 2023 06:51:34 GMT - debug: [xedit-cleaning-extension] undefined
;------------------------------------------------now everything is undefined
Thu, 06 Jul 2023 06:51:34 GMT - debug: [xedit-cleaning-extension] let's see what we get from const xEditTool = xEditKey ? tools[xEditKey] : undefined;:
Thu, 06 Jul 2023 06:51:34 GMT - debug: [xedit-cleaning-extension] xEditTool
Thu, 06 Jul 2023 06:51:34 GMT - debug: [xedit-cleaning-extension] undefined
;------------------------------------------------again undefined
Thu, 06 Jul 2023 06:51:34 GMT - error: xEdit not found text=Vortex could not find FO4Edit. Please check the tool in your starter dashlet is pointing to the right place., wrap=true
;------------------------------------------------Vortex throws the error in the UI because it can't find a path to the exe, it's undefined
Now the extension buttons return an error, "xEdit not found" and "More" reveals "Vortex could not find SSEEdit. Please check the tool in your starter dashlet is pointing to the right place."
I am using xEdit.exe. i see the extension is named xEdit Cleaning Extension, but is it looking for SSEEdit rather than xEdit?
FYI, regarding your statement that "Vortex is probably borked up" I have to agree. When I removed my xEdit dashlet, it did the same thing as I described above about removing FNIS, but in reverse. The xEdit dashlet remained in the same location, but changed the name of the dashlet to FNIS. I had to remove it twice, as described above.
As I then added the new dashlet for SSEEdit, the "Add" menu gave me two named options, FNIS and SSEEdit. Apparently as I have kept the same installation of Vortex for several years and gone through many, many updates, somewhere along the way those named options were added in an update and it messed with what you called a "specific tool ID." Apparently, that update way back whenever didn't go smoothly. That's my best guess, for what it is worth.
Thanks for the extension, and thanks for the rapid reply!