Version 1.2.0 (Dota Edition)
Additions
-
Multi-bot support. Guilds and tournaments with a high match load can now host multiple lobbies at a time with multiple steam bot support. Running
npm run steam
for the second time will prompt you to add a second bot, or remove an existing one. -
MMR Support. The bot is now able to fetch users' MMR from OpenDota. Additionally, displaying MMR can be enforced through an option in
config.js
, preventing players from joining any events if they don't display their MMR publicly.What the bot cannot do is restrict an event to a range of MMR, but might in the future.
-
Added
cmpick
flag to theadd-inhouse
command, to decide who gets the first pick. -
Added
add_inhouse_is_admin_command
option toconfig.js
to give admins the ability to prevent regular users from adding inhouses to events. -
Added
game_generic_name
option to theconfig.js
so "Inhouse" can be relabeled to things like "Lobby" or "Match". This is useful for tournaments, where matches are not technically inhouses. -
Status command. This is an admin command that sends information about the bot. Currently: its uptime, and the status of all steam bots.
-
The bot is now able to detect the match ID on ticketed lobbies. In the future it might do useful stuff with the match results.
Changes
- Due to multiple lobbies being able to be hosted at a time, commands like
resend-invite
andforce-lobby-start
now require you to pass the event ID. - Expired events are now unpinned from the master channel.
Other
- Updated the
node-dota2
dependency.