Honeypot

The Honeypot feature allows you to convert the whole Server into a honeypot, which can be useful for testing and security purposes. This feature is experimental and may not be fully functional yet.

Events (Pings, Joins) are published via RabbitMQ . To consume these events, you will have to write your own consumer.

Configuration

To enable the Honeypot feature, you need to set the following environment variables:

HONEYPOT_RABBITMQ_ENABLED=true
HONEYPOT_NAME=<your_honeypot_name>

HONEYPOT_NAME is the name of your honeypot. It will be used to uniquely identify your honeypot.

To configure the RabbitMQ connection, you can set the following environment variables:

HONEYPOT_RABBITMQ_HOST
HONEYPOT_RABBITMQ_PASSWORD
HONEYPOT_RABBITMQ_USE_SSL
HONEYPOT_RABBITMQ_USERNAME
HONEYPOT_RABBITMQ_VIRTUAL_HOST
HONEYPOT_RABBITMQ_PORT

Consuming Events

Liveliness Event

The liveliness event is sent every 5 seconds to indicate that the honeypot is still running. You can consume this event to monitor the status of your honeypot.

Queue: mc.raw_honeypot_ping

Example message: <honeypot_name>;<mc_version>

Join Event

The join event is sent whenever a player joins the server. It contains information about the player, such as their name and UUID.

Queue: mc.raw_honeypot_join

Example message: <honeypot_name>;<ip>;<player_name>;<player_uuid>

Ping Event

The ping event is sent whenever a player pings the server. It contains the requesters IP address.

Queue: mc.raw_honeypot_request

Example message: <honeypot_name>;<ip>