Module and command support are basically working. You can still include local modules though. So you can include modules just by including them in the package.json. I'm currently planning on having most modules be an NPM package. You can see an example module in src/modules/. See the sample config for how to configure, then run tsc and then node bin/index.js to start the bot. Each endpoint will provide its own extra details in the event, but the basis of each event will tell you who triggered the event, and what endpoint the event came from.Ĭurrently a work in progress. For IRC, a QUIT will be mapped to every channel that user was part of as a Leave. Leave is when the user is no longer available in that channel. Join is whenever a user joins a location the bot can see (usually a channel). It understands how to join and leave channels (some endpoints don't support it).Įvery endpoint needs to emit 3 different events: Join, Leave, and Message. Various properts can be added on a per endpoint basis and used in a module, but the bot itself operates in a very abstract manner.Īn endpoint is just a connection that has a "me" object (who the bot is on this endpoint), and that's basically it. ![]() A lot of information gets abstracted out, but considering a large portion of that information isn't needed for a typical bot, it's worth the abstraction. The goal of the bot was to have a framework that can connect to multiple endpoints and work the same way regardless of the endpoint. A bot written in Typescript that connects to various chat services such as Discord, Telegram, and IRC.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |