A multipurpose bot designed to make Discord better for everyone, written in Python.

Related tags

Third-party APIs WrappersHadum-Bot
Overview

Hadum

Hadum

CodeFactor Python license

A multipurpose bot that makes Discord better for everyone

Features

  • A Fully Functional Moderation component: manage your staff, members and permissions all in one bot.
  • Memes.
  • Support Chatbot (Coming Soon™)

Commands

Hadum Features a wide(-ish) set of commands to choose from.

Command Usage Description
ping h.ping Get Latency between bot and Discord Servers
coinflip h.coinflip Flip a coin!
kick h.kick [user] [reason] Kick a user from your guild
masskick h.masskick [users] Kicks multiple users at a time
ban h.ban [user] [reason] Permanently Bans a user
massban h.massban [users] Bans multiple users at a time
purge h.purge [number_of_messages] Delete messages in the current channel

Command Line Args

Hadum Features a few CLI args to choose from (more coming soon)

Name/Flag Description
-q Skip the 'Hadum' loading animation
-v Show error logs in console
-h Get help

To use them, enter

python main.py /[ARG_FLAG]  # Windows
python3 main.py -[ARG_FLAG] # Linux/Unix-like/Windows WSL

Hosting on your own machine

So, you edited the code to your own liking and now you want to host it on your own machine? No problem! There are 3 ways of installing the bot:

  1. (NOTE: This is now deprecated, use Docker instead.) For an automatic install, run bash scripts/install.sh (Linux/Unix or Windows WSL only) in the root directory of the project

  2. For a Docker Installation, run the following command (don't ignore comments!):

    docker run -it $(docker build --build-args token=BOT_TOKEN -q .)  # Replace 'BOT_TOKEN' with your token.

  3. Or by following the steps below for a manual installation of the bot:

    1. Clone the repository using
    git clone https://github.com/shadawcraw/Hadum.git
cd Hadum  # Accessing the project directory
    1. To install the dependencies, Run in the root folder of the project the following command:
    python -m pip  --no-cache-dir -r requirements.txt  # Windows
python3 -m pip3 --no-cache-dir -r requirements.txt # Windows WSL, Linux and UNIX-Like systems (OSX)

    In a Bash/ZSH shell or in Windows WSL.

    1. Then, create a file named ".env" in the root folder of the project.

    2. Once that is done, enter the following lines into the .env file created earlier: TOKEN="[YOUR_TOKEN_HERE]" Remember to put the variable name in ALL CAPS and replace the brackets and the text inside it with your own token.

    3. After that, you're all set! Run the run.sh file or enter python main.py for Windows and python3 main.py for Linux and Unix-like systems.

Changelog

See CHANGELOG.md

Addendum A

Run docker image ls to see available images and their IDs

Comments
  • Sourcery refactored master branch

    Sourcery refactored master branch

    Branch master refactored by Sourcery.

    If you're happy with these changes, merge this Pull Request using the Squash and merge strategy.

    See our documentation here.

    Run Sourcery locally

    Reduce the feedback loop during development by using the Sourcery editor plugin:

    Review changes via command line

    To manually merge these changes, make sure you're on the master branch, then run:

    git fetch origin sourcery/master
git merge --ff-only FETCH_HEAD
git reset HEAD^

    Help us improve this pull request!

    opened by sourcery-ai[bot] 1
  • [Snyk] Security upgrade python from 3.9.5 to 3.9

    [Snyk] Security upgrade python from 3.9.5 to 3.9

    Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.

    Changes included in this PR

    • Dockerfile

    We recommend upgrading to python:3.9, as this image has only 237 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.

    Some of the most important vulnerabilities in your base image include:

    | Severity | Priority Score / 1000 | Issue | Exploit Maturity | | :------: | :-------------------- | :---- | :--------------- | | critical severity | 714 | Buffer Overflow
    SNYK-DEBIAN10-OPENSSL-1569403 | No Known Exploit | | critical severity | 714 | Buffer Overflow
    SNYK-DEBIAN10-OPENSSL-1569403 | No Known Exploit | | critical severity | 714 | Buffer Overflow
    SNYK-DEBIAN10-OPENSSL-1569403 | No Known Exploit | | high severity | 614 | Out-of-bounds Read
    SNYK-DEBIAN10-OPENSSL-1569406 | No Known Exploit | | medium severity | 514 | CVE-2021-4160
    SNYK-DEBIAN10-OPENSSL-2388381 | No Known Exploit |

    Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

    For more information: 🧐 View latest project report

    🛠 Adjust project settings

    Learn how to fix vulnerabilities with free interactive lessons:

    🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

    opened by snyk-bot 0
  • [Snyk] Security upgrade python from 3.9.5 to 3.9.10

    [Snyk] Security upgrade python from 3.9.5 to 3.9.10

    Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.

    Changes included in this PR

    • Dockerfile

    We recommend upgrading to python:3.9.10, as this image has only 237 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.

    Some of the most important vulnerabilities in your base image include:

    | Severity | Priority Score / 1000 | Issue | Exploit Maturity | | :------: | :-------------------- | :---- | :--------------- | | critical severity | 500 | Integer Overflow or Wraparound
    SNYK-DEBIAN10-EXPAT-2406128 | No Known Exploit | | critical severity | 714 | Buffer Overflow
    SNYK-DEBIAN10-OPENSSL-1569403 | No Known Exploit | | critical severity | 714 | Buffer Overflow
    SNYK-DEBIAN10-OPENSSL-1569403 | No Known Exploit | | critical severity | 714 | Buffer Overflow
    SNYK-DEBIAN10-OPENSSL-1569403 | No Known Exploit | | high severity | 614 | Out-of-bounds Read
    SNYK-DEBIAN10-OPENSSL-1569406 | No Known Exploit |

    Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

    For more information: 🧐 View latest project report

    🛠 Adjust project settings

    Learn how to fix vulnerabilities with free interactive lessons:

    🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

    opened by snyk-bot 0
  • [Snyk] Security upgrade python from 3.9.5 to 3.9

    [Snyk] Security upgrade python from 3.9.5 to 3.9

    Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.

    Changes included in this PR

    • Dockerfile

    We recommend upgrading to python:3.9, as this image has only 235 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.

    Some of the most important vulnerabilities in your base image include:

    | Severity | Priority Score / 1000 | Issue | Exploit Maturity | | :------: | :-------------------- | :---- | :--------------- | | high severity | 567 | SQL Injection
    SNYK-DEBIAN10-CYRUSSASL2-2412041 | No Known Exploit | | high severity | 567 | SQL Injection
    SNYK-DEBIAN10-CYRUSSASL2-2412041 | No Known Exploit | | critical severity | 714 | Buffer Overflow
    SNYK-DEBIAN10-OPENSSL-1569403 | No Known Exploit | | critical severity | 714 | Buffer Overflow
    SNYK-DEBIAN10-OPENSSL-1569403 | No Known Exploit | | high severity | 614 | Out-of-bounds Read
    SNYK-DEBIAN10-OPENSSL-1569406 | No Known Exploit |

    Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

    For more information: 🧐 View latest project report

    🛠 Adjust project settings

    Learn how to fix vulnerabilities with free interactive lessons:

    🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

    opened by snyk-bot 0
  • [Snyk] Security upgrade python from 3.8 to 3.9.5

    [Snyk] Security upgrade python from 3.8 to 3.9.5

    Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.

    Changes included in this PR

    • Dockerfile

    We recommend upgrading to python:3.9.5, as this image has only 458 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.

    Some of the most important vulnerabilities in your base image include:

    | Severity | Priority Score / 1000 | Issue | Exploit Maturity | | :------: | :-------------------- | :---- | :--------------- | | critical severity | 500 | Integer Overflow or Wraparound
    SNYK-DEBIAN11-EXPAT-2331802 | No Known Exploit | | critical severity | 500 | Integer Overflow or Wraparound
    SNYK-DEBIAN11-EXPAT-2331808 | No Known Exploit | | critical severity | 500 | Integer Overflow or Wraparound
    SNYK-DEBIAN11-EXPAT-2331811 | No Known Exploit | | critical severity | 500 | Integer Overflow or Wraparound
    SNYK-DEBIAN11-EXPAT-2359255 | No Known Exploit | | critical severity | 500 | Integer Overflow or Wraparound
    SNYK-DEBIAN11-EXPAT-2384928 | No Known Exploit |

    Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

    For more information: 🧐 View latest project report

    🛠 Adjust project settings

    opened by snyk-bot 0
  • [Snyk] Security upgrade python from 3.8 to 3.10.0b3

    [Snyk] Security upgrade python from 3.8 to 3.10.0b3

    Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.

    Changes included in this PR

    • Dockerfile

    We recommend upgrading to python:3.10.0b3, as this image has only 458 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.

    Some of the most important vulnerabilities in your base image include:

    | Severity | Priority Score / 1000 | Issue | Exploit Maturity | | :------: | :-------------------- | :---- | :--------------- | | critical severity | 500 | Integer Overflow or Wraparound
    SNYK-DEBIAN11-EXPAT-2331802 | No Known Exploit | | critical severity | 500 | Integer Overflow or Wraparound
    SNYK-DEBIAN11-EXPAT-2331808 | No Known Exploit | | critical severity | 500 | Integer Overflow or Wraparound
    SNYK-DEBIAN11-EXPAT-2331811 | No Known Exploit | | critical severity | 500 | Integer Overflow or Wraparound
    SNYK-DEBIAN11-EXPAT-2359255 | No Known Exploit | | critical severity | 500 | Integer Overflow or Wraparound
    SNYK-DEBIAN11-EXPAT-2384928 | No Known Exploit |

    Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

    For more information: 🧐 View latest project report

    🛠 Adjust project settings

    opened by snyk-bot 0
  • [Snyk] Security upgrade python from 3.8 to 3.9.5

    [Snyk] Security upgrade python from 3.8 to 3.9.5

    Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.

    Changes included in this PR

    • Dockerfile

    We recommend upgrading to python:3.9.5, as this image has only 449 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.

    Some of the most important vulnerabilities in your base image include:

    | Severity | Priority Score / 1000 | Issue | Exploit Maturity | | :------: | :-------------------- | :---- | :--------------- | | critical severity | 571 | Integer Overflow or Wraparound
    SNYK-DEBIAN11-EXPAT-2359255 | No Known Exploit | | critical severity | 571 | Integer Overflow or Wraparound
    SNYK-DEBIAN11-EXPAT-2359255 | No Known Exploit | | critical severity | 571 | Integer Overflow or Wraparound
    SNYK-DEBIAN11-EXPAT-2384928 | No Known Exploit | | critical severity | 571 | Integer Overflow or Wraparound
    SNYK-DEBIAN11-EXPAT-2384928 | No Known Exploit | | critical severity | 500 | Improper Input Validation
    SNYK-DEBIAN11-PYTHON39-1290158 | No Known Exploit |

    Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

    For more information: 🧐 View latest project report

    🛠 Adjust project settings

    opened by snyk-bot 0
  • [Snyk] Security upgrade python from 3.8 to 3.10.0b2

    [Snyk] Security upgrade python from 3.8 to 3.10.0b2

    Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.

    Changes included in this PR

    • Dockerfile

    We recommend upgrading to python:3.10.0b2, as this image has only 449 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.

    Some of the most important vulnerabilities in your base image include:

    | Severity | Priority Score / 1000 | Issue | Exploit Maturity | | :------: | :-------------------- | :---- | :--------------- | | critical severity | 571 | Integer Overflow or Wraparound
    SNYK-DEBIAN11-EXPAT-2359255 | No Known Exploit | | critical severity | 571 | Integer Overflow or Wraparound
    SNYK-DEBIAN11-EXPAT-2359255 | No Known Exploit | | critical severity | 571 | Integer Overflow or Wraparound
    SNYK-DEBIAN11-EXPAT-2384928 | No Known Exploit | | critical severity | 571 | Integer Overflow or Wraparound
    SNYK-DEBIAN11-EXPAT-2384928 | No Known Exploit | | critical severity | 500 | Improper Input Validation
    SNYK-DEBIAN11-PYTHON39-1290158 | No Known Exploit |

    Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

    For more information: 🧐 View latest project report

    🛠 Adjust project settings

    opened by snyk-bot 0
  • [Snyk] Security upgrade python from 3.8 to 3.10.0b2

    [Snyk] Security upgrade python from 3.8 to 3.10.0b2

    Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.

    Changes included in this PR

    • Dockerfile

    We recommend upgrading to python:3.10.0b2, as this image has only 449 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.

    Some of the most important vulnerabilities in your base image include:

    | Severity | Priority Score / 1000 | Issue | Exploit Maturity | | :------: | :-------------------- | :---- | :--------------- | | critical severity | 571 | Integer Overflow or Wraparound
    SNYK-DEBIAN11-EXPAT-2359255 | No Known Exploit | | critical severity | 571 | Integer Overflow or Wraparound
    SNYK-DEBIAN11-EXPAT-2359255 | No Known Exploit | | critical severity | 571 | Integer Overflow or Wraparound
    SNYK-DEBIAN11-EXPAT-2384928 | No Known Exploit | | critical severity | 571 | Integer Overflow or Wraparound
    SNYK-DEBIAN11-EXPAT-2384928 | No Known Exploit | | critical severity | 500 | Buffer Overflow
    SNYK-DEBIAN11-GLIBC-2340922 | No Known Exploit |

    Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

    For more information: 🧐 View latest project report

    🛠 Adjust project settings

    opened by snyk-bot 0
  • Bump certifi from 2021.10.8 to 2022.12.7

    Bump certifi from 2021.10.8 to 2022.12.7

    Bumps certifi from 2021.10.8 to 2022.12.7.

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies 
    opened by dependabot[bot] 0
  • [Snyk] Security upgrade aiohttp from 3.7.4.post0 to 3.8.0

    [Snyk] Security upgrade aiohttp from 3.7.4.post0 to 3.8.0

    This PR was automatically created by Snyk using the credentials of a real user.


    Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.

    Changes included in this PR

    • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
      • requirements.txt

    Vulnerabilities that will be fixed

    By pinning:

    Severity | Priority Score (*) | Issue | Upgrade | Breaking Change | Exploit Maturity :-------------------------:|-------------------------|:-------------------------|:-------------------------|:-------------------------|:------------------------- high severity | 686/1000
    Why? Proof of Concept exploit, Has a fix available, CVSS 7.3 | HTTP Header Injection
    SNYK-PYTHON-AIOHTTP-1584144 | aiohttp:
    3.7.4.post0 -> 3.8.0
    | No | Proof of Concept

    (*) Note that the real score may have changed since the PR was raised.

    Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

    Check the changes in this PR to ensure they won't cause issues with your project.

    Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

    For more information: 🧐 View latest project report

    🛠 Adjust project settings

    📚 Read more about Snyk's upgrade and patch logic

    Learn how to fix vulnerabilities with free interactive lessons:

    🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

    opened by BiasedKiwi 0
  • [Snyk] Security upgrade aiohttp from 3.7.4.post0 to 3.8.0

    [Snyk] Security upgrade aiohttp from 3.7.4.post0 to 3.8.0

    This PR was automatically created by Snyk using the credentials of a real user.


    Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.

    Changes included in this PR

    • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
      • requirements.txt

    Vulnerabilities that will be fixed

    By pinning:

    Severity | Priority Score (*) | Issue | Upgrade | Breaking Change | Exploit Maturity :-------------------------:|-------------------------|:-------------------------|:-------------------------|:-------------------------|:------------------------- high severity | 686/1000
    Why? Proof of Concept exploit, Has a fix available, CVSS 7.3 | HTTP Header Injection
    SNYK-PYTHON-AIOHTTP-1584144 | aiohttp:
    3.7.4.post0 -> 3.8.0
    | No | Proof of Concept

    (*) Note that the real score may have changed since the PR was raised.

    Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

    Check the changes in this PR to ensure they won't cause issues with your project.

    Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

    For more information: 🧐 View latest project report

    🛠 Adjust project settings

    📚 Read more about Snyk's upgrade and patch logic

    Learn how to fix vulnerabilities with free interactive lessons:

    🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

    opened by BiasedKiwi 0
  • [Snyk] Security upgrade aiohttp from 3.7.4.post0 to 3.8.0

    [Snyk] Security upgrade aiohttp from 3.7.4.post0 to 3.8.0

    This PR was automatically created by Snyk using the credentials of a real user.


    Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.

    Changes included in this PR

    • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
      • requirements.txt

    Vulnerabilities that will be fixed

    By pinning:

    Severity | Priority Score (*) | Issue | Upgrade | Breaking Change | Exploit Maturity :-------------------------:|-------------------------|:-------------------------|:-------------------------|:-------------------------|:------------------------- high severity | 686/1000
    Why? Proof of Concept exploit, Has a fix available, CVSS 7.3 | HTTP Header Injection
    SNYK-PYTHON-AIOHTTP-1584144 | aiohttp:
    3.7.4.post0 -> 3.8.0
    | No | Proof of Concept

    (*) Note that the real score may have changed since the PR was raised.

    Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

    Check the changes in this PR to ensure they won't cause issues with your project.

    Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

    For more information: 🧐 View latest project report

    🛠 Adjust project settings

    📚 Read more about Snyk's upgrade and patch logic

    Learn how to fix vulnerabilities with free interactive lessons:

    🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

    opened by BiasedKiwi 0
Releases(v0.7.4)

  • v0.7.4(Jan 28, 2022)

    Version 0.7.4

    What's Changed

    • Minor changes to the install script by @shadawcraw in https://github.com/shadawcraw/Hadum-Bot/pull/26

    Full Changelog: https://github.com/shadawcraw/Hadum-Bot/compare/v0.7.3...v0.7.4

    Source code(tar.gz)
    Source code(zip)

  • v0.7.3(Jan 27, 2022)

    Version 0.7.3

    What's Changed

    • General code cleanup by @shadawcraw in https://github.com/shadawcraw/Hadum-Bot/pull/25

    Full Changelog: https://github.com/shadawcraw/Hadum-Bot/compare/v0.7.2...v0.7.3

    Source code(tar.gz)
    Source code(zip)

  • v0.7.2(Jan 27, 2022)

    Version 0.7.2

    What's Changed

    • Update install script by @shadawcraw in https://github.com/shadawcraw/Hadum-Bot/pull/22

    Full Changelog: https://github.com/shadawcraw/Hadum-Bot/compare/v0.7.1...v0.7.2

    Source code(tar.gz)
    Source code(zip)

  • v0.7.1(Jan 25, 2022)

    Version 0.7.1

    What's Changed

    • Update issue templates by @shadawcraw in https://github.com/shadawcraw/Hadum-Bot/pull/2
    • Added SQLite Support by @shadawcraw in https://github.com/shadawcraw/Hadum-Bot/pull/8
    • Sourcery refactored master branch by @sourcery-ai in https://github.com/shadawcraw/Hadum-Bot/pull/20
    • Add install script by @shadawcraw in https://github.com/shadawcraw/Hadum-Bot/pull/21

    New Contributors

    • @sourcery-ai made their first contribution in https://github.com/shadawcraw/Hadum-Bot/pull/20

    Full Changelog: https://github.com/shadawcraw/Hadum-Bot/compare/v0.9.0...v0.7.1

    Source code(tar.gz)
    Source code(zip)

  • v0.8.0(Jan 27, 2022)

    Version 0.8.0

    What's Changed

    • Auto Updates and Discord Status by @shadawcraw in https://github.com/shadawcraw/Hadum-Bot/pull/19

    Full Changelog: https://github.com/shadawcraw/Hadum-Bot/compare/v0.6.2...v0.8.0

    Source code(tar.gz)
    Source code(zip)

  • v0.7.0(Dec 19, 2021)

    Version 0.7.0

    What's Changed

    • Auto Updates and Discord Status by @shadawcraw in https://github.com/HadumDev/Hadum-Bot/pull/19

    Full Changelog: https://github.com/HadumDev/Hadum-Bot/compare/v0.6.2...v0.7.0

    Source code(tar.gz)
    Source code(zip)

  • v0.6.2(Dec 19, 2021)

    Version 0.6.2

    What's Changed

    • Add .env.example by @shadawcraw in https://github.com/HadumDev/Hadum-Bot/pull/18

    Full Changelog: https://github.com/HadumDev/Hadum-Bot/compare/v0.6.1...v0.6.2

    Source code(tar.gz)
    Source code(zip)

  • v0.6.1(Dec 18, 2021)

    Version 0.6.1

    What's Changed

    • v0.6.0 by @shadawcraw in https://github.com/HadumDev/Hadum-Bot/pull/15
    • v0.6.1 by @shadawcraw in https://github.com/HadumDev/Hadum-Bot/pull/16

    Full Changelog: https://github.com/HadumDev/Hadum-Bot/compare/v0.6.0...v0.6.1

    Source code(tar.gz)
    Source code(zip)

  • v0.6.0(Dec 13, 2021)

  • v0.5.0(Dec 13, 2021)

  • v0.4.0(Dec 13, 2021)

  • v0.3.0(Dec 13, 2021)

  • v0.2.0(Dec 13, 2021)

  • v0.1.0(Dec 13, 2021)

Owner
GitHub Repository
Valorant store offer discord-bot

Valorant store checker - Discord Bot Discord bot that shows your daily store offer without open the VALORANT by using the Ingame API. written using Py

STACIA 226 Jan 02, 2023
Bancos de Dados Relacionais (SQL) na AWS com Amazon RDS.

Bancos de Dados Relacionais (SQL) na AWS com Amazon RDS Explorando o Amazon RDS, um serviço de provisionamente e gerenciamento de banco de dados relac

Lucas Magalhães 1 Dec 05, 2021
A discord bot wrapper for python have slash command

A discord bot wrapper for python have slash command

4 Dec 04, 2021
User-Bot for reporting russian propaganda channels

Юзер-Бот, що автоматизує репортування Телеграм каналів пропагандистів Цей Телеграм Юзер-Бот використовується для автоматизації репорту пропагандистьск

58 Nov 07, 2022
GitHub Activity Generator - A script that helps you instantly generate a beautiful GitHub Contributions Graph for the last year.

GitHub Activity Generator A script that helps you instantly generate a beautiful GitHub Contributions Graph for the last year. Before 😐 😶 😒 After ?

1 Dec 30, 2021
CyberTKR - CyberTK-API

CyberTKR - CyberTK-API

TKR 2 Apr 08, 2022
Neko: An Anime themed advance Telegram group management bot

𝑪𝒖𝒕𝒊𝒆𝒑𝒊𝒊 𝑹𝒐𝒃𝒐𝒕 A modular telegram Python bot running on python3 wit

「 Rajkumar™ 」 39 Jan 08, 2023
Drop-in Replacement of pychallonge

pychal Pychal is a drop-in replacement of pychallonge with some extra features and support for new Python versions. Pychal provides python bindings fo

ZED 29 Nov 28, 2022
A demo without 🚀 science, just simple UTXO spending logic.

Stuck TX Demo Docker container that runs 4 dogecoind to demonstrate "the stuck tx problem". Scenario A wallet sends out 3 transactions to a recipient

Patrick Lodder 2 Nov 16, 2021
A simple bot to upload file to various cloud servers.

Cloudsy Bot A simple bot to upload file to various cloud servers. Variables API_HASH Your API Hash from my.telegram.org API_ID Your API ID from my.tel

Flying Santas 8 Oct 31, 2022
A simple and modular Discord bot with various functionalities.

All-In-Bot for Discord A simple and modular Discord bot with various functionalities. How to use the bot? Simple! Just invite the bot to your server u

Th3J0nny 3 Jan 29, 2022
A repo to automate the booking process for vaccinations

OntarioVaccineFormAutomaker A repo to automate the booking process for vaccinations Requirements Allow ALL sights to be able to know your location (on

Rafid Dewan 7 May 31, 2021
ClearML - Auto-Magical Suite of tools to streamline your ML workflow. Experiment Manager, MLOps and Data-Management

ClearML - Auto-Magical Suite of tools to streamline your ML workflow Experiment Manager, MLOps and Data-Management ClearML Formerly known as Allegro T

ClearML 3.9k Jan 01, 2023
A bot for the [email protected] Discord server.

KittyBot - a sentient Discord bot! Key Notes An open-source, community-powered bot for the [email 

Ollie 11 Dec 06, 2022
unofficial library for discord components(on development)

discord.py-buttons unofficial library for discord buttons(on development) Install pip install --upgrade discord_buttons Example from discord import Cl

kiki7000 129 Dec 31, 2022
Spore API wrapper written in Python

A wrapper for the Spore API that simplifies and complements its functionality

1 Nov 25, 2021
GitHub action to deploy serverless functions to YandexCloud

YandexCloud serverless function deploy action Deploy new serverless function version (including function creation if it does not exist). Inputs yc_acc

Много Лосося 4 Apr 10, 2022
Basic-Discord-Response-Bot, in Python

Response bot for Discord. EG: User: Hello! Bot: Hello there! About Very customizable, no credits needed. Edit the bot.py to what you want, basic Pytho

rhys 1 Nov 20, 2021
SI_EXPLAINER_tg_bot: This bot is an assistant for medical professionals in interpreting the results of patient clustering.

SI_EXPLAINER_tg_bot This bot is an assistant for medical professionals in interpreting the results of patient clustering. ABOUT This chatbot was devel

Alexander Kanonirov 1 Jan 21, 2022
Random Geek Jokes REST API

Geek-Jokes A RESTful API to get random geek jokes written in Flask What is the Geek-Jokes-api? The Geek Jokes RESTful API lets you fetch a random geek

Sameer Kumar 84 Dec 15, 2022