Closed shturmann closed 2 years ago
Even if i do bot.Dota2.exit(); in
bot.Dota2.leavePracticeLobby(function (err, body) {
console.log(38);
console.log('leavePracticeLobby body/////////////////////////');
bot.free = true;
bot.currentLobby.id = null;
console.log(err, body, '////////////////////////////////////////');
bot.Dota2.abandonCurrentGame(function (err, body) {});
util.log('[Bot #' + bot.id + '] ' + 'Bot leave lobby by timeout');
bot.Dota2.exit();
// bot.Dota2.leaveAbandonedChat();
});
bot still listening postgame channel O_O
27 Jun 13:19:59 - Sending match CMsgAbandonCurrentGame request
27 Jun 13:19:59 - GC not ready, please listen for the 'ready' event.
27 Jun 13:19:59 - [Bot #1] Bot leave lobby by timeout
27 Jun 13:19:59 - Exiting Dota 2
27 Jun 13:19:59 - Cache unsubscribed, 26199248896956068
27 Jun 13:20:08 - Chat channel PostGame_26199248896956068 has 1 person(s) online
27 Jun 13:20:08 - 76561198085031857 joined channel PostGame_26199248896956068
27 Jun 13:20:10 - Chat channel PostGame_26199248896956068 has 2 person(s) online
Chat channels are separate from lobbies. Leaving a lobby does not disconnect you from the chat, you need to disconnect separately.
Hello, sorry for maybe a stupid question, but I was stumped.
I found a bot that works on binary logs, but I don’t quite understand how it works, because I’m not even a Node developer :)
The bot successfully enters Steam, Dota2, creates a lobby, sends invites and starts the game. But after that, it stops responding to the same event that should restart the creation of an invite-start lobby. It seems to me that this is due to the fact that the bot is "stuck" in the post-game chat channel, remaining on its listening, and the logic of the code considers that it is still busy.
Can you even tell me if I'm digging in that direction?
Here is the logic of the bot with my idiotic attempts to understand what is happening in it.