Did you ever want to create a copy of a guild? Now you can! There is no need to manually create roles, channels and permissions, which can take very long depending on the original guilds size. The script does everything for you. It backs up a guild into a single file and lets you create a new guild from it. You can share your file with others, too.
- Categories
- Text & Voice channels
- Roles (also managed ones)
- Role permissions for categories and text/voice channels (no user specific ones)
- Emojis (see Disclaimer)
- Bans
- Chat history
- Invites
- Webhooks
- Audit Logs
- Third party integrations (Twitch/Youtube)
- Node.js any version >= 8.0.0 should work
- discord.js The latest version not the stable release. (Explanation)
- This will automatically be downloaded. See Installation for more information.
- A Discord account with a bot user
- Discord Developer page link to create a bot
- A preferably empty guild which can be overwritten
Use this script at your own risk!
According to the recent statement of the discord team, any kind of user accounts including so called SelfBots are forbidden. The script still allows you to backup a guild with a user account and stop after, but i still don't recommend it. Therefore, if you use this on a user account, it will be at your own risk with the possibility of your account being banned from discord permanently! Please don't come to me and complain if you get banned using this on a user account.
If you provide a user account token the script will backup the original guild and save it to a file but then stop the execution with a warning. You then just replace the user token with a bot token and rerun the script. It will automatically load the backup file and do its job.
- Download the repository from github
- Unzip it
- Navigate into the extracted folder
- Edit the
settings.jsonand fill in all necessary data (see Settings for more information) - Open the console and run
npm install(on windows you can shift + right click inside the project folder folder and select 'open command prompt here') - Run
node copy.jsin the console to start the script
To get the id of a guild open your client settings -> Appearance and then enable developer mode. If you now right click on a guild you can select 'Copy ID'.
| Variable | Explanation |
|---|---|
| originalGuildId | The id of the guild you want to clone. Can be left blank if a guildData.json already exists. |
| newGuildId | The id of the new guild you want to clone to. |
| newGuildAdminRoleId | The id of a role with administrator permissions. The bot needs to have this role on the new guild! You can manually create a new role called 'guildcopy' and the script will automatically use it. If you do so, just leave this field empty. |
| copyEmojis | default: false - set to true to copy emojis (see also Common Behaviour) |
| copyBans | default: false - set to true to copy banned users The bot needs to have the BAN_MEMBERS permission on the original guild if you enable this! |
| debug | default: false - set to true for a more detailed general and error output e.g. when creating an issue |
| token | Your account token. The bot does not need any permissions on the original guild (only exception: copyBans=true). |
- New guild cleanup
- Emoji Creation/Deletion: This will take time, especially if there are lot of them. Expect a few rateLimits when 'debug' is on. If 'copyEmojis' is disabled, emojis on the new server won't be deleted or new ones added.
- Bans Creation/Deletion: see 'Emoji Creation/Deletion' above
- Channel Deletion: The client might still show deleted channels despite them already being deleted. To fix this, just restart your discord client. You can do this while the script is running.
- Region
- Some guilds have VIP regions which cannot be used by normal guilds. Therefore if you copy such a guild the region will be set to us-central.
This was developed when 11.2.1 was the latest version which wasn't able to provide all needed features (e.g. categories, permsissions) to clone a whole guild. A port/rewrite to 11.3.X (or any version <12.0) and then to 12.0 again would just be unnecessary busywork. I will probably switch to the stable release as soon as 12.0 is stable.
I try to check new commits for changes which might break something but if I miss one, feel free to remind me ;D
Most of the common issues are displayed in the console while running the script. If you encounter crashes or any other weird behaviour not listed here feel free to create an issue. The script creates logs in the 'logs' folder. Feel free to upload those to something like pastebin and add them to the created issue to help me find the problem.
Of course, just create an issue or a pull request.
This software is licensed under the terms of the GPLv3. For more details see LICENSE.