lug-helper: a shell script that installs Star Citizen on Linux through Wine

A community installer for a game without Linux support

lug-helper is the official installer of the Star Citizen Linux Users Group, and the repository points at the group's page on the publisher's site and at a community wiki. The project describes itself as helping you install and manage Star Citizen on Linux, maintained by the group org and the community, and it makes a point of saying it is human-made, not AI-generated.

That framing matters for what a reader should expect. This is a volunteer effort to run a game that the publisher does not ship with Linux support, so the workarounds are the substance of the project rather than a side effect. Star Citizen runs under Wine, and the launch path involves a Wine prefix, a launcher, a graphics translation layer, and two operating system limits that the game needs.

The primary language is shell, the licence is GPL-3.0, the default branch is main, and the release history shows steady work. Version 4.15 is dated 2026-07-30, 4.16 on 2026-08-03, and 4.17 on 2026-10-14, which is also the date of the last push. The last two releases being close together and the third further back suggests maintenance releases rather than a feature burst.

The tree is small and reflects that it is one script. There is lug-helper.sh at the top level, a lib/ directory holding the function library, a LICENSE, the README, and three images used by the interface and the wiki.

Three ways to get it, and what each one asks of you

The installation section offers distro packages, a source archive and an AppImage, and the packages are community maintained rather than built by the project.

For Arch Linux there is an AUR package, for Fedora a COPR build, and for NixOS there is a separate nix-citizen project. The README is explicit that these packages are maintained by the community, which is a distinction worth carrying with you: if something breaks in a distro build, the bug may belong to the packager rather than to the script.

From source you download and extract the .tar.gz archive from the releases page, then either right click lug-helper.sh in your file manager and choose Run as a Program, or open a terminal, change into the extracted directory with cd /path/to/extracted/lug-helper, and run it with:

./lug-helper.sh

The AppImage route is three steps: download the .AppImage, give it executable permissions in your file manager, and double click to launch it.

The dependency list is short and mostly already present. The required ones are bash, coreutils, findutils, curl and polkit, with the note that these should be installed by default on most distributions. Winetricks brings in cabextract and unzip, and zenity is optional, for the graphical interface.

Zenity menus with a terminal fallback, and a saved config

The interface design is the thing that makes a shell installer usable by people who do not want a terminal. Zenity menus are used for a graphical experience, with a fallback to terminal-based menus where Zenity is unavailable, and command line arguments are available for quickly launching functions from the terminal, listed under ./lug-helper.sh --help.

So the script degrades rather than breaks. A system with zenity installed gets dialogs, and a minimal system gets a text menu that works the same way. That is the right trade for a tool that has to run on dozens of distributions.

Configuration is saved in $XDG_CONFIG_HOME/starcitizen-lug, which follows the XDG base directory convention, so the script respects a user's existing configuration layout rather than writing into the home directory directly. There is also a menu entry to reset the helper configs, which deletes what the helper saved in that directory.

The function list under About and Support shows the extent of it, with entries for displaying information about the helper and links to the community. The wiki is where the quick start guide, troubleshooting steps, news, and guidance on input devices and head tracking setup live, and the README defers to it rather than duplicating that content.

The preflight check changes two kernel limits on your system

The first function in the list is the preflight check, which runs a series of system optimization checks and offers to fix any issues it finds. Two of those checks are worth knowing about in detail, because they are the ones that make the difference between the game starting and not starting.

The first checks that vm.max_map_count is set to at least 16777216. The explanation given is that this sets the maximum number of memory map areas a process can have, and while most applications need less than a thousand maps, Star Citizen requires access to more. The second checks that the hard open file descriptor limit is set to at least 524288, which limits the maximum number of open files on the system, and on some Linux distributions the default is set too low for Star Citizen.

These are the two adjustments every manual guide for running this game on Linux asks for, and having a script check and offer to fix them removes the most common first-run failure. The offer matters: the checks are presented as things the script can fix, with the option to accept.

The important caveat is that these are system-wide changes, and the hard file descriptor limit in particular is a global setting. A script that adjusts them on your machine is doing something that outlives the game, and the wording of the check is a technical one that you should read before accepting rather than a cosmetic setting.

Wine runners, DXVK and the launch script repair tools

The bulk of the menu is maintenance, and the structure of it tells you what actually breaks in practice.

There is a function to install the Star Citizen RSI Launcher using Wine, and a separate one to re-install the latest version of it. There is Manage Wine Runners, which quickly installs and deletes custom Wine runners, and Manage DXVK, which updates or switches to a different DXVK in the game's Wine prefix.

Then there is the group of repair tools, and these are the most telling part of the list. One lets you target a different Star Citizen installation, selecting a different Wine prefix for the helper to operate on. One updates or repairs the launch script, including broken paths, icons and .desktop files. One edits the launch script directly. One opens the Wine prefix configuration by running winecfg in the prefix, and another opens Wine's game controller configuration.

A game installed through Wine has a desktop entry, a launch script with absolute paths, and a prefix that can be rebuilt. All three break. Having a menu entry for each, plus the ability to point the helper at a different prefix, is what turns a one-time install script into a tool you keep.

The remaining entries cover the edges. Create joystick hidraw rules creates udev rules to enable joystick hidraw access, which is a controller-related workaround. Install PowerShell into Wine prefix uses winetricks to install PowerShell. List Helper and Star Citizen directories and files shows everything in use by both, and Show logs displays the Star Citizen and Easy Anti-Cheat log files for troubleshooting, which is the first thing you want when the game will not start.

Where lug-helper is the wrong tool

The first wrong case is a machine you do not want modified. The preflight check raises a kernel limit and the hard file descriptor limit, the script creates udev rules for joystick hidraw access, and the uninstall function is what cleans up the Wine prefix and the installed files, not the system settings. On a shared or work machine, that is a package of persistent changes to your system for one game.

The second is anyone who needs a supported platform. This is a community project making an unsupported configuration work, and the publisher's support channels do not cover it. That is not a criticism of the project, it is what the project says it is.

The third is a distribution whose packaging you cannot get. The AUR, COPR and NixOS routes are community maintained, and if none of them covers your distribution then you are on the source or AppImage path, which means you own the updates. There is no package repository for the project itself.

The fourth is automation. This is an interactive script with a menu. There is a --help and command line arguments for launching individual functions quickly, and the wiki has a page describing the code structure and a packager's guide for those who want to integrate it, but it is not a declarative configuration tool and it is not a CI-friendly installer for a fleet of machines.

The honest summary is that this is a well-maintained community answer to a problem the publisher has not solved, and if you are in that situation it is very likely the best option available.

Editorial conclusion

Adopt lug-helper if you play Star Citizen on Linux and want the Wine prefix, the launcher, DXVK and the required system limits set up and kept in repair for you, since the preflight check and the repair options cover the parts that break most often. Keep away if you expect vendor support, because this is a volunteer community project maintaining an unofficial path to a game without Linux support. Before you run it, read the preflight values, because the script raises vm.max_map_count to 16777216 and the open file descriptor limit to 524288 on your system, and note that configuration is written under $XDG_CONFIG_HOME/starcitizen-lug, with the 4.17 release dated 2026-10-14 and the last push the same day.

Frequently asked questions

Official sources

1. License: GPL-3.0
2. Project website
3. README
4. Releases
5. starcitizen-lug/lug-helper on GitHub