# Asteroid Proxy

## G-List Injection&#x20;

#### 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:** When using Velocity, you must place both the Asteroid plugin AND AsteroidLibs on your proxy server. Additionally, configure your credentials in the proxy's Asteroid configuration file.

For other server types, you only need to install the AsteroidLibs on the main server. Here is a link to it: <https://builtbybit.com/resources/asteroidlibs-asteroid-dependency.35035/>

To enable this functionality, use the following configuration:

{% code overflow="wrap" %}

```yaml
# ######################################################
#                       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"
```

{% endcode %}

* `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.

{% content-ref url="/pages/oUrAluCn87nD403G1edU" %}
[RedisDB + Lettuce](/asteroid/setup/features/asteroid-proxy/redisdb-+-lettuce.md)
{% endcontent-ref %}

{% content-ref url="/pages/yLTyxoicrDaAagSmSl9Z" %}
[MySQL](/asteroid/setup/features/asteroid-proxy/mysql.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.spoof.dev/asteroid/setup/features/asteroid-proxy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
