vrc-get/vrc-get-gui

ALCOM

A crossplatform fast open-source alternative of VRChat Creator Companion

Homepage

Installation

The recommended way to install ALCOM is download from Website.

Or you can install ALCOM from package managers like Homebrew, Scoop, AUR, or WinGet.

If you want, you may download the HEAD build from GitHub Actions

Supported Platforms

ALCOM runs on macOS, Windows, and Linux.

We support modern versions of the platforms. Basically, we support the versions that the platform vendor supports.

This support policy is to describe how my limited development resources use so it's welcome to pull requests that ports ALCOM to an older version of OSes. However, I won't maintain the backports so may break at any moment, I'll try to not break as possible though.

Here are detailed version support policies for each platform: Version numbers shown here are as of the writing (Dec 2024), so might be outdated.

• macOS: We support the latest version of macOS that is available for non-vintage and non-obsoleted Macs.
  This means currently we support macOS 13 (Ventura) or later. On macOS, we use WKWebView, which is built-in to macOS, so no additional requirements are needed.
• Windows: We support the latest version of Windows that is supported as mainstream by Microsoft.
  This means currently we support Windows 10 21H2 or later and Windows 11 23H2 or later. On windows, we use WebView2 so WebView2 should also be updated to supported versions. Currently, WebView2 with Edge 130 or later is supported.
• Linux: Linux is not well-supported, Linux support is best-effort by the community.
  No maintainer is using Linux as a primary platform, so we can't guarantee the quality of the Linux version.
  No specific version is guaranteed to work, but we will try to fix issues with your help.
  Basically, modern webkit2gtk 4.1 is required to run ALCOM since we use modern web features.

Requirements (building)

To build ALCOM, you need to have the following installed:

• Node.js >=20 supported — to build the web part of the project
• npm v10 — to install the dependencies of the web part (bundled with node.js so no extra attention needed in most case)
• cargo latest — to build the most part of the project
• And other requirements for tauri, see tauri requirements

Please note that ALCOM requires the latest version of rust toolchain at that time. We update the required version of cargo without notice. Therefore, It's recommended to update rust toolchain before building the project.

Building

To build the project, run the following command:

cargo xtask build-alcom --release

This command builds the main ALCOM executable for the current platform. For cross-compilation, add the --target command-line parameter. The executable will be created in the target/release directory.

There are a few build options available when building ALCOM. Most notably, you can disable the self-updater with the --no-self-updater option. Note that this does not disable update checks. ALCOM will show a message when a newer release is available instead of offering a self-update.

Directly distributing the executable may be suitable for some environments, but we also provide bundled distributions. To bundle ALCOM, run the following command after building it.

cargo xtask bundle-alcom --release --bundles <bundles>

Check --help for the list of supported bundle types.

Development

ALCOM is currently based on tauri and next.js.

Run npm run tauri dev to start the development server and gui.

Contribution

For how to contribute localization to ALCOM (vrc-get-gui): CONTRIBUTING.md (Please read ../CONTRIBUTING.md#configuration-requirements first before you read CONTRIBUTING.md!)

License

ALCOM is licensed under the MIT License. See LICENSE for more information.