aboutsummaryrefslogtreecommitdiff
path: root/src/index.js
diff options
context:
space:
mode:
author0neGal <mail@0negal.com>2022-02-23 18:33:59 +0100
committer0neGal <mail@0negal.com>2022-02-23 18:44:27 +0100
commit5193485b5c66170330b920d891e3fe1442cc1f3d (patch)
treef1a64a3fccc64774d527165fc5d6c68d4cf5d4f6 /src/index.js
parent70309583c81622ff5f5d41e2a9b85df287792326 (diff)
downloadViper-5193485b5c66170330b920d891e3fe1442cc1f3d.tar.gz
Viper-5193485b5c66170330b920d891e3fe1442cc1f3d.zip
implement ability to disable NS auto-updates
Albeit with some caveats, due to the way electron-updater is setup, if you're not on a version of Viper which supports auto-updates the event which runs the NS Updater code will never be run, and hence it'll never auto-update. This was also an issue before, but I only noticed it now.
Diffstat (limited to 'src/index.js')
-rw-r--r--src/index.js8
1 files changed, 7 insertions, 1 deletions
diff --git a/src/index.js b/src/index.js
index fa2a35f..0e8364f 100644
--- a/src/index.js
+++ b/src/index.js
@@ -59,7 +59,13 @@ function start() {
win.webContents.send("mods", utils.mods.list());
});
- if (utils.settings.autoupdate) {utils.updatevp(false)}
+ if (utils.settings.autoupdate) {
+ utils.updatevp(false)
+ } else {
+ if (utils.settings.nsupdate) {
+ utils.update();
+ }
+ }
autoUpdater.on("update-downloaded", () => {
win.webContents.send("updateavailable")