You might know me from such things as My YouTube Channel, the discord.js guide I handed over to York, my Komada Framework, my Guardian bot or my Dithcord Library.

But now you can also enjoy the use of my personal selfbot! However, one caveat needs to be established:

USING SELFBOTS IS AGAINST THE DISCORD TERMS OF SERVICE. I AM NOT RESPONSIBLE AND CANNOT BE HELD LIABLE IF YOU LOSE PRIVILEGES, GET KICKED OR BANNED FROM ANY SERVER OR FROM DISCORD. So why does this still exist? Because we're all rebels and we like taking risks in order to get cool stuff.

Oh and also: This is my personal selfbot code, and though I put it online with this nice readme for you to install and use it, I can't cater to other people's requests or desires. I update this when I feel like it with the features I want and I make breaking changes without consideration for other people's installations.

• git command line (Windows|Linux|MacOS) installed
• node Version 8.4.0 or higher
• a machine to host it on. Want it to be online 24/7? Get a VPS. I suggest OVH (no there are no good free hosts).
• some goddamn sense If you don't intend to read the rest of this document, you shouldn't bother using this selfbot.
• some knowledge of node and javascript because I'm not there to handhold you.

In a command prompt in your projects folder (wherever that may be) run the following:

git clone https://github.com/eslachance/evie.selfbot.git

Once finished:

• Create a webhook in a channel where you want logs to appear (Channel Settings, Webhooks) and grab its ID and token.
• In the folder from where you ran the git command, run cd evie.selfbot and then run npm install
• Rename config.json.example to config.json
• Edit config.json and enter your token and other details as indicated. It should look like this afterwards:

{
  "botToken": "mfa.VkO_2G4Qv3T--NO--lWetW_tjND--TOKEN--QFTm6YGtzq9PH--4U--tG0",
  "webhook": {
    "id": "123456789123456789",
    "token": "mfa.VkO_2G4Qv3T--NO--lWetW_tjND--TOKEN--QFTm6YGtzq9PH--4U--tG0"
  },
  "prefix": "/"
}

1. From either the web application, or the installed Discord app, use the CTRL+SHIFT+I keyboard shortcut.
2. This brings up the Developer Tools. Go to the Application tab
3. On the left, expand Local Storage, then click on the discordapp.com entry (it should be the only one).
4. Locate the entry called token, and copy it.

KEEP YOUR TOKEN SECRET, AND NEVER SHARE IT WITH ANYONE

To start the selfbot, in the command prompt, run the following command: node app.js

If at any point it says "cannot find module X" just run npm install X and try again.

For support join 〈evie.codes〉 and talk to me, 〈evie.codes〉!

Please see the wiki on github for details on adding your own commands, events, etc.

If relevant, updating to a new version here will indicate what you need to do.

This version updates to Enmap version 0.4.1. 0.4.x introduces providers which separate the persistence from the Map itself. To update to this version:

• Backup your ./data/ folder (just in case, I didn't have any issues)
• Shutdown the bot
• Do a git pull to get the updates (app.js and modules/PersistentDB.js are the 2 files)
• do npm i as the version of enmap changed, and enmap-level must be installed.
• Start the bot again.

Per my tests, there should be no change at all in data access. None of my tags, or quotes, or guide entries were lost. But, backup's always a good thing!

Eh why not bump a version, I feel like it.

I've changed the logging feature to use a webhook instead of a channel output. The reason for this is that it will actually notify the user if a mention is made, or if the bot encounters an error or reboots, etc. Basically any log you send.

The code is almost identical, except that you need to change the config.json to reflect it: a single channel is used, you just need to provide a webhook ID and Token to get started (see example config above).

I've also removed the "password" thing from the config and the code since I seem to not be using that anyway and it introduces a possible security breach if you upload your config by mistake (not that the token isn't the same but whatever).

Other changes include continuously updating the code to work on the latest version of discord.js version 12, small optimizations, and udpates that I can't be bothered to properly document.

There was a change in the way that the tags, quotes and guide commands work. These commands are now class-based (a nice exercise you can see me execute on twitch in a livestream). This required some tweak of the commands, but most notably the tags command now has a slightly different storage format. Yes. Again. Fear not, running the following eval command will most definitely make your tags continue to work with this new update!

/eval client.tags.forEach( (t,k) => {
  try { JSON.parse(t) } catch(e) { client.tags.set(k, {"contents" : t}) }
});

Remember that if you've made modifications of your local files, you might not have all the updated files using git pull. But, that's up to you to fix!

I have completely overhauled the tag and "slashes" system into one using my new djs-collection-persistent which is just pure bliss. To update to the new system, after running git pull you'll need to run the following "eval" codes:

/eval bot.db.all("SELECT * FROM shortcuts").then(rows => rows.forEach(r=>bot.tags.set(r.name, r.contents)))

You also need to copy the tags:

/eval bot.db.all("SELECT * FROM tags").then(rows => {
  rows.forEach(r=> {
    if(bot.tags.has(r.name)) r.name = r.name + "1";
    bot.tags.set(r.name, r.contents)
  })
})

In the extremely rare circumstance where you might have already added stuff to the new quote system, run this eval:

/eval bot.db.all("SELECT * FROM quotes").then(rows => rows.forEach(r=>{
  bot.quotes.set(r.name, {channel: r.channel, message: r.message, author: r.author, embed : r.embed})
}))

That should be it. You'll now get the same result from /tag name and /name, but now you can do /lenny that was lewd and it'll actually, like, output the message. So, go wild!