Modern style	Classic style

Discord · Matrix · Wiki

⚠️ Please don't link to this repository

We understand you want to help people run An Anime Game on Linux. The issue is, the more people know of the tools involved in it, the higher the chances The Anime Game Company will notice them, and then fix the flaws that let us do the needful.

While sharing in your self-managed chat services and through private messaging is fine, we humbly ask that you refrain from publically sharing links to this repository, or to any of the tools involved.

Or share them and ruin it for the dozens of Linux players. It's up to you.

If you're going to share it anyway

Do what you must, but we would respectfully request that you try to label the game as "The Honkers Railway Game" instead of the actual name of the game, to avoid search engine parsing.

♥️ Useful links and thanks

• Original patch project without which this project wouldn't be possible. Link is omitted for "privacy" purposes
• macOS launcher which contains some additional compatibility components
• Wiki contains some basic FAQ, installation instructions and more
• Releases page where you can find latest available version
• Changelog with chronology of the project

⬇️ Download

Distribution	Format	Wiki	Source
Fedora	Flatpak	link	-
Arch Linux, Manjaro	AUR	link	the-honkers-railway-launcher-bin
Fedora, OpenSUSE	RPM	link	HRL
Gentoo	ebuild	link	gentoo-ebuilds
NixOS	nixpkg	link	aagl-gtk-on-nix

To see the installation guides, please visit the wiki page here

Lutris integration described here

Chinese version support

This should be automatically enabled if you're using zh_cn (Chinese) as your system language. If you're not using it - you can change the game edition in the launcher settings

💻 Development

Folder	Description
src	Rust source code
assets	App assets folder
assets/locales	App localizations
target/release	Release build of the app

Clone repo

git clone --recursive https://github.com/an-anime-team/the-honkers-railway-launcher

Run app

cargo run

Build app

cargo build --release

Updates strategy

Starting from 3.2.1 (fcab428) we have 2 branches: stable (main) and dev (next). Code changes will be pushed into dev branch and merged into stable once they're ready for new version release