Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/xhrvan/EvilBot
https://github.com/xhrvan/EvilBot
Last synced: 3 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/xhrvan/EvilBot
- Owner: xhrvan
- License: gpl-3.0
- Created: 2021-06-16T08:12:03.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2023-05-26T11:40:25.000Z (over 1 year ago)
- Last Synced: 2024-06-28T17:49:17.611Z (5 months ago)
- Language: Python
- Size: 1.52 MB
- Stars: 36
- Watchers: 1
- Forks: 370
- Open Issues: 18
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
😈EVIL BOT😈
## You can also tap the Deploy To Heroku button below to deploy straight to Heroku!
[![Deploy](https://www.herokucdn.com/deploy/button.svg)](https://heroku.com/deploy?template=https://github.com/shrvan42/EvilBot)
___________
## Starting the bot.
Once you've setup your database and your configuration (see below) is complete, simply run:
`python3 -m EvilBot`
### Configuration
There are two possible ways of configuring your bot: a config.py file, or ENV variables.
If you can't have a config.py file (EG on heroku), it is also possible to use environment variables.
The following env variables are supported:
___________
## Session String
* [![Run on Repl.it](https://replit.com/badge/github/TeamUltroid/Ultroid)](http://generatestringsession.sandeep1709.repl.run/)
## Variables
- `API HASH AND ID`: Your Api Hash And Id from [here](https://my.telegram.org).
- `ENV`: Setting this to ANYTHING will enable env variables
- `TOKEN`: Your bot token.
- `OWNER_ID`: An integer of consisting of your owner ID
- `OWNER_USERNAME`: Your username- `DATABASE_URL`: Your database URL
- `MESSAGE_DUMP`: optional: a chat where your replied saved messages are stored, to stop people deleting their old
- `LOAD`: Space separated list of modules you would like to load
- `NO_LOAD`: Space separated list of modules you would like NOT to load
- `WEBHOOK`: Setting this to ANYTHING will enable webhooks when in env mode
messages
- `URL`: The URL your webhook should connect to (only needed for webhook mode)- `SUDO_USERS`: A space separated list of user_ids which should be considered sudo users
- `SUPPORT_USERS`: A space separated list of user_ids which should be considered support users (can gban/ungban,
nothing else)
- `WHITELIST_USERS`: A space separated list of user_ids which should be considered whitelisted - they can't be banned.
- `DONATION_LINK`: Optional: link where you would like to receive donations.
- `CERT_PATH`: Path to your webhook certificate
- `PORT`: Port to use for your webhooks
- `DEL_CMDS`: Whether to delete commands from users which don't have rights to use that command
- `STRICT_GBAN`: Enforce gbans across new groups as well as old groups. When a gbanned user talks, he will be banned.
- `WORKERS`: Number of threads to use. 8 is the recommended (and default) amount, but your experience may vary.
__Note__ that going crazy with more threads wont necessarily speed up your bot, given the large amount of sql data
accesses, and the way python asynchronous calls work.
- `BAN_STICKER`: Which sticker to use when banning people.
- `ALLOW_EXCL`: Whether to allow using exclamation marks ! for commands as well as /.