You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
benji7425 b77eded7c2 3.4.0 3 years ago
..
core-commands git subrepo pull (merge) discord-bot-core 4 years ago
.gitignore Sqaush merge and adapt for template update using shared core code 4 years ago
.gitrepo git subrepo push --force discord-bot-core 3 years ago
.npmrc Sqaush merge and adapt for template update using shared core code 4 years ago
BaseEmbeddedData.js Refactor for efficiency and improved readability 4 years ago
BaseGuildData.js Fix various issues in core 4 years ago
Client.js Disable a few unused websocket events 3 years ago
Command.js Housekeeping 4 years ago
HandleGuildMessage.js 3.2.0-b2 4 years ago
LICENSE git subrepo pull (merge) discord-bot-core 3 years ago
README.md git subrepo pull (merge) discord-bot-core 3 years ago
Util.js 3.2.2 3 years ago
index.js Refactor for efficiency and improved readability 4 years ago
internal-config.json Update default NeDB compaction schedule to once per minute 3 years ago
monitor.js Add daily auto restart 3 years ago
package-lock.json Fix various issues in core 4 years ago
package.json Fix various issues in core 4 years ago

README.md

Discord bot core

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.

Built with

Contributing

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 discord-bot-core fork.
If you are uncomfortable using git subrepo, you could just as easily copy/paste your child discord-bot-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 discord-bot-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.