On the recordRead 3 Oct 202622 facts
YvLink
On the record
- API documentation
- The project includes API documentation and links to an online API documentation site deployed by GitHub Actions.github.com · read 3 Oct 2026
- Authentication limits
- YvLink does not terminate Minecraft online-mode authentication or generate Velocity modern forwarding or BungeeCord player data, and its allowlist is only an early filter.github.com · read 3 Oct 2026
- Backend selection
- Backend selection supports sequential, random, round-robin, least-connections, and lowest-latency strategies, with automatic failover when a connection fails.github.com · read 3 Oct 2026
- Bedrock crossplay
- Bedrock crossplay can use an external Geyser Standalone process or YvLink-managed GeyserLite, with a real RakNet Pong check; managed GeyserLite is Linux-only.github.com · read 3 Oct 2026
- Compatibility limit
- YvLink does not terminate online-mode authentication or generate Velocity modern forwarding or BungeeCord player information.github.com · read 3 Oct 2026
- Deployment guidance
- The management listener defaults to 127.0.0.1:18080, and the README recommends exposing it through an HTTPS reverse proxy rather than binding it directly to a public address.github.com · read 3 Oct 2026
- Deployment platforms
- The maker lists downloadable builds for x86_64 Linux variants, ARM64 Linux, and 64-bit Windows; Linux is recommended for source builds and other Rust/Tokio platforms may build from source.github.com · read 3 Oct 2026
- Download platforms
- The README lists installable packages for 64-bit Windows and Linux builds for x86_64 and ARM64.github.com · read 3 Oct 2026
- Game compatibility
- After routing, YvLink transparently forwards Vanilla, Fabric, Forge, and NeoForge traffic and preserves Forge/NeoForge status extensions.github.com · read 3 Oct 2026
- Health and failover
- YvLink can try another backend after a connection failure and optionally check backend health using TCP or Minecraft Status probes.github.com · read 3 Oct 2026
- Health checks
- Optional health checks use TCP or the Minecraft Status protocol.github.com · read 3 Oct 2026
- Integrations
- The project documents integrations with Geyser Standalone, GeyserLite, optional ViaLite, Nginx, systemd, and Certbot.github.com · read 3 Oct 2026
- Intended users
- The documented features and deployment instructions describe YvLink as a self-hosted proxy for Minecraft server operators managing routes and backend pools.github.com · read 3 Oct 2026
- License
- YvLink is licensed under AGPL-3.0-only, which the maker says permits personal, corporate, and commercial use subject to the license's source-sharing requirements.github.com · read 3 Oct 2026
- Mod support
- After routing, it transparently forwards Vanilla, Fabric, Forge, and NeoForge traffic and preserves Forge and NeoForge status extensions.github.com · read 3 Oct 2026
- Product
- YvLink is a Rust and Tokio Minecraft Java TCP proxy that routes connections by hostname and transparently forwards later game and mod-loader traffic.github.com · read 3 Oct 2026
- Purpose
- YvLink is a Rust and Tokio Minecraft Java TCP proxy that routes connections by the hostname in the client handshake and relays later game and mod traffic.github.com · read 3 Oct 2026
- Routing
- One public port can serve multiple hostnames, with exact and wildcard matching, a fallback rule, and up to 128 backends per route.github.com · read 3 Oct 2026
