2Based2Wait

Lightweight & (theoretically) extensible 2b2t proxy.

Wiki · Report Bug

Quick Start
Features
Images
Keep in Mind
For Developers

Quick Start

In config.json, configure the following values:
- account.username: Your Minecraft account playername.
- proxy.whitelist: Playernames of accounts that are allowed to connect to the proxy.
Run npm ci
Run npm start
Enter the auth code that appears in the console into microsoft.com/link
Connect to 127.0.0.1 in Minecraft
- If 127.0.0.1 doesn't work try 0.0.0.0

(See configuration guide to see how to enable features like Ngrok tunneling or Discord webhooks.)

Features

Extremely low RAM and CPU usage
Robust auto-reconnection
- Battle-tested to be online 24/7/365
High configurability
- Easily configure small-to-medium-sized networks
Convenient Discord webhooks for:
- Livechat
- Queue position
- Tunnels & connections
Toast notifications
Auto /queue main
Mineflayer support and extensibility (see: ./utils/mineflayer.js)
- Already comes with:
  - Kill aura
  - Auto eat
  - Anti afk
  - Anti drowning
Extensive logging
Share proxies with plug-and-play Ngrok tunnels
- Your machine's IP is never shared with players connecting to your proxy
- Your players' IPs are never shared with your machine

Images

No-Frills Cli Gui

Convenient Discord Webhooks

Extensive Logs

For Developers

If you have a local copy of 2based2wait with a personal config.json that's being tracked by git despite the .gitignore rule, run the following command:

git update-index --assume-unchanged config.json

Keep in Mind

2based2wait ships with as many options disabled by default as possible; including auto-reconnect, ngrok tunneling (for sharing accounts), coordination (for multiple proxies), Discord webhooks, and much more.

If you want to utilize all the proxy's features you'll need to RTFM, especially the configuration guide.

2b2tplayer / 2based2wait