aboutsummaryrefslogtreecommitdiff



Overview | Releases



What is Viper?

Viper is a launcher and updater for Northstar, and not much more than that.

Install

Downloads are available on the releases page.

Please note that some versions will update themselves automatically when a new release is available (just like Origin or Steam) and some will NOT, so choose it accordingly. Only the AppImage and Windows Setup/Installer can auto-update.

Windows: Viper Setup [x.y.z].exe (auto-updates, and is recommanded), Viper [x.y.z].exe (single executable, no fuss)

Linux: .AppImage (auto-updates), .deb, .rpm, .snap, .tar.gz

What can it do specifically?

Currently Viper is capable of: * Updating/Installing Northstar * Launching Vanilla and or Northstar * Manage Mods * Auto-Update itself * Be pretty! Besides this I've been considering adding some easy to use VPK modding tools so everybody can have fun with VPK modding even if you don't know how to do it the traditional way. However that is not at the top of the todo list right now.

Configuration

Almost all configuration takes place inside the UI, and almost no configuration isn't either handled their or automatically handled, the only option that isn't configured in the GUI is disabling auto-updates, by default updates are handled automatically, when you launch the application it'll update, ask you if you want to restart, if not it'll continue with the old version until you restart, however you can disable this entirely by settings "autoupdates": true to false in your viper.json

Your configuration file will be found in %APPDATA%\viper.json on Windows, and inside either ~/.config or through your environment variables ($XDG_CONFIG_HOME) on Linux, the latter has priority.

Contact/Support

To get supoport either open a GitHub issue.
Or if you must you can contact a developer through the methods below:

Ways to contact the main developer: 0neGal * Twitter: @0neGal * Reddit: /u/0neGal

Sidenote

Given that we already have so many Northstar updaters and launchers I urge people to instead of creating new launchers unless there's a very specific reason, just make a pull request on one of the existing, otherwise we'll continue to have new ones.

Relevant xkcd:

Some of the existing launchers are listed below: * Viper - A launcher with an easy to use GUI and CLI albeit missing some features * Ronin - a CLI only updater * laundmo's updater - another CLI only updater * Juicy's mod manager - an updater and manager for mods, most feature rich

Development

If you wanna edit Viper's code and run it and so on, you can simply do something along the lines of the below:

$ git clone https://github.com/0neGal/viper

$ cd viper

$ npm i

$ npm run start

This'll launch it with the Electron build installed by npm.

Additionally, if you're creating your own fork you easily publish builds and or make builds with either npm run publish or npm run build respectively, the prior requiring a $GH_TOKEN to be set, as it creates the release itself so it needs a token with access to your repo. So you'd do something along the lines of:

$ GH_TOKEN="<your very long, private and wonderful token>" npm run publish

Keep in mind building all Linux builds may take a while on some systems as packaging the tar.gz release can take a while on many CPU's, at least from my testing. All other builds should be done quickly. When using the publish command it also automatically uploads the needed files to deploy auto-updates, keep in mind you'd need to have the repository setting changed to your new fork's location, otherwise it'll fetch from the original.

Credits

Logo: Imply#9781
Viper Background: Uber Panzerhund
Titanfall+Northstar Logo: Aftonstjarma