DWShells
Customer Panel
← All guides

IRC apps / 6 min READ

Create and manage an Eggdrop bot

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

Reviewed 6 October 2026 · DarkWorld Network · Applies to the selected shell’s effective permissions

Detailed wiki guide ↗
One bot, one configuration Workflow illustration
  1. 01Packages

    Create or choose a named instance.

  2. 02File Manager

    Edit that instance’s configuration and scripts.

  3. 03Restart + logs

    Apply settings and verify the bot’s connection.

Before creating a bot

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 seeWhat to do
Bot is stopped after setupRead the action result and logs; check configuration syntax and permissions.
Bot runs but is not on IRCCheck server, TLS, nickname conflicts, network access and IPv6 on Free.
Cannot create another botCheck allowed instance count, assigned port reservations and resource limits.
Changes have no effectSave the correct instance’s file and restart that instance.

Read this topic in the wiki ↗ · Documentation hub ↗

Reference and help

Checked against the current customer-panel implementation and DWShells signup and rules. For assigned values and eligibility, use your dashboard. Need help? Join #DWShells on DarkWorld IRC or contact staff. Do not send credentials.

CONTINUE LEARNINGKeep your Free shell renewed →