In order to change the account number tag without Nitro, change the username to an username that has an identical numerical tag. For instance, if there are two users bill#8000 and jane#9888, then if bill#8000 changes the username to jane, the numerical tag 8000 will be randomly rolled again.

In order to run multiple Discord instances at the same time whilst logging into different accounts, create a shortcut from the Discord.exe binary and adjust the Target to include the –multi-instance switch:

C:\Users\...\AppData\Local\Discord\app-1.0.9013\Discord.exe --multi-instance

Discord does not benefit from a feature that would allow one to delete all message history from a chat, but this can be accomplished via Greasemonkey and Undiscord that essentially perform some looped automation where all messages are retrieved and then manually deleted as if the user were to delete the messages on their own by browsing the message history.

The procedure using these two tools is easy, it just requires installing Greasemonkey or similar, and then installing the Undiscord script. After that, browsing to a Discord server or chat will reveal a garbage can on the top upper right of the interface that, one clicked, will reveal an interface allowing the user to delete all past messages.

A private bot can be used to manage channels without making the bot publicly available to anyone that wants to add a bot to their server. The process can be roughly described as the following:

• go to https://discord.com/developers/applications
• create a new application with a name,
• go to the Bot tab on the left and create a new bot,
• click the Create Token or Refresh Token on the Bot page and copy the key somewhere safely (this token will be used by an application to log-in to the bot account that you are now creating so keep the key in mind),
• go to the Oauth2 tab on the left sidebar,
• in the OAuth2 URL Generator under Scopes tick the bot box,
• under Bot Permissions tick the required bot permissions
  • Note that Discord permissions are highly structured such that some of the permission will go as far as to determine whether a bot can even read the name of the server members or determine which users are muted. Depending on the application that will be used for the bot, the application might just fail silently if the bot does not have a given permission. For example, if the bot cannot read the guild (server) members, the node.js library will silently just return an empty array making it seem as if nobody is on the server! For starters and testing it is always recommended to use the Administrator role before attempting to narrow down the permissions to whatever the application that will be used will require.
• make the necessary settings for the application that will connect (in particular, pass the bot token so it can log-in)