![]() ![]() In this use case, mod authors would be required to manage the mod manually (add it outside Vortex) as IMO catering for it from inside Vortex introduces potential for regular users to mess up.ģ, 4. Regarding the items you raised in your last post:Ī notification is now displayed whenever the user changes the LO Hi apologies for not keeping you up to date regarding BaS load ordering - we had a chat with KospY and the game implementation at the time could not guarantee that mods would indeed load in alphabetical order, reason why we waited for a while for this to get rectified in the game first. I have not included any log files as I have not encountered any errors or issues. This is pretty essential for load order management to be effective. ZZZ) if there are non-Vortex mods installed.Īs you've already identified, non-Vortex installed mods (even with valid manifests) are not visible in the load order and cannot be managed. There's currently no way to send a mod to the end of the load order (e.g. There should be a way to exclude mods from load order management. As a result, mods are always prefixed with the load order tag (AAA, AAB) which may introduce load order issues that were unintended by the mod author. There's currently no way to 'un-manage' a mod from the load order. I would suggest either displaying a notification to the user that the load order has changed and requires a redeployment OR modifying the filesystem when the user changes load order in Vortex without redeployment. It's not clear to the user that they must 'Deploy' after changing the load order. Ok from what I've tried so far it seems to work however I have a few notes on usability. ![]() Please let me know if you run into any issues, and always include your latest vortex.log file in your replies so I can debug any odd behaviour - you can find the log files in your "%appdata%/Vortex" directory.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |