Minecraft proxy/bot intended for use on 2b2t.org.
Unlike a traditional MC bot, you can login to it as a normal MC server and control the account.
The primary purpose is to have accounts always online in-game and securely shared by multiple people.
This project is also used to support the 2b2t.vc API and Discord Bot.
What is a proxy?
This proxy itself consists of two components:
1. A Minecraft Server ("Proxy Server")
2. A Minecraft Client ("Proxy Client")
Players use a Minecraft client to connect to the Proxy Server as you would a normal MC server.
The Proxy Client connects to a destination MC server (i.e. 2b2t.org).
The Player's packets to the Proxy Server get forwarded to the Proxy Client which
forwards them to the destination MC server.
Player MC Client -> Proxy Server -> Proxy Client -> MC Server
When no Player Client is connected the Proxy Client will act
as a bot: moving around, chatting, etc.
How does it work?
ZenithProxy does not use, depend on, or interact with the Minecraft client or server code.
This means much greater opportunities for optimizing memory usage and performance.
But this also means existing MC mods or plugins cannot be used and must be
reimplemented specifically for ZenithProxy.
ZenithProxy acts primarily at the network packet layer. It can read/modify/cancel/send
arbitrary packets in either direction at any time.
Using packet interception, the client's session and world state is cached and
sent to players when they connect.
The cached world state is also used to simulate player movements,
inventory actions, discord chat relay, and all features.
- High performance and efficiency on minimal hardware, <300MB RAM per java instance or <150MB on linux.
- Integrated ViaVersion
- Can connect to (almost) any MC server and players can connect with (almost) any MC client
- Secure Whitelist system - share MC accounts without sharing passwords
- Extensive Discord Bot integration for management and monitoring
- Chat relay
- Customizable pings, alerts, and notifications. e.g. Player in visual range alerts
- Command System - Discord, In-game, and Terminal
- 25+ commands and modules to configure every feature
- Spectator mode
- Multiple players can connect to the proxy and spectate the player
- Advanced AntiAFK with full player movement simulation
- Integrated ReplayMod Recording
- Modules including AutoEat, AutoDisconnect, AutoReconnect, AutoRespawn, AutoTotem, KillAura, Spammer, AutoReply
- Many, many, more features.
- Linux, Windows, or Mac computer. I recommend using a VPS (droplet) from DigitalOcean:
- Java 21+ (Not required for
linux
release channel on supported CPU)- The ZenithProxy launcher will install Java 21 automatically if not already installed
- Download the launcher zip for your system
- For other systems, download the Python version (Universal). Requires Python 3.10+
- Unzip the file.
- Double click or run the launcher executable in a terminal:
- Windows:
.\launch.exe
- Linux/Mac:
./launch
- (Terminal Only) Python Universal:
./launch.sh
(Linux/Mac) or.\launch.bat
(Windows)
- Windows:
How do I download a file from a Linux terminal?
- Use wget in the terminal
- Example:
wget https://github.com/rfresh2/ZenithProxy/releases/download/launcher-v3/ZenithProxy-launcher-linux-amd64.zip
Recommended unzip tools
- Windows: 7zip
- Linux: unzip
- Mac: The Unarchiver
Recommended Terminals
- Windows: Windows Terminal
- Mac: iterm2
- The launcher will ask for all configuration on first launch
- Or run the launcher with the
--setup
flag. e.g..\launch.exe --setup
- Or run the launcher with the
- Use the
connect
command to link an MC account and log in once ZenithProxy is launched - Command Prefixes:
- Discord:
.
(e.g..help
) - In-game:
/
OR!
-> (e.g./help
) - Terminal: N/A -> (e.g.
help
)
- Discord:
- Full Commands Documentation
See the Linux Guide
I highly recommend using a terminal multiplexer - a program that manages terminal sessions.
If you do not use one, ZenithProxy will be killed after you exit your SSH session.
- (Default)
java
- Supports all operating systems - (Recommended)
linux
- Linux native x86_64 executable. ~50% reduced memory usage and instant startup
- To use a domain name you need the following DNS records:
- Create a discord bot here: https://discord.com/developers/
- Enable
Message Content Intent
under the "Bot" tab. Example - Invite the discord bot to a server:
- In the "OAuth2" tab, generate an invite link with these permissions
- Open the invite link in a web browser and select the server to invite the bot to
- Now in your discord server:
- In the discord server settings, create a role for users to manage the bot
- Create a channel to manage the proxy in
- (Optional) create another channel for the chat relay
- At first launch, the launcher will ask you to configure the role/channel ID's (or you can use
discord
command after)- To get the ID's, you must enable Developer Mode in your discord user settings
- Right-click on the roles/channels you created and click "Copy ID"
Create a new folder for each instance with its own copy of the launcher files. Example
Instances must be independently run and configured. i.e. separate terminal sessions, discord bots, ports, config files, etc.
See the Linux Guide for help copying files, creating folders, etc.
2b2t limits accounts without priority queue based on:
- Accounts currently connected per IP address
- In-game session time, excluding time in queue.
Current limits are documented in a discord channel