zyu/lcg-pair
Watch
1
0
Fork
You've already forked lcg-pair
 0
Code Issues Pull requests Projects Releases 2 Wiki Activity Actions
No description
4 commits 1 branch 2 tags 25 KiB
  • TypeScript 100%
Find a file
Exact
Repository files (latest commit first)
Filename Latest commit message Latest commit date
heisenburgah 4c13c422eb
All checks were successful
release / release (push) Successful in 45s
Details
ci: build releases on forgejo actions instead of by hand 
asset names now match what the lcg dashboard links (lcg-pair-windows.exe,
-darwin-arm64, -darwin-x64, -linux); the old GHA matrix emitted -windows-x64.exe
and -linux-x64, which would have 404'd every download button.

uploads go to http://forgejo:3000 rather than git.fable.bz so the ~109MB windows
binary doesn't hit cloudflare's 100MB request-body cap.
2026-08-12 02:34:33 +02:00
.forgejo/workflows ci: build releases on forgejo actions instead of by hand 2026-08-12 02:34:33 +02:00
src point source + release links at git.fable.bz 2026-08-12 02:08:16 +02:00
.gitignore initial commit 2026-05-13 03:07:51 +08:00
bun.lock initial commit 2026-05-13 03:07:51 +08:00
LICENSE initial commit 2026-05-13 03:07:51 +08:00
package.json ci: build releases on forgejo actions instead of by hand 2026-08-12 02:34:33 +02:00
README.md ci: build releases on forgejo actions instead of by hand 2026-08-12 02:34:33 +02:00
tsconfig.json initial commit 2026-05-13 03:07:51 +08:00

README.md

lcg-pair

connects your steam to lcg so esc → pairing → enable in-game auto-adds the server to your dashboard. one-time setup.

it does NOT see your steam password. ever.

flow

  1. opens a chromium window in app mode pointing at a local page on 127.0.0.1
  2. that page pops out facepunch's rust+ login (companion-rust.facepunch.com)
  3. you sign in. during the openid step the popup's address bar shows steamcommunity.com — that's steam's own login page, not a fake
  4. facepunch hands back a rust+ auth token. it's the same token the official mobile rust+ companion app uses to fetch your server list — it can NOT touch your inventory, buy games, change your password, read DMs, etc
  5. tool registers a fake android device with google fcm + expo so we can receive pairing pushes for you
  6. uploads (rust+ auth token, fcm credentials) to lcg.heroinhound.cc/api/fcm/exchange with your one-time pair code

after that, every in-game pair press shows up on your dashboard in a few seconds.

download

releases page → pick the binary for your OS. SHA256SUMS.txt is in every release.

verify with sha256sum -c SHA256SUMS.txt (linux/mac) or Get-FileHash on windows.

run from source if you don't trust the binary

bun install
bun run dev <pair-code>

source is what compiles into the binary. nothing hidden.

LCG_BASE_URL env var overrides the lcg endpoint if you're testing against a local api.

prereqs

chromium-based browser installed (edge / brave / chrome / chromium). on windows edge is preinstalled so usually nothing to do.

build it yourself

bun install
bun run build:all

produces four binaries in dist/ — windows-x64, darwin-arm64, darwin-x64, linux-x64.

the published release assets run the same commands in CI: pushing a v* tag triggers .forgejo/workflows/release.yml, which builds all four on a clean runner from the frozen lockfile, generates SHA256SUMS.txt in the same run, and attaches everything to the release. nothing is uploaded by hand.