Commands

Format: Command <Required Parameter> [Optional Parameter]

Tip

In koishi: commands, command aliases can be created, allowing you to eliminate the "dota2tracker" prefix or establish a simple alias "match" for "dota2tracker.query-match".

Tip

The following content is generated based on the command help text in the plugin, essentially equivalent to executing command -h.

---

dota2tracker.subscribe

Description

After subscribing, players need to bind their Steam ID to this group.

Usage instructions

After subscribing, players need to bind their Steam ID to this group. BOT will subscribe to the new game data of bound players in this group. After the STRATZ game analysis is completed, the game data will be generated into a picture battle report and published to this group.

---

dota2tracker.unsubscribe

Description

Unsubscribe from this group.

---

dota2tracker.bind <steam_id> [nick_name]

Description

Bind your SteamID and optionally set a nickname.

Usage instructions

Bind your SteamID to your account. If the group is subscribed, your new match data will be posted in the group in real-time.

Usage examples

bind 123456789bind 123456789 Johnbind 123456789 "John Doe"

---

dota2tracker.unbind

Description

Unbind your personal information.

---

dota2tracker.rename <nick_name>

Description

Change the nickname set during binding.

Usage examples

rename Johnrename "John Doe"

---

dota2tracker.query-members

Description

Query the players bound in this group.

---

dota2tracker.query-match <match_id>

Description

Query the match data of the specified match ID and generate a picture.

Option parameters

• --parse
  Whether to wait for match data parsing

Usage examples

query-match 1234567890query-match 1234567890 -pquery-match 1234567890 --parse

---

dota2tracker.query-recent-match [input_data]

Description

Query the most recent match data and generate a picture.

Option parameters

• --parse
  Whether to wait for match data parsing

Usage instructions

Query the most recent match data of the specified player and generate a picture. The parameter can be the player's SteamID or the nickname of a player bound in this group. If no parameter is provided, it will try to query the SteamID of the command caller.

Usage examples

query-recent-matchquery-recent-match 123456789query-recent-match Johnquery-recent-match 123456789 -pquery-recent-match John --parse

---

dota2tracker.query-player <input_data>

Description

Query the player's personal information, optionally specify a hero.

Option parameters

• --hero
  Query the player's usage of the specified hero (same as querying a hero, can use nickname or ID)

Usage instructions

Query the personal information of the specified player and generate a picture, optionally specify a hero. The parameter can be the player's SteamID or the nickname of a player bound in this group. If no parameter is provided, it will try to query the SteamID of the command caller.

Usage examples

query-playerquery-player 123456789query-player Johnquery-player John --hero Anti-Magequery-player John -o Anti-Mage

---

dota2tracker.query-hero <input_data>

Description

Query hero skills/stats information.

Option parameters

• --random
  Randomly select a hero.

Usage instructions

Query the hero's skill descriptions and various stats, generate a picture. The parameter can be the hero's ID, name, or common nickname.

Usage examples

query-hero 15query-hero Razorquery-hero -r

---

dota2tracker.query-item <input_data>

Description

Query item information

Usage instructions

Query item descriptions and attributes, then generate and publish an image report. Parameters can be item name (supports fuzzy search), item alias, or item ID. You can set the maximum number of items to send per query on the configuration page, as well as whether to send the item list when the limit is exceeded or parameters are not entered.

Usage examples

query-item Vanguard