Jump to content

Destroyer5

Premium Member
  • Posts

    14
  • Joined

  • Last visited

Nexus Mods Profile

About Destroyer5

Profile Fields

  • Website URL
    https://www.youtube.com/channel/UCWBMX_RGoHnawbu0lVlo7zA
  • Country
    United States

Destroyer5's Achievements

Apprentice

Apprentice (3/14)

0

Reputation

  1. Hello, Is there a way to remove the alert to https://www.nexusmod...4244/?tab=files Since they blocked me for whatever reason lol. I dont want to keep getting updates on a mod I cant use. Thank you.
  2. I noticed that the load order will not update until you shut down and reload Vortex. Is there a fix?
  3. When I try to lock a mod in a particular load order it locks at first, but when I add a new mod the program changes the lock position and messes with my load order. I have bat files that need particular mods to stay and locked, so I do not get bat problems. Is there a way to force the program to never move my locked mod and sort the rest around my locked mod?
  4. Lol, are you for real? Overdramatic much? That post should have started with "I have a dream..." Anyway, I have explained to you why the solution you propose is impractical. If you didn't understand something in my posts I will be happy to go into detail, but I have no interest in going in circles on this. Your entire argument rests on the assumption that a mod consists of only one file which we all know is not usually the case - why don't you think about the consequences of that for a bit instead of repeating how simple and common sense your proposal is over and over? Does it not occur to you that maybe you're the one missing something that the people disagreeing with you have understood? Anyway as I stated before those that say they cant do something will fall behind. This person made it possible to use NMM in Vr, https://www.nexusmods.com/fallout4/mods/32511, and guess what??? NMM actually warns you when you uninstall a mod that it will delete the backup. NMM prompts you with "These mods will be uninstalled and all their files and their ARCHIVES will be permanently deleted from your hard drive are you sure? this operation cannot be undone." That gives a person the opportunity to manually remove the mode themselves, before deleting, or just deleting. NMM knows what they doing. Hmmm i thought it could not be done. Yet NMM does it, but Vortex, awww poor vortex, is left behind. why you may ask, because instead of saying I can they said we cant. Go Figure. LOL
  5. Not common sense. A tool manipulates an installation in the way it was instructed. And it offers the function to revert these manipulations. In no way it should delete any stuff already present which wasn't put there by the tool itself. Unless this would be the explicit function of the tool in question and the user explicitly requested that operation. Any tool which would not follow these rules would be thrown off my machine right away. Your request just remains unreasonable. Wow are you even paying attention. Do you know programming? No one is stating to delete anything. A simple line routine when the program checks to see if it made a back up of a mod if the user would like to restore or keep it as a back up. Are serious that you think programs cant do that. I mean a file called Freevideoedit asks the user if they would like to create a restore point before installing. COME ON. Vortex; Installing Reads the installation mod to install Checks if there is a mod with the same name If there is a file with the same name it asks the user do you want to replace or rename? You say replace Vortex creates a back of the file. Mod installed Vortex asks do you want to enable the mod. You enable Done Uninstalling Now you instruct Vortex to uninstall Vortex checks the file folder and ensures nothing has changed before uninstalling It prompts you with do you want to remove the mod and its archive? You say to remove both. Vortex goes into the folder and removes the mod and archive VORTEX created Vortex now goes and renames and reinstall the same mod. So why cant it ask the user before renaming the old mod and placing it back, if we want to reinstall, keep or delete a backup of the same mod? It knows there was one when it first installed and asked if you would like to replace it so....... SO SIMPLE. But i guess that is too sophisticated for the programmers. It is what it is. Just know That those that say something cannot be done are left behind those that say it can be done. You are like the people that said we cannot have planes or go to space. Take off the blinders.
  6. The computer is not being asked to think as a human. If the program backs up a program, then when you uninstall the program right before reinstalling a backup IT has a prompt stating a back up of this file was made would you like to reinstall? Simple. Vortex backs up hello.esm The user uninstalls Vortex knows it made a back up because it puts it back. SO why not add a subroutine that it will ask the user if they would like to put back the program IT backed up. If not Vortex moves it to the Vortex backup folder. SIMPLE. Common sense.
  7. First the computer would not create the same file in one particular folder, so deleting everything with the same name not possible. Also the program is REINSTALLING a BACK UP it made and not deleting, so it should ASK the user would you like to REINSTALL the back up of a program the USER said To UNINSTALL/DELETE like other sophisticated programs do. So please use logic and some common sense. SCENARIO I manually install hello.esm Then I install vortex and say I want vortex to handle my mods so I add Hello.esm to Vortex to install. Vortex prompts you if you would like to Replace the mod installed and you select yes or at times Vortex will just install it and later tell you a change was made. Toss up. Now to some replace means to get rid of the old. Then you UNINSTALL Hello.esm because you don't want it anymore. Vortex uninstalls Hello.esm but puts back Hello.esm from the back pup WITHOUT informing you. So a program you instructed to uninstall was put back from a backup without informing you. Now hello.esm is still loaded. Now you go and install goodbye.esm and the mod states DO NOT USE WITH HELLO.esm. You say to yourself I dont have HELLO.esm because VORTEX deleted it. You install and play Goodbye and the game crashes, or does not perform the way it should. Then you go to the forums and ask whats going on. The modder asks do you have Hello.esm installed? So how will you answer??????? COMMON SENSE.
  8. When you use Vortex to reinstall a mod, that you placed manually, Vortex will create a back up of that mod and when you go to uninstall Vortex will put that mod backup back into the data folder, so technically you never deleted the mod. This can cause mods to have issues with mods that dont work well together. Do you have plans to ask the user if they wish to reinstall the backup mod?
  9. a) No, that is not common sense, that is what you want in your current situation right now. Vortex is not there to uninstall the mods you have installed outside vortex. If you installed a mod through NMM you uninstall it through NMM. If you have installed a mod through Wrye Bash, you uninstall it through Wrye bash. If you have installed a mod manually then you uninstall it manually. That is common sense. b) You completely miss the point that Vortex doesn't know that the file it overwrote belong to the same mod, it just knows that they are the same files. They could belong to a completely different mod that happens to contain the same file and if Vortex didn't restore the backup that other mod, which you installed outside Vortex, would be broken. That's how Vortex generally works, if you install "moda" and then "modb" and they both contain "sometexture.dds", you resolve the file conflict via rule, let's say "modb after moda" and so the texture from modb is applied. But then if you disable modb it doesn't leave moda broken, missing a texture, Vortex will start deploying the texture from moda. The behaviour in regards to pre-existing files is the same: The assumption is that the files belong to a mod which would break if the files aren't restored. Vortex can not know that the files belong to the same mod you were installing and that you intended them to be replaced, it can't read your mind. Nope, it doesn't. You installed the mod manually, apparently, and then couldn't be arsed to check if a certain file exists that you manually put there? You made a bunch of assumptions about how Vortex works and never bothered to check them and instead wasted other peoples time on the forum? Don't make this our fault, it's not. Listen I am not going to go back and forth. THE FACT is if you have manually installed a mod and then decided to reinstall the same mod because issues with Vortex, Vortex will back up the old mod and install the new one. FACT when you uninstall that mod it will put back the old one. Thats the fact, and that can be an issue for a lot of people. I am sure if people checked there plugins with the mod list they will see a lot of mods that they thought was uninstalled still there. So if you tell a program to get rid of a mod, then get rid of it, dont put the old one back or at least warn us. The idea of get rid of means to get rid of. Common Sense. And it is VERY unprofessional the way you are reacting to users that are voicing their opinion on issues that can arise from using Vortex.
  10. I have to add this part for those that do not understand how having a backup mod reinstalled without you knowing it can cause issues. Scenario- If you uninstalled a mod and Vortex re-installs the same mod from a backup and than a month goes by and a person makes a similar mode which specifically states, do not use a mod that alters a certain mesh, you will say to yourself hey I don't have any installed, because i UNINSTALLED it, so you install the new mod. Come to find out the new mod causes unexpected behavior and you sit and wonder why is this happening, so you waste your time on forums asking the world what did you do wrong?, when it was Vortex that reinstalled a mod that you thought was uninstalled and is now causing issues with the other mods that said not use that mod. I hope it makes sense. I appreciate what Vortex has done so far, but as in any program there is always room for improvement and I think the example i just used is important. Especially when Modders tend to use the same area when making new mods, which can conflict with older mods. That is why it is important to know if a Mod, that you uninstalled, was reinstalled by Vortex from a backup. A simple prompt asking do you want to reinstalled the backup mod, Yes or no, is not too much to ask for, especially when you have sooo many mods that can conflict with each other.
  11. Hmmmmm. Lets start off with if you install a mod using vortex and Vortex sees that you have the SAME mod installed, then I would think it would be smart enough to know if you uninstall the mod that it would not return the old mod since you are uninstalling. Correct. I mean it is common sense. Now as for the crashing part, hmmm, if I uninstalled a mod and Vortex re-installs the same mod from a backup and than a month goes by and a person makes a similar mode which specifically states, do not use a mod that alters a certain mesh, you will say to yourself hey I don't have any installed, because i UNINSTALLED it so you install the new mod. Come to find out the new mod causes unexpected behavior and you sit and wonder why this is happening, so you waste your time on forums asking the world what did i do wrong?, when it was Vortex that reinstalled a mod that you thought was uninstalled and is causing issues with other mods that say do not use that mod. I hope it makes sense. It is just common sense.
  12. If you have manually installed mods in your game data directory, without Vortex, do not reinstall with Vortex without deleting your manual install. When you use Vortex to reinstall a mod, that you placed manually, Vortex will create a back up of that mod and when you go to uninstall Vortex will put that mod backup mod back into the data folder, so technically you never deleted the mod. This can cause mods to crash. MAKE SURE YOUR MOD LISTING MATCHES YOUR PLUGIN LIST. The Plugin list will show all the mods installed and the mod list will only show what Vortex is managing. Can be very misleading. Vortex should ask if you wish to restore a backup of the mod before restoring it.
  13. If you have manually installed mods in your game data directory, without Vortex, do not reinstall with Vortex without deleting your manual install. When you use Vortex to reinstall a mod, that you placed manually, Vortex will create a back up of that mod and when you go to uninstall Vortex will put that mod backup mod back into the data folder, so technically you never deleted the mod. This can cause mods to crash. MAKE SURE YOUR MOD LISTING MATCHES YOUR PLUGIN LIST. The Plugin list will show all the mods installed and the mod list will only show what Vortex is managing. Can be very misleading. Vortex should ask if you wish to restore a backup of the mod before restoring it.
×
×
  • Create New...