The BackupBot is a bot developed for the Discord Hack Week and was developed using the Luvit environment, with the Lua programming language and the Discordia API.

Its invite link: https://discordapp.com/oauth2/authorize?client_id=592860951917756426&scope=bot&permissions=8
I have decided not to host it, since it easy-to-use and can get overloaded if thousands of people use it at the same time.

Productivity

The aim of the bot is to copy entirely a server, including roles and emojis.

It can be useful for multiple occasions, such as:

• Refreshing your oldie server;
• Duplicating the server for bot testing purposes; _{( Don't code on production ;) )}
• Storing the server structure for possible future damage;
• Why not backuping something important?

Behavior

The bot initially deletes all content from the duplicated server (channels, categories, emojis, ...) and asynchronally copies all emojis, roles, categories, channels and voice channels, permissions and other server settings.

It will keep you updated about the remaining seconds / processes through private messages.

Once the backup is done, you will receive the guild IDs and the log files.

The file LOG has a debugging log with all actions and errors _{(mostly about creating permissions for non-members)}.
The file TREE has a tree using the Lua table format [index] = "value" with the relation of original-server-id and cloned-server-id, so you know what became what.

How to start (Code)

A ready-to-use version of the bot can be downloaded here.

To start the bot, open your command prompt _{(in the folder of the bot)} and type the command luvit bot.

The file token must contain the bot token.

How to start (User)

The bot has a single and simple command, .BACKUP, that can be used in any channel of the server that you want to be cloned.

Even though it's not checked, it's fundamental for the bot to have administrator permissions in the original server, so it can reach every channel.
Nothing will be changed in the original server.

It's obligatory for the bot to have administrator permissions in the server that is going to be used as backup.
It's recommended that you set the bot role the highest one of the clone server, so it can manage all the roles.
This server is automatically detected by the bot and it relies on two conditions:

• Must have only 2 members;
  • One member must be the bot itself;
  • One member must be who typed the command .BACKUP.
• Both members must have administrator permissions.

Once it's matched, the bot will start to work.

See images here.

Good luck everybody!