eggdrop@kire:~$ uptime since 1997 • ddos: armed • vhosts: loaded • userfile: ours

$./how

Not a timeline. The actual order of operations.

You fill in nick, network, channels. We do the rest. After it is in the channel, you talk to it like any other Eggdrop.

  1. 01
    Order. Pick a billing term. Tell us the bot nick, the IRC network, and the channels it should join. That form is not a prison — you can change all of it later.
  2. 02
    We build it. Install, config, ident, vhost, the process that actually stays up. Typically the same business day, often a few hours.
  3. 03
    You get mail. How to introduce yourself to the bot: DCC, telnet, the owner handle. Read it once. It is shorter than an Eggdrop README.
  4. 04
    The bot joins your channel. That is the “it is live” signal. If it is not there yet, it is not live. Do not open a ticket five minutes after paying.
  5. 05
    You run it. Add users, auto-op, banlists, extra channels, TCL you actually want. We do not babysit the partyline. We babysit the box.

$./control

you

Channel, users, scripts

Nick, channels, who gets ops, what TCL is loaded, the vhost it wears. DCC chat or telnet into the bot. Same controls a self-hosted Eggdrop has. You just skipped the compiler.

us

Machine, uptime, floods

The process, the disk, the DDoS filter, the “why did it vanish” ticket. If you wanted to SSH in and edit eggdrop.conf by hand, that is a shell, not this.

Order FAQ