Graybark Posted May 16, 2018 Share Posted May 16, 2018 Is there a way to prevent Vortex from touching plugins.txt at all when auto-sorting is disabled. It still generates a load order when starting it up that slightly differs from how LOOT would sort it. You can tell by the "Automatically generated by Vortex" line. Would be nice if we could disable that startup editing. Link to comment Share on other sites More sharing options...
Grestorn Posted May 16, 2018 Share Posted May 16, 2018 Why would it be different than LOOT? Just because the hadline says that it‘s created by Vortex is neither proof nor hint that the result is different. Link to comment Share on other sites More sharing options...
Tannin42 Posted May 16, 2018 Share Posted May 16, 2018 If Vortex couldn't touch the plugins.txt then it also wouldn't be able to enable/disable plugins. If you want that you can just disable the entire "gamebryo-plugin-management" extension. Link to comment Share on other sites More sharing options...
Graybark Posted May 16, 2018 Author Share Posted May 16, 2018 Why would it be different than LOOT? Just because the hadline says that it‘s created by Vortex is neither proof nor hint that the result is different. The result is different. It treats the disabled SSEMerged and Bashed patch differently. That line was just my way of proving that it is indeed Vortex that does it. If Vortex couldn't touch the plugins.txt then it also wouldn't be able to enable/disable plugins. If you want that you can just disable the entire "gamebryo-plugin-management" extension.True. I did not think of that. What about the editing it on start up though? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.