FAQ |
Contributing |
Releases
Viper is a launcher and updater for Northstar, and not much more than that.
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, Flatpak and Windows Setup/Installer can auto-update.
Windows: Viper Setup [x.y.z].exe
(auto-updates, and is recommended), Viper [x.y.z].exe
(single executable, no fuss)
Linux: .AppImage
or Flatpak (auto-updates), AUR (unofficial), .deb
, .rpm
, .tar.gz
Currently Viper is capable of:
* Updating/Installing Northstar
* Launching Vanilla and or Northstar
* Manage Mods
* Auto-Update itself
* Be pretty!
There are of course many other things that it can do, but summed up very simply, that is what Viper is capable of doing. With every update Viper gets more features and alike, often many optional features are also available in the settings menu.
All settings take place in the settings page, found in the top right corner of the app, where you can change all kinds of settings. You can also manually go in and edit your config file (viper.json
), if you feel so inclined.
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.
To get support please open a GitHub issue, and clearly describe the problem with as many details as possible.
Many of the questions and problems you may have might be able to be answered by reading the FAQ page. So before opening an issue or asking for support please read through it first!
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 ones, otherwise we'll continue to have new ones.
Relevant xkcd:
Some of the existing launchers are listed below:
If you wanna edit Viper's code, 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 CPUs, 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.
Logo: Imply#9781
Viper Background: Uber Panzerhund
Titanfall+Northstar Logo: Aftonstjarma