How do you UN manage a game

[obmike]

I have looked everywhere and I cannot find an option to UNmanage a game once it's been managed. Why is it so hard to do this and why is it not covered in the KB.

[DoctorKaizeld]

you have to change which manager handles Nexus downloads via your browser

[HadToRegister]

I have looked everywhere and I cannot find an option to UNmanage a game once it's been managed. Why is it so hard to do this and why is it not covered in the KB.

 

 

Are you planning to manage it with another mod manager, or are you just planning to not manage it at all?

 

Just CTRL+A and PURGE your mods for that game (In order to find PURGE in the menu on the Mod or Plugin tab, go to SETTINGS---->INTERFACE---->Enable Advanced Mode)

Then use a different mod manager

[Tannin42]

The way to remove a game from the "Managed" tab is by removing all profiles you had for it. Even if you haven't enabled profile management, managing a game means having at least a default profile for it.

[obmike]

The way to remove a game from the "Managed" tab is by removing all profiles you had for it. Even if you haven't enabled profile management, managing a game means having at least a default profile for it.

As you said, that only removes the game from the "Managed" tab. This does not reset a games files / folders to the state they were in before they were "managed" by Vortex. For example, Documents\My Games\Skyrim still has the Skyrim.ini.baked, Skyrim.ini.base, SkyrimPrefs.ini.baked, SkyrimPrefs.ini.base (maybe others as well in other locations, but I have not looked yet) files left behind after removing all the profiles for the game which is not what I desire. So again I ask the question how does one "UN-manage" a game so that it returns to the state it was in before it was "managed" by Vortex?

 

To answer the other users questions, I will not be using any mod manager and the reason I want to "UN-manage" the game is because I was only using it as a test game to test the capabilities of Vortex. I have no actual plans on using mods for this particular game.

[HadToRegister]

 

The way to remove a game from the "Managed" tab is by removing all profiles you had for it. Even if you haven't enabled profile management, managing a game means having at least a default profile for it.

As you said, that only removes the game from the "Managed" tab. This does not reset a games files / folders to the state they were in before they were "managed" by Vortex. For example, Documents\My Games\Skyrim still has the Skyrim.ini.baked, Skyrim.ini.base, SkyrimPrefs.ini.baked, SkyrimPrefs.ini.base (maybe others as well in other locations, but I have not looked yet) files left behind after removing all the profiles for the game which is not what I desire. So again I ask the question how does one "UN-manage" a game so that it returns to the state it was in before it was "managed" by Vortex?

 

To answer the other users questions, I will not be using any mod manager and the reason I want to "UN-manage" the game is because I was only using it as a test game to test the capabilities of Vortex. I have no actual plans on using mods for this particular game.

 

 

Then Uninstall all the mods with Vortex, and remove your profiles.

 

YOu can delete the baked and base files by hand

[obmike]

 

 

The way to remove a game from the "Managed" tab is by removing all profiles you had for it. Even if you haven't enabled profile management, managing a game means having at least a default profile for it.

As you said, that only removes the game from the "Managed" tab. This does not reset a games files / folders to the state they were in before they were "managed" by Vortex. For example, Documents\My Games\Skyrim still has the Skyrim.ini.baked, Skyrim.ini.base, SkyrimPrefs.ini.baked, SkyrimPrefs.ini.base (maybe others as well in other locations, but I have not looked yet) files left behind after removing all the profiles for the game which is not what I desire. So again I ask the question how does one "UN-manage" a game so that it returns to the state it was in before it was "managed" by Vortex?

 

To answer the other users questions, I will not be using any mod manager and the reason I want to "UN-manage" the game is because I was only using it as a test game to test the capabilities of Vortex. I have no actual plans on using mods for this particular game.

 

 

Then Uninstall all the mods with Vortex, and remove your profiles.

 

YOu can delete the baked and base files by hand

 

You are missing the point. This should all be done for me when I "un-manage" a game. Unless it is outlined somewhere that I have not seen, there is no way for me as an end user to know what files, folders are created / edited when a game gets "managed" with Vortex and to be honest I don't want to know. All I want as an end user if for Vortex to clean up after itself when I am done with it.

 

Additionally, as I said in my previous post the *.baked and *.base files are just one example of files that are left behind after a game is "un-managed" by vortex. However, I would not be surprised if there where other files / folders that created / edited when a game gets "managed" that are never removed or returned to their "pre-managed" state as part of the "un-management" process so just removing those files alone would not really be enough and as I said before, as an end user I should not be worried about such things and this should all be handled by the application itself.

 

TLDR: It is just good coding etiquette to let the application manage as much of itself as possible and not unnecessary burden your end user with task that the application can and SHOULD handle on it's own. My $.02

[HadToRegister]

 

You are missing the point. This should all be done for me when I "un-manage" a game. Unless it is outlined somewhere that I have not seen, there is no way for me as an end user to know what files, folders are created / edited when a game gets "managed" with Vortex and to be honest I don't want to know. All I want as an end user if for Vortex to clean up after itself when I am done with it.

 

 

Additionally, as I said in my previous post the *.baked and *.base files are just one example of files that are left behind after a game is "un-managed" by vortex. However, I would not be surprised if there where other files / folders that created / edited when a game gets "managed" that are never removed or returned to their "pre-managed" state as part of the "un-management" process so just removing those files alone would not really be enough and as I said before, as an end user I should not be worried about such things and this should all be handled by the application itself.

 

TLDR: It is just good coding etiquette to let the application manage as much of itself as possible and not unnecessary burden your end user with task that the application can and SHOULD handle on it's own. My $.02

 

 

 

If you believe it's good 'coding etiquette" for the things you've suggested, then you should submit your code to the github repository, so you can help develop Vortex so we can all experience the improvements you're suggesting.

[Guest deleted34304850]

Just to clarify, your idea/suggestion is similar in concept to an uninstaller package? So that if you decide to un-manage a game with Vortex, anything created by Vortex for it to manage the game would be removed completely, and without any kind of user interaction?

 

That's not a bad idea at all, actually.

 

You may want to offer this idea to the developers as an enhancement to the tool.

[Tannin42]

A more automated way of cleaning things up in preparation of an uninstall or unmanaging the game is actually on my todo list, but it's far more complex than you might think and thereby the risk of something going wrong is massive, so the feature is basically rated "effort: high, risk: high, gain: low".

 

Let's say you start managing a game, create a second profile, add mods to the profile, change settings in your ini files, create profile-local save games.

Then you uninstall Vortex.

What is vortex to do? Go back to the state before the game was managed? This would involve deleting the profile, reverting all ini settings you made while using it and the save games. Surely you can see how users might not expect their savegames to get deleted.

Or, turn the last profile you used into a now permanent state? But that wouldn't be a "revert" and it'd involve deleting the first profile with all of _its_ settings and profile-local save games - same problem.

We could try to "merge" the savegames and settings, but that too wouldn't be a revert and it would still bear the risk of overwriting things (e.g. both profiles would contain autosaves/quicksaves that are not uniquely named).

This gets much more complicated since Vortex supports so many games, other games may require changes to xml files or the registry.

 

Also: You might expect Vortex to remove all the mods when you "unmanage" a game, another user may expect vortex to leave the mods installed and just stop managing them, so they act as if they were installed manually. A third user might expect Vortex to not drop any information so you can "re-manage" the game at a later time and just continue where you left off.

 

A cleanup will always either leave too much or delete too much for some users expectations and I'd much rather have a user mildly unhappy for having to do cleanup manually than have a user furious because we "cleaned up" a mod that he had worked on for months.