| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
Slightly better UX I guess?
|
|
Previously it didn't have the settings button, it now does!
|
|
For testing purposes I had the mod browser auto show on startup, that's
removed now, I also when refactoring some code forgot to change the name
of a function everywhere, leading to an error.
|
|
Fully implemented (I think? Maybe there's an edge case?), albeit it's
missing "Updateable" and "Installed" filters, but they'll be added later
|
|
|
|
Bumps [minimist](https://github.com/substack/minimist) from 1.2.5 to 1.2.6.
- [Release notes](https://github.com/substack/minimist/releases)
- [Commits](https://github.com/substack/minimist/compare/1.2.5...1.2.6)
---
updated-dependencies:
- dependency-name: minimist
dependency-type: indirect
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
|
Bumps [electron](https://github.com/electron/electron) from 16.0.5 to 16.0.6.
- [Release notes](https://github.com/electron/electron/releases)
- [Changelog](https://github.com/electron/electron/blob/main/docs/breaking-changes.md)
- [Commits](https://github.com/electron/electron/compare/v16.0.5...v16.0.6)
---
updated-dependencies:
- dependency-name: electron
dependency-type: direct:development
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
|
I forgot about this when merging the VDF fix
|
|
This overwrites viper.json and disables Viper updates, this is useful
when repackaging Viper for other formats we don't already support.
|
|
* added debug messages
* more debug logging
* even more debug logging
* removed debugging and fixed VDF problem maybe?
Apparently the libraryfolders.vdf doesn't always come with the same
values, sometimes it comes with the contentstatsid variable and other
times not, we assumed it always was there, and never checked for it,
this caused problems if it wasn't there. This should fix that...
|
|
This lead to you going through the whole build process but it never
actually uploaded all the files. Quite annoying!
|
|
If a mod has the name of an already existing element some issues may
arise... So now we have all mod elements prefixed with "mod-" and we
also only search for elements inside #browserEntries, that should avoid
all issues...
|
|
|
|
|
|
|
|
If the nsargs are edited by a third-party program or anything that isn't
Viper, the next time you launch Viper it'll reset the nsargs back to
what it was when you last opened it.
|
|
Some users got confused about the "Change Game Path" label on the
startup page, thinking it was Viper asking the user to change the path,
to clear up that confusion we now just don't show that page on startup.
|
|
|
|
|
|
Since all configuration now takes place in the UI, there's no need to
explain how to disable auto-updates through the config file.
|
|
feat: Settings page
|
|
[feat] french settings translations
|
|
|
|
feat: Settings page: add "es" localization
|
|
#85
|
|
I localized all strings for English, then went ahead and made array
options have a wider input and more word spacing, since they're all
space separated.
|
|
When #87 was merged an unnoticed problem slipped in where if Viper was
running in a version that did not support auto-updates we would never
auto-update Northstar. Now that's fixed, and the nsupdate option is
completely implemented.
I also took the liberty of removing the auto-update option in the
settings page if Viper can't auto-update anyway, as it's useless if
that's not possible.
|
|
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.
|
|
|
|
It actually saves settings, loads them properly and everything...
|
|
refactor: i18n
|
|
[fix] updates checking order
|
|
|
|
|
|
Albeit only frontend functionality, it doesn't actually save your
settings, it simply loads them, and Settings.get(), allows you to
convert them to a format that can be used to save settings.
|
|
I added descriptions and options for excluding files.
|
|
This only has the actual UI for the settings page in place, no actual
functionality has been implemented yet. I made several changes not
directly related to the settings page, such as changes the CSS color
variables to use RGB, as to easily add an alpha channel to colors. I
also changed the way the Browser is toggled in some respects and many
other changes that makes it easy to re-use the browser code to create
the settings UI
|
|
|
|
variable
|
|
|
|
|
|
build/langs.js now gives more info and has colors. It also changes it's
exit code if an error happened, we then use that in build/publish.sh to
catch localization errors before publishing. We also ensure that version
numbers are set correctly.
Then at last we will make sure $GH_TOKEN is set, and if not, prompt for
the token, to make sure you don't build everything then error out when
you forgot to put in your token.
|
|
|
|
feat: drag and drop to install mods
|
|
feat: Spanish "gui.mods.dragdrop" key
|
|
#81
|
