Handling updates (new messages)
Update handling can be done in different ways:
Async Event driven
use danog\MadelineProto\EventHandler;
use danog\MadelineProto\Tools;
use danog\MadelineProto\API;
use danog\MadelineProto\Logger;
use danog\MadelineProto\Settings;
use danog\MadelineProto\RPCErrorException;
/**
* Event handler class.
*/
class MyEventHandler extends EventHandler
{
/**
* @var int|string Username or ID of bot admin
*/
const ADMIN = "danogentili"; // Change this
/**
* List of properties automatically stored in database (MySQL, Postgres, redis or memory).
* @see https://docs.madelineproto.xyz/docs/DATABASE.html
* @var array
*/
protected static array $dbProperties = [
'dataStoredOnDb' => 'array'
];
/**
* @var DbArray<array>
*/
protected $dataStoredOnDb;
/**
* Get peer(s) where to report errors
*
* @return int|string|array
*/
public function getReportPeers()
{
return [self::ADMIN];
}
/**
* Called on startup, can contain async calls for initialization of the bot
*/
public function onStart()
{
}
/**
* Handle updates from supergroups and channels
*
* @param array $update Update
*/
public function onUpdateNewChannelMessage(array $update): void
{
$this->onUpdateNewMessage($update);
}
/**
* Handle updates from users.
*
* @param array $update Update
*/
public function onUpdateNewMessage(array $update): void
{
if ($update['message']['_'] === 'messageEmpty' || $update['message']['out'] ?? false) {
return;
}
$res = \json_encode($update, JSON_PRETTY_PRINT);
$this->messages->sendMessage(['peer' => $update, 'message' => "This userbot is powered by MadelineProto!", 'reply_to_msg_id' => isset($update['message']['id']) ? $update['message']['id'] : null, 'parse_mode' => 'HTML']);
if (isset($update['message']['media']) && $update['message']['media']['_'] !== 'messageMediaGame') {
$this->messages->sendMedia(['peer' => $update, 'message' => $update['message']['message'], 'media' => $update]);
}
// Test MadelineProto's built-in database driver, which automatically maps to MySQL/PostgreSQL/Redis
// properties mentioned in the MyEventHandler::$dbProperties property!
// Remove the following code when running your bot
// Can be anything serializable: an array, an int, an object, ...
$myData = [];
if (isset($this->dataStoredOnDb['k1'])) {
$myData = $this->dataStoredOnDb['k1'];
}
$this->dataStoredOnDb['k1'] = $myData + ['moreStuff' => 'yay'];
$this->dataStoredOnDb['k2'] = 0;
unset($this->dataStoredOnDb['k2']);
$this->logger("Count: ".count($this->dataStoredOnDb));
// You can even iterate over the data
foreach ($this->dataStoredOnDb as $key => $value) {
$this->logger($key);
$this->logger($value);
}
}
}
$settings = new Settings;
$settings->getLogger()->setLevel(Logger::LEVEL_ULTRA_VERBOSE);
// For users or bots
MyEventHandler::startAndLoop('bot.madeline', $settings);
// For bots only
MyEventHandler::startAndLoopBot('bot.madeline', 'bot token', $settings);
This will create an event handler class MyEventHandler, create a MadelineProto session, and set the event handler class to our newly created event handler.
The new startAndLoop method automatically initializes MadelineProto, enables async, logs in the user/bot, initializes error reporting, catches and reports all errors surfacing from the event loop to the peers returned by the getReportPeers method.
All events are handled conrrently thanks to async, here’s a full explanation.
When an Update is received, the corresponding onUpdateType event handler method is called.
To get a list of all possible update types, click here.
If such a method does not exist, the onAny event handler method is called.
If the onAny event handler method does not exist, the update is ignored.
The onLoop method is not recommended anymore, use AMPHP’s repeat or MadelineProto’s async loop API to schedule actions in a cron-like manner.
To access the $MadelineProto instance inside of the event handler, simply access $this:
$this->messages->sendMessage(['peer' => '@danogentili', 'message' => 'hi']);
If you intend to use your own constructor in the event handler, make sure to call the parent construtor with the only parameter provided to your constructor.
To forecfully restart and apply changes made to the event handler class, call $MadelineProto->restart();.
Built-in database driver
You can also directly connect to any database using the same async MySQL/Postgres/Redis ORM used by MadelineProto internally.
To do so, simply specify the database settings, and declare a static $dbProperties property to initialize the async database mapper:
class MyEventHandler extends EventHandler
{
/**
* List of properties automatically stored in database (MySQL, Postgres, redis or memory).
* @see https://docs.madelineproto.xyz/docs/DATABASE.html
* @var array
*/
protected static array $dbProperties = [
'dataStoredOnDb' => 'array'
];
/**
* @var DbArray<array>
*/
protected $dataStoredOnDb;
// ...
And use the newly created $dataStoredOnDb property to access the database:
// Can be anything serializable, an array, an int, an object
$myData = [];
// Use the isset method to check whether some data exists in the database
if (isset($this->dataStoredOnDb['yourKey'])) {
// Always when fetching data
$myData = $this->dataStoredOnDb['yourKey'];
}
$this->dataStoredOnDb['yourKey'] = $myData + ['moreStuff' => 'yay'];
$this->dataStoredOnDb['otherKey'] = 0;
unset($this->dataStoredOnDb['otherKey']);
$this->logger("Count: ".count($this->dataStoredOnDb));
foreach ($this->dataStoredOnDb as $key => $value) {
$this->logger($key);
$this->logger($value);
}
Psalm generic typing is supported.
Self-restart on webhosts
When running the event handler via web, MadelineProto will automatically enable a magical self-restart hack (callback ID restarter), to keep the bot running even on webhosts with limited execution time.
Locking will also be handled automatically (as well as disconnection from the user that opened the page), so even if you start the script via web several times, only one instance will be running at a time (no need to do flocking manually!).
It relies on the shutdown function, so you must not set a custom shutdown function in your code, and instead use the MadelineProto shutdown static API:
use danog\MadelineProto\Shutdown;
$id = Shutdown::addCallback(static function () {
// This function will run on shutdown
});
$id = Shutdown::addCallback(static function () {
// This function will run on shutdown
}, 'custom id');
$id = Shutdown::addCallback(static function () {
// This function will overwrite the previously set function with custom id
}, 'custom id');
$ok = Shutdown::removeCallback($id);
You can of course pass non-static functions, any type of callable is accepted.
A second optional parameter can also be accepted, containing the ID of the callable: you can use this if you want to later overwrite the callable with another callback, or remove it altogether.
The removeCallback will return true if the callback exists and it was removed correctly, false otherwise (as with all new MadelineProto APIs, there are PHPDOCs for these methods so you’ll see them in your IDE).
Async event driven (multiaccount)
use danog\MadelineProto\EventHandler;
use danog\MadelineProto\Tools;
use danog\MadelineProto\API;
use danog\MadelineProto\Logger;
use danog\MadelineProto\RPCErrorException;
// Normal event handler definition as above
$MadelineProtos = [];
foreach ([
'bot.madeline' => 'Bot Login',
'user.madeline' => 'Userbot login',
'user2.madeline' => 'Userbot login (2)'
] as $session => $message) {
Logger::log($message, Logger::WARNING);
$MadelineProtos []= new API($session);
}
API::startAndLoopMulti($MadelineProtos, MyEventHandler::class);
This will create an event handler class EventHandler, create a combined MadelineProto session with session files bot.madeline, user.madeline, user2.madeline, and set the event handler class to our newly created event handler.
Usage is the same as for the normal event handler, with the difference is that multiple accounts can receive and handle updates in parallel, each with its own event handler instance.
Noop
$MadelineProto = new \danog\MadelineProto\API('bot.madeline');
$MadelineProto->start();
$MadelineProto->setNoop();
When an Update is received, nothing is done. This is useful if you need to populate the internal peer database with peers to avoid This peer is not present in the internal peer database errors, but don’t need to handle updates.
This is the default.