Asteroid Proxy

G-List Injection

General Settings

If you are using BungeeCord/Velocity, you can now synchronize fake players across your network without requiring Redis. This new feature allows fake players to function both as server-specific entities and as ProxiedPlayer entities, ensuring they're counted in metrics like %bungee_total% and %online_players%.

IMPORTANT: You need to put Asteroid & AsteroidLibs on the proxy (only put libs on proxy if you use Velocity), and put the credentials in there as well.

To enable this functionality, use the following configuration:

# ######################################################
#                       PROXY                          #
# ######################################################
proxy:
  # Master switch for proxy functionality
  enabled: true

  # The name of this server as registered in the proxy network
  # This should match the server name in your proxy's configuration
  server_name: 'dev2' # (formerly known as local_name)

  # Data storage method for cross-server communication
  # Available options: Redis, Lettuce, MySQL
  # Note: If using MySQL, ensure correct database details are provided in the "database" section
  storage: "redis"

  # Redis connection settings (RECOMMENDED)
  # Only relevant if storage matches set to "redis" or "lettuce"
  redis:
    # Redis connection URI
    # Format: redis://[:password@]host[:port][/database]
    uri: "redis://:password@host:port/0"

• enabled: Set to true to enable proxy functionality

• server_name: This MUST match exactly the server name as configured in your proxy (formerly called local_name)

• storage: Database type for synchronizing fake players across the network. Options are: redis, lettuce, or mysql

• redis -> uri: Connection details for Redis in URI format

For the proxy synchronization to work properly, you must set up either a MySQL database or Redis. This allows the plugin to inject and track fake players across your entire network.

RedisDB + Lettuce

MySQL