Open source version of Games bot.
This repository does contain only source code. You would not be able to compile it and use as it does not contain database, config template, images, dependencies, etc. This code can be only used for reference proposes. I do not provide any support regarding it.
this repository is not direct open sourcing of games bot, it is full remake of it using coroutines and full redesign of architecture.
- 2048
- achievements
- battleships
- chess
- connect_four
- dominoes
- global_stats
- hangman
- help
- local_stats
- minesweeper
- ping
- premium
- puzzle_15
- rubiks_cube
- sudoku
- tic_tac_toe
- website
- reports to websites like top.gg
- statistics collection
Every module is a runtime linking .so which inherits Module class
Every module inherits basic module and implements 3 methods init, run, stop and also create factory function which will create module
and return shared_ptr to it.
Every module (if it is planned to be accessible) should have an abstract class of it which will be included into Modules using it defining all public methods and variables, And all the implementation should be separated into different file, this way we can decrease headers parsing and remove need to link dependencies of current module to another when it is not needed.
Every module has its own name and dependencies list (list of names of modules this module is dependent on). Modules_manager will handle them and load in appropriate order, also it is made to notify about missing or circular dependencies.
Bot implements admin terminal running with executable. Each command can add its own command to terminal at runtime which can be run by owner. For example, manually load/stop modules, forbidding modules loading, adding new connection to Database pool, etc.
Database is based on using combination of connections pool and C++20 coroutines, you can define amount of connections which should be open and executed in parallel and use coroutines approach to create sql queries. No more callback hell!!!
When you create task of sql request it is automatically adds itself to the queue and could be picked up by one of open connections. So by the time you call co_await (somewhere later in the code) you can already have response from database which will make awaiting instant as it will just return value.
Database module also supports prepared statements and executing them is made as template so no need to predefine parameters amount or their types.
Support for background queries, if you need to insert something why make user wait for it to happen, just do request in background.
All the components ids are hidden from user to prevent self-bots make automation based on ids.
We have created Id_cache class for automating id hiding. it uses 64-bit unsigned integer to map them discord components ids. to store ids at runtime which are always cleared when no needed anymore. They are randomly chosen every time, so same custom_id will not produce same hidden id which is passed to discord and user.
This approach is used in select_click_handler and button_click_handler to make life of self-bots a bit harder (self-bots are forbidden by TOS of discord).
Interaction handlers implement way to await interactions on specific message using our unique ids, check for specific users allow to interact and timeouts which make them really handy.
As advantage now the length of our custom ids basically has no limit (discord limits custom component ids to 100 bytes) in size so we can store as much data as we want there.