Advertisement
Guest User

Discord Information

a guest
Jan 12th, 2020
1,392
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.92 KB | None | 0 0
  1. **__Welcome to Bots Temple, A Discord Bot List__**
  2.  
  3. Welcome to Bots Temple, here you can find bots for your Discord server, or if you are a developer find resources, help and support in addition to promoting your bot on our page making it reach more people, and more of them know your project, but Before doing this we strongly recommend you read the rules.
  4.  
  5. **Resources**
  6.  
  7. Website: **https://botstemple.ml/**
  8. Official Invite: **https://discord.gg/RGaJJpb**
  9. Discord Api (Support Libraries): **https://discord.gg/discord-api**
  10.  
  11. Make your bot better for everyone: https://github.com/meew0/discord-bot-best-practices
  12.  
  13. Below we will present the most common things for which bots are rejected:
  14.  
  15. 1) Be a cloned bot.
  16. 2) Do not put a description in the bot submit.
  17. 3) Bot is offline for long periods of time
  18. 4) Bot does not respond to his prefix, nor to the `@mention` of his name.
  19. 5) Bot or the owner not in the official server.
  20.  
  21. **RULES** (From **https://discord.bots.gg/**)
  22.  
  23. Please read this if you plan to or have submitted a discord bot to this server.
  24.  
  25. Once a bot is submitted, it enters the bot approval queue. You'll be able to see your bot, but it will not be listed until it is verified.
  26. The verification process has a number of steps to it. Here are the most important parts that you, as a bot developer submitting a bot, need to care about.
  27.  
  28. The most important thing to keep in mind is that all of the bots are in a queue. We see your bot, and we will get to it. You will not get the Bot Developers role until your bot is verified. Do NOT message or ping moderators about verifying/inviting your bot. Doing so will likely get your bot deleted on the spot unless you have a very good reason to do so. The whole process could take anywhere from a few days to a few weeks. Nothing you do will speed it up.
  29.  
  30. All bots submitted to the list must be manually invited by a moderator. Once a bot is invited, we look for a few things:
  31. **Uptime** - We can't test your bot if it isn't running. If your bot is still in early development and has frequent downtime, or you don't have a host that can keep it online while you sleep, consider waiting before submitting your bot, as it will likely be denied if your bot is offline for long periods of time each day. This is the longest part of the approval process; bots are given a few days to build up a history of good uptime, and to weed out the bots that don't actually have any code behind them.
  32. **Originality** - We're not super picky about what your bot does, so long as it's your own creation. If your bot is an unmodified or barely modified clone of an existing bot (ex. Redbot, Rhinobot, Nadeko), it will be denied.
  33. **A good description** - Please put as much effort into your description on the website as possible. Something like "A friendly and useful bot!" is not helpful or informative. Leaving out the description entirely will likely result in your bot being denied.
  34. **Actually responds** - We can't test your bot if it doesn't respond to commands. If your bot doesn't respond to its listed prefix or by being mentioned, your bot will be denied. If you must change the prefix your bot uses, ensure that you keep your listing updated as well.
  35. You will get a message from @-BT- letting you know if your bot is approved or denied.
  36. If your bot didn't make it, the reason should be DM'd to you, and will be available in #bot-list-log as well.
  37. Do not message moderators about your bot being deleted if you have not searched for the reason first.
  38.  
  39. **Summary**:
  40. You should read the whole thing, but
  41. - Have a good and informative description
  42. - Make sure your bot actually works and is online
  43. - If your bot is removed check the reason first
  44. - Don't ask about verification
  45.  
  46. **Don't put your token on GitHub**
  47.  
  48. This is because Discord security detects when a token is made public, it is changed automatically, a message arrives in your mail, and this is strictly named in Discord **TOS** (**https://discordapp.com/terms**).
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement