Rename the Library #62
Replies: 3 comments 3 replies
-
Beta Was this translation helpful? Give feedback.
-
|
Since there is large demand for it, and I haven't heard of many people actually using this library with abandoned closed-source selfbots: I'll rename the next version. I think selfcord.py sounds pretty good, however it kinda conflicts with the project name too much. EDIT: To clarify, I won't be renaming the project, only the import. EDIT 2: Welp, now I'm getting tons of emails to not rename it. I'm either going to have two versions or just keep it the way it is. |
Beta Was this translation helpful? Give feedback.
-
|
Some people want me to rename, some don't. Because of that, what I'm planning to do is create a new branch on this repo that has a different import name. That way, you'll be able to install it using EDIT: See this new branch. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
This seems very bold but there's reason to it. The current import, as it stands, is
import discord. This is identical to the import for discord.py because of the way it has been forked. This is understandable and makes sense to a degree, but makes it very difficult for someone looking to code both selfbots and regular bots. While it is possible to use a venv, then install the right one, it still poses issues: it's difficult to import both into one project (seems counterintuitive, but could be a scenario) and that it's unnecessarily unproductive to have to re-install discord.py each time.Therefore, would it not be best to rename the library? Existing code can still be kept, since the existing import would simply be changed to:
A suggestion for a new name I have is either
selfcordordiscord_selfOf course the new name won't matter too much.
Beta Was this translation helpful? Give feedback.
All reactions