VanillaCord downloads and patches a vanilla Minecraft server, so proxies can connect to it with your choice of BungeeCord, BungeeGuard, or Velocity IP forwarding enabled.
java -jar VanillaCord.jar <versions...>
For Minecraft 1.7, 1.8, 1.9, 1.10, 1.11, 1.12, 1.13, 1.14, 1.15, 1.16, 1.17, 1.18, 1.19, 1.20, 1.21, snapshots, and pre-releases
https://dev.me1312.net/jenkins/job/VanillaCord
Fork note: original work by the ME1312 team; this fork only adjusts the build/publish flow to use GitHub-hosted services and packages.
- Requires Java 21+ (Bridge artifacts target Java 21).
- Bridge artifacts are pulled from GitHub Packages at
https://maven.pkg.github.com/<owner>/Bridge. BRIDGE_OWNERcontrols which GitHub owner to pull from (defaults to the repository owner in CI, ormark-e-deyounglocally).BRIDGE_VERSIONpins a specific Bridge build. GitHub builds publish run-numbered versions (e.g.,0.1.0-SNAPSHOT.123); leaveBRIDGE_VERSIONunset/LATESTto auto-resolve the latest published version from GitHub Packages or pin it explicitly for reproducible builds.- Example:
BRIDGE_OWNER=ME1312 BRIDGE_VERSION=$(./scripts/resolve-bridge-version.sh) mvn -B verify - Compatibility probe: provide a release or snapshot server jar to sanity-check patch targets —
mvn -B verify -Dminecraft.serverJar=/path/to/server-<version>.jar
- You need a PAT with
read:packagesfor the owner hosting Bridge (andwrite:packagesif you publish a new Bridge build). - Keep auth in-repo to avoid host config issues:
export GH_CONFIG_DIR=$PWD/.gh && printf "%s\n" "$PAT" | gh auth login --with-token - When building locally, set
GITHUB_TOKEN=$PATso Maven (andscripts/resolve-bridge-version.sh) can read fromhttps://maven.pkg.github.com/${BRIDGE_OWNER}/Bridge.
- The workflow uses
BRIDGE_PACKAGES_TOKEN(PAT withread:packagesandrepoif Bridge is private) andBRIDGE_PACKAGES_USERNAMEif provided; otherwise it falls back to the defaultGITHUB_TOKEN/actor. Add the secret in repo settings if builds need to read Bridge from another private repo.