-
Notifications
You must be signed in to change notification settings - Fork 213
[WIP] v1.9 of discord.py-self #57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
I'm not sure what you mean. The behavior of the |
My stupidity, not to lose the habit ;( |
Been there, done that lol |
|
Would it be possible to reimplement the |
|
This is basically ready, and the "docs" are finally up. Unless major bugs are found, I will be pushing soon. |
|
Can't launch my bot with the latest commit in the dev branch |
|
Crap. Forgot to add it to the slots. Commit incoming. |
|
That's what happens when you forget to |
|
Is there a scheduled update date for v1.9? Thanks. |
|
It's basically done. This week I'm just going to do some bug-testing. If everything goes well it should be out by the weekend. I would appreciate people looking over the docs for mistakes and testing out the update. |
… preferred_region, remove guild_ready_timeout
Summary
Here's a (relatively) short, outdated, non-exhaustive list of the changes in this version:
LazyUsers (I'm betting this will make a lot of people happy)guild_createstreamingis_botattributesClient.fetch_guilds()Client.fetch_user()guild.members(WIP)on_*events (unfortunatelyon_member_joinis unfixable for the time being, as Discord just doesn't provide that information reliably)manage_guildspermission unfortunately 😭)Client.join_guild()&Invite.use())Note: This is not everything.
Documentation
Before this is released and pushed to PyPi, I'll update the website (which is kinda trash right now) with an exhaustive list of everything public that was added, removed, and changed.
I am not going to document internal changes (outside of updating docstrings) as that will take waaayyy too long.
Credits
Huge thanks to arandomnewaccount and Discord-S.C.U.M for helping me navigate the mess that is Discord's APIs.
Conclusion
This version of the project is almost finished. To keep the feature-creep back, I'm only going to do the following before release:
Some people have been asking about what will happen when 2.0 releases. I will rebase this project to that version, however, it won't be quick. v2.0 adds type-hints to the entire project, completely removes everything user-related, and changes a lot of things internally.
A lot of people have asked me to rename the project, because it conflicts with the original discord.py. I will not be doing this. I have chosen to keep the same package name in the name of backwards-compatibility. There is a scary amount of closed-source selfbots that cannot be easily edited to change
import discordtoimport packagename as discord. Python has a great feature called virtual environments that can help people wanting to use both libs.I also want to address one final issue
I see a lot of Python beginners using this project to create something that would work perfectly fine as a regular bot. I want to make it clear that you shouldn't break the Discord ToS for no reason (no matter how bad it is), and that working with a library such as this or the original discord.py for your first coding adventure is not a good idea. Get familiar with Python first, and then come back to the mess that is the Discord API. If you do come back, consider using a regular bot.
I don't want script-kiddies getting banned for being curious.
Been there, done that.The reason I created this fork was to fix/improve upon discord.py's support of selfbots, and keep it maintained when discord.py removes it. Even though selfbots are against Discord ToS, I believe people should have a choice; writing code isn't against ToS, but using this library, unfortunately, is.
For that reason, I cannot ever recommend anybody ever uses this, and I carry no responsibility for any crap you do.
In my opinion, Discord banning selfbots was an incredibly stupid idea. It hasn't stopped bad actors from using them, it has only affected regular people trying to enhance their chat experience on what is (or at least used to be) a wonderful platform, with a wonderful community, and caring staff.
They had good intentions, but the selfbot detection is easy to work around (and always will be). Raids, dm spam, and all the other cons of selfbots still occur. Raiders, spammers, and advertisers don't care if their alts get disabled, or even if their mains get banned; they'll just generate a few hundred more tokens and continue. Disabled accounts only affect the people that aren't raiding, spamming, or advertising; just having fun. The selfbot ban only stops people that actually use Discord for keeping in touch with friends and being a part of communities they love, and wanted to tinker, carry around some extra chatting features, and add functionality to their servers.
Selfbotting is very low-risk to people that will abuse it, and high-risk to people that want to mess around and create cool things on their account.
The solution is not banning selfbotting as a whole. It is acting against people who abuse the Discord API.
If you support this, please go vote here and tell Discord how you feel.
For all of you saying "just use a bot":
...amongst other things
~Dolfies