Skip to content

Latest commit

 

History

History
84 lines (61 loc) · 2.75 KB

readme.md

File metadata and controls

84 lines (61 loc) · 2.75 KB
Raw

Requirements

Installation

  • first install dependencies npm install

  • run the bot once (node index.js) and the bot will create all files

  • edit config.json:

{
  "token": "get your token at https://discord.com/developers/applications",
  "logs": {
    "crash": "crash{y}.{m}.{d}-{h}_{i}.{s}.log"
  },
  "statuses": [
    "If i am not working, ping me for info",
    "{guilds} servers | /help",
    "Managing {manageGuilds} servers | /help",
    "Listening to {manageUsers} bots | /help",
    "Average downtime: {avgDowntimePRETTY} | /help",
    "Average uptime: {avgUptimePRETTY} | /help",
    "Made by mrballou#9055 and contributors | /help"
  ]
}

  • make sure that is on image

  • now you can start the bot with node index.js

TOS

(I mainly need this because of discord)

Privacy Policy

  • I collect/store data about the guilds (guild ID) and ADDED users.

This includes:

  • Guild ID (to assign the rest of the data).
  • Broadcast channel ID (to be able to know what channel to send the pings to).
  • Pings
    • user ID to ping
      • user ID to send pings about
  • Bot data:
    • user ID (to know for what user to send notification)
    • timestamps (to be able to know for how long the bot has being online / offline):
      • gone online (milliseconds)
      • gone offline (milliseconds)

For the purpose of being able to notify users that bots turned offline / online. You can see the data in the database.json file or via the data get command.

  • If you want to completely wipe the data from that guild, use the data delete command.
  • If the bot was kicked from the server and on the next boot the bot deletes all data from missing guilds / bots.

Additional information

  • public bots:

  • I do not make support on forks of this bot. Go to the repo bound to the bot you are using.

  • Profile picture by JBugel#0001

  • if you have the V1 version, and you want to migrate the db to v2 (this) you can use the following steps:

    • Rename the db to oldDb.json
    • and run node migrateDb.js
    • there should be a new file called newDb.json. That is the migrated db.
    • now rename that to database.json