subrepo: subdir: "core" merged: "7a3eed3" upstream: origin: "firstname.lastname@example.org:benji7425/discord-bot-core.git" branch: "master" commit: "7a3eed3" git-subrepo: version: "0.3.1" origin: "???" commit: "???"
|2 years ago|
|commands||2 years ago|
|.gitignore||2 years ago|
|.gitrepo||2 years ago|
|.npmrc||2 years ago|
|LICENSE||2 years ago|
|README.md||2 years ago|
|base-embedded-data.js||2 years ago|
|base-guild-data.js||2 years ago|
|client.js||2 years ago|
|command.js||2 years ago|
|handle-guild-message.js||2 years ago|
|index.js||2 years ago|
|internal-config.json||2 years ago|
|package-lock.json||2 years ago|
|package.json||2 years ago|
|util.js||2 years ago|
Core code for connection and command handling for my Discord bots.
This is not actually a Discord bot. To learn about some of my available Discord bots please visit my website
This code is included in the repo for each bot using git subrepo, which I prefer over submodules and subtrees.
This code does not function on it’s own, it simply provides common functionality my Discord bots can make use of. To test/modify this code, it needs to be run in the context of an actual bot. A good candidate is my template project, which should run and connect just fine, just won’t do much.
The easiest way to get setup would be a fork of this repo, and the fork of a bot to use as a development context.
I suggest using my template project as a development context, along with git subrepo to push back to your core fork.
If you are uncomfortable using git subrepo, you could just as easily copy/paste your child
core directory back into your fork.
My template project has more in-depth details about how to setup and test.
If you have a completed change, please submit a pull request from your
core fork back to this repo.
Whilst this is very easy to use once you know how, I appreciate this might be a little tricky if you aren’t familiar with developing in this way. Feel free to contact me if you would like assistance. Find contact details here.