DWShells:Eggdrop

Create and manage an Eggdrop bot

Create an instance, edit its own configuration and keep other bots running during changes.

Last verified: 6 October 2026, against the current customer panel and service rules. Your effective dashboard permissions and assigned values take precedence over examples.

← Documentation hub · Visual website guide

One bot, one configuration

Step	What it means
01 · Packages	Create or choose a named instance.
02 · File Manager	Edit that instance’s configuration and scripts.
03 · Restart + logs	Apply settings and verify the bot’s connection.

Before creating a bot

Before you continue: Eggdrop must be allowed by your plan, and you need a free assigned listener port plus available app and IRC connection capacity. Obtain permission to operate the bot on your chosen network and channel.

Create your first instance

1. Open Eggdrop in Packages. Select the correct shell and expand Create a new Eggdrop instance. Choose a unique instance name, such as mybot. It is separate from the IRC nickname.
2. Fill the bot settings. Enter the IRC nickname, owner handle, a separate owner password of at least 14 characters and its confirmation. The current owner-handle field allows up to nine characters.
3. Choose server and channels. Use a permitted IRC server and its server port; keep TLS enabled when the server supports the chosen TLS port. Channels are entered as names such as #DWShells #MyChannel. Join only channels where your bot is welcome.
4. Set up and start bot. The portal selects an available allocated listener port, excluding existing ZNC and bot reservations. Read the result, confirm the running state and open View logs.

Edit one bot safely

1. Choose the instance card. Use Edit configuration or Files and scripts on the bot you intend to change. Do not edit a similarly named bot by mistake.
2. Save a copy and edit. File Manager lets you choose Eggdrop · INSTANCE. Save a local copy before modifying eggdrop.conf or scripts. SFTP locations are under ~/apps/eggdrop/instances/.
3. Restart that instance. Save the text, then return to Packages and Restart the same bot to apply configuration changes. Other instances have their own controls.
4. Check the result. Inspect View logs and the bot’s presence on IRC. A running process alone does not prove that it joined the correct network or channel.

Learn from the installed reference

Full reference opens the configuration reference for that instance. Use it to understand settings rather than pasting an unrelated configuration with another account’s bind address, ports or owner credentials. The owner listener uses TLS; follow the displayed port and certificate fingerprint when connecting.

Fresh install and deletion

Stop the instance and copy anything you want to keep. Install fresh or Delete bot permanently removes that instance’s configuration, credentials, logs and scripts after the typed confirmation. Fresh install opens new setup. Other instances are preserved, but choosing the wrong name still destroys the selected bot.

Troubleshooting

What you see	What to do
Bot is stopped after setup	Read the action result and logs; check configuration syntax and permissions.
Bot runs but is not on IRC	Check server, TLS, nickname conflicts, network access and IPv6 on Free.
Cannot create another bot	Check allowed instance count, assigned port reservations and resource limits.
Changes have no effect	Save the correct instance’s file and restart that instance.

Instance name, nickname and owner handle

Name	Purpose
Instance name	Identifies the bot's directory and panel controls, for example mybot
IRC nickname	Name other IRC users see on the network
Owner handle	Eggdrop's owner identity; follow the current field limit

Changing one name does not necessarily change the other two.

Add a script carefully

1. Read the script's documentation and confirm that its commands and resource use fit your plan and network rules.
2. Copy the selected instance's configuration and scripts to your own computer.
3. Open Files and scripts for that instance, or use SFTP into its instance directory.
4. Upload the script and edit the configuration according to the installed reference and the script's documented loading instructions.
5. Save and restart that instance, then inspect View logs.

Do not source untrusted scripts or copy another user's passwords, bind addresses or allocated ports. A syntax error can prevent the bot from starting; retain a known-good configuration to restore.

Rules and support

This guide describes how to use the service; it does not replace Signup and Rules. Join #DWShells on irc.darkworld.chat using TLS port 6697 for help. Use the customer portal for your actual status and connection details. Never share credentials or recovery links.

Back to documentation