AlwaysMOTD | Pterodactyl v2

Install and set up AlwaysMOTD for Pterodactyl v2: the extension, the agent on each node, the messages per server state and the settings.

AlwaysMOTD | Pterodactyl v2

Requirements

  • Pterodactyl Panel v2.0 or newer (the extension system).
  • Nodes running Linux with Wings and Docker, which every Wings node already has.
  • Root SSH access to the node, or a user that can use sudo without a password. The login is only used during the install and is not stored.
  • Four free ports on every node for the agent, by default 4001 to 4004.
  • The node can reach the Panel URL, which Wings needs anyway.

Installation

Step 1: Download the extension

Extract the product ZIP and keep both alwaysmotd-1.0.pteroext (the installable build) and alwaysmotd-source.zip (the editable source) if you want to customize the extension.

Step 2: Install in the Panel

  1. Sign in to your Panel as an administrator.
  2. Go to Admin → Extensions.
  3. Click Install and upload the .pteroext file.
  4. Toggle the extension on to enable it, then reload the page.

Step 3: Install the agent on your nodes

  1. Open Admin → AlwaysMOTD. Every node is listed.
  2. Click Install on a node and enter its SSH host, port, user and password or private key.
  3. The Panel checks that the machine runs the Wings of that node, starts the agent in Docker and shows Online after about a minute.

Prefer not to give the Panel SSH access? Run the command shown on the AlwaysMOTD page on the node as root instead:

curl -fsSL https://panel.example.com/alwaysmotd-agent/install.sh | sudo sh

The agent signs in to the Panel with the existing Wings credentials of the node, so no API keys are needed.

Setting up the messages

  1. Open the Messages tab and pick a state: Offline, Suspended, Installing or Starting.
  2. Write the MOTD and the kick message. Use § codes for colors and styles, for example §c red, §a green, §l bold and §r reset.
  3. The preview shows the server list entry and the kick screen as players will see them.
  4. Click Save changes. The agents pick up the change within 20 seconds.

The version text appears in red on the right of the server list when the protocol number differs from the version of the player. Set the protocol to 0 to show the player count instead.

Settings

Setting What it does
Show MOTDs Switches every agent on or off at once. When off, players reach the servers directly.
First port and last port Servers with an allocation in this range get a MOTD. Default 25500 to 25600.
Agent ports The agent answers on this port and the three after it. Default 4001 to 4004.
Check every How often the agent asks Wings for the state of its servers. Default 3 seconds.
Server icon The icon in the server list. Any PNG, JPG, GIF or WebP is scaled to 64 by 64 pixels.
Excluded eggs Servers using these eggs never get a MOTD, for example proxies or other games in the same port range.

Managing the extension

Action How
Update Install the newer .pteroext over the top. The agents update themselves within a minute.
Disable without removing Toggle the extension off. The agents remove their redirects and players reach the servers directly.
Remove the agent from a node Click Remove on the node, or run the remove command shown on the AlwaysMOTD page on the node.
Remove the extension Remove the agents first, then click Remove on the Extensions page.

Notes

  • The agent runs as the Docker container alwaysmotd and keeps its files in /opt/alwaysmotd.
  • While a server is not running, the agent sends new connections on its port to the MOTD of its state. As soon as the server is running, players reach it directly again.
  • Players that are already connected are never affected.
  • The agent removes all of its redirects when it stops, so stopping or removing it always leaves the node as it was.

Need Help?

Join our Discord Server and open a ticket for support.

© 2026 AlwaysMOTD, BuiltByOtte . All rights reserved.