beebophuckleberry Posted June 24, 2023 Share Posted June 24, 2023 (edited) On more than one occasion I've accidently clicked purge mods. Purge mods is directly adjacent to deploy. Also, deploy and purge have icons that resemble each other. Please change this. Or, create a extension that allows us to add confirmation, relocate, or hide the purge button. Edited June 24, 2023 by beebophuckleberry Link to comment Share on other sites More sharing options...
vortexposer Posted June 25, 2023 Share Posted June 25, 2023 (edited) By default there is a confirmation window to cancel purge, unless the never show again box is selected. Edited June 25, 2023 by vortexposer Link to comment Share on other sites More sharing options...
beebophuckleberry Posted June 25, 2023 Author Share Posted June 25, 2023 Great suggestion. I didn't consider the suppressed messages. I did check. No messages are being suppressed. Link to comment Share on other sites More sharing options...
vortexposer Posted June 25, 2023 Share Posted June 25, 2023 (edited) It only shows on new installs and once it is selected, it doesn't come back afaik. Allowing to reset that prompt would be something to suggest on the Nexus feedback forum though as lots of users seem to forget they've selected this option. Edited June 25, 2023 by vortexposer Link to comment Share on other sites More sharing options...
Pickysaurus Posted June 25, 2023 Share Posted June 25, 2023 What's the logic in this? Purge is a harmless operation and it just unlinks all deployed mod files. If you accidentally purge, just deploy to fix it. Link to comment Share on other sites More sharing options...
vortexposer Posted June 25, 2023 Share Posted June 25, 2023 (edited) Boggles my mind as well but I think a potential solution for some of these complaints is users simply shouldn't hide prompt to cancel purge option when initially setting up Vortex. Edited June 25, 2023 by vortexposer Link to comment Share on other sites More sharing options...
Guest deleted34304850 Posted June 25, 2023 Share Posted June 25, 2023 this is funny. Link to comment Share on other sites More sharing options...
vortexposer Posted June 25, 2023 Share Posted June 25, 2023 (edited) ikr. I learned to embrace the purge and now its a critical part of my workflow. First time set up prompt with selection box to bypass is fine though, once understood and accepted as just another every day part of the process. Edited June 25, 2023 by vortexposer Link to comment Share on other sites More sharing options...
showler Posted June 25, 2023 Share Posted June 25, 2023 I'd think the only problem here is that if you choose to hide the cancellation message for purging and it DOES NOT show in the "suppressed notifications" count and cannot be reset then that is wrong. Anything that you suppress should be able to be reset. Link to comment Share on other sites More sharing options...
beebophuckleberry Posted June 25, 2023 Author Share Posted June 25, 2023 lol, it's funny reading all your unhelpful responses. You came here to criticise and offered nothing in return. All I can do is sigh and remember that our species is full people like you. I shouldn't have to explain a idea that Vortex already thinks is a good idea. For example; Vortex already shows you which messages are suppressed and allows you to reset those preferences. So, obviously, the Vortex team thinks this is a good idea because they have already implemented the feature; however, somebody didn't apply this feature to the purging notification. One of you said purging is harmless. Incorrect. Vortex is not perfect (which is obvious from all the updates and bugfixes, right?). Purging is not perfect. In rare cases links can be left behind and cause issues. This risk increases depending on what Vortex settings you have selected such as the deployment method option. You ever had a link left behind and then had to hunt down the mod? I did. Had to reinstall over 2000 mods. All of which happened because the purge button got pressed instead of deploy. Could have been avoided if the suppressed notification was still available. Purging is harmless you say? I disagree. I think it's mostly harmless, but has the potential to screw things up in a bad way if links get left behind. Also, purging takes time. If you accidently purge then you also have to deploy again. This takes my build almost 3 minutes to do. Sit down and watch the clock for 3 minutes. It's a long time to wait for a button you didn't even intend to press. And, it's a button that could potentially provide a confirmation warning; however that notification was suppressed at one point and now can not be unsuppressed. One more thing, if purging is no big deal as you all say then why even have a confirmation in the first place? Hmmm? I'll tell you. They put the confirmation there as a courtesy notification so you don't do something you're don't intended to do. So, it's a big enough deal for your devs to implement a warning in the first place. Right? Anyways, having a confirmation before purging will not only save time but reduce risk of errors. Showler is the only person to reply with a decent response. Thanks Showler. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now