| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Slightly better UX I guess?
|
|
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
|
|
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...
|
|
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.
|
|
|
|
#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
|
|
|
|
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
|
|
|
|
|
|
#81
|
|
|
|
This was due to me testing something, not actually supposed to be in
release builds...
|
|
Usually utils.js would default to simply unzipping whatever was uploaded
if it wasn't a folder, now we check if it has "zip" as the extension,
case insensitive. If not simply report back the file wasn't a mod.
As opposed to the obscure error you got before this.
|
|
Since apparently dragleave and dragenter don't quite work as intended we
have to resort to this obscure method which should work just fine on the
user's end.
|
|
If you closed the file selection window after clicking the "Install Mod"
button it would improperly try to install "nothing", and therefore never
re-enable the buttons, this is now fixed.
|
|
incomplete update process
|
|
|
|
I have no clue why this is only a Windows error, but it is, which is
also why it slipped through into the 1.2.0 release.
|
|
|
|
The failed to install toast now pops up when it actually should.
|
|
#69
|
|
The modpath variable is now refreshed when you change the game path.
Which stops the problem altogether.
|
|
|
|
It'll notify of incorrectly formatted mods, it'll also notify on errors
and on success.
|
|
There used to be an error where if you spawned two toasts simultaneously
they'll get the same ID, this fixes that by upping the ID by one if the
ID is already taken.
|
|
No functional toasts yet, just the code for them, I'll add the actual
toasts later...
|
|
It now only does it if there's currently no results in the browser, aka
an empty search or it has yet to be loaded once before. Loading it every
time would cause lag.
|
|
Before this commit, the Thunderstore request would be sent on
application startup, now instead, it only does it when someone actually
clicks the "Find Mods" button, which should intern decrease load on
Thunderstore's end. Not that it mattered in the grand scheme of things,
it was just sort of unneeded.
|
|
|
|
|
|
Also fixes section buttons not being able to be clicked.
|
|
We now directly check the manifest file info as well therefore in all
cases even if the folder name for the mod is completely obscure, we
should now finally still get an installed status, both on removal and
install.
|
