ViaVersion as a Service - standalone ViaVersion proxy
Go to file
2021-02-09 11:09:15 -03:00
.github/workflows Update gradle.yml 2020-10-31 07:35:45 -03:00
.well-known Create microsoft-identity-association.json 2021-01-31 13:19:47 -03:00
gradle/wrapper update gradle 2021-01-27 13:15:44 -03:00
src/main fixed ending dot, fix ctrl+d 2021-02-08 08:45:59 -03:00
.gitignore closes #5 closes #4, add log4j and terminal console 2020-10-30 12:00:16 -03:00
build.gradle.kts use old fastutil-lite 2021-02-03 20:56:41 -03:00
gradlew update gradle, use fetch 2021-01-19 14:36:45 -03:00
gradlew.bat update gradle, use fetch 2021-01-19 14:36:45 -03:00
index.html redirect page 2020-11-15 11:48:09 -03:00
LICENSE.md draft 2020-08-15 18:02:35 -03:00
README.md cors anywhere instance for viaaas 2021-02-09 11:09:15 -03:00

VIAaaS

VIAaaS - ViaVersion acetylsalicylic acid as a Service - Standalone ViaVersion proxy

How to use: server.example.com._p25565._v1_12_2._ofalse._uBACKUSERNAME.viaaas.example.com (similar to tor to web proxies)

Parts:

  • server.example.com: backend server address
  • _p: backend port
  • _v: backend version (protocol id https://wiki.vg/Protocol_version_numbers or name with underline instead of dots)
  • _o: true to force online mode in frontend, false to disable online mode in frontend. if not set, it will be based on backend online mode.
  • _u: username to use in backend connection
  • viaaas.example.com: hostname suffix (defined in config)

Default Minecraft: viaaas.localhost with port 25565

Default WS URL: wss://localhost:25543/ws

Download: https://github.com/ViaVersion/VIAaaS/actions (needs to be logged into GitHub)

Requires Java 11

How to start VIAaaS server:

  • java -jar VIAaaS-all.jar

Usage for offline mode:

  • Connect to mc.example.com._v1_8.viaaas.localhost

Usage for online mode:

  • You can use two accounts (avoids Bad Login error), the same account for front-end and back-end connections or use _ofalse (offline mode in frontend, not encrypted).
  • You should set up a CORS Proxy (something like https://www.npmjs.com/package/cors-anywhere, git clone https://github.com/Rob--W/cors-anywhere && cd cors-anywhere && npm install && node server.js) on the machine you are using the VIAaaS authenticator webpage. You can use my CORS Anywhere instance https://crp123-cors.herokuapp.com/ when using https://viaversion.github.io/VIAaaS/ but Mojang may look it as suspect.
  • Go to VIAaaS auth webpage (https://localhost:25543/), configure the CORS Proxy URL (something like http://localhost:8080/, note the ending slash) and listen to the username A that you're using to connect to the proxy.
  • Add the account B you'll use in _u parameter to browser auth page.
  • Connect to mc.example.com._v1_8._u(account B).viaaas.localhost (_u(account B) parameter can be removed if you are using the same account)
  • Approve the login in auth webpage
  • Minecraft client will give Bad Login after you approve the login in your browser if you are using the same account. You can use https://www.curseforge.com/minecraft/mc-mods/auth-me for reauthenticate the client.

WARNING

VIAaaS may trigger anti-cheats, due to block, item, movement and other differences between versions. USE AT OWN RISK

FAQ

VIAaaS is stuck when connecting with online mode: