Game compliance
Competitive integrity is one of our core values, and we work tirelessly to enforce this value, both in-house and with the cooperation of game developers.
NetEase's game compliance policy prevents giving users confidential information like damage and healing statistics, selectively ban heroes, and predict opponents' ultimate abilities. Apps that severely undermine the fairness of the game are deemed as cheating software and will not be allowed during gameplay.
Overwolf’s app policy and game compliance guidelines strictly forbid giving any kind of player advantages in its apps. In addition, apps will also need to comply with the game’s ToS.
- Game events API
Please read the overwolf.games.events documentation page to learn how to use Overwolf game events.
Sample Apps
Available Features
Game events status
It's highly recommended to communicate errors and warnings to your app users. Check current game event status here or easily check game event status from your app using our API.
gep_internal
match_info
Info Updates
| key | Category | Values | Notes | Since GEP Ver. |
|---|---|---|---|---|
| roster_xx | match_info | A full roster with data during the match. | See notes | 269.0 |
| match_id | match_info | The match ID of the current match. | See notes | 269.0 |
| game_type | match_info | The current game type. | See notes | 269.0 |
| game_mode | match_info | The current game mode. | See notes | 269.0 |
| map | match_info | The current played map. | See notes | 269.0 |
| player_stats | match_info | Local player's statistics during the match. | See notes | 269.0 |
| match_outcome | match_info | Outcome of the current match | See notes | 272.0 |
| banned_characters | match_info | The name and IDs of the banned characters in the match | See notes | 281.0 |
| ability_cooldown_X | match_info | Abbility cooldown timer in seconds | See notes | 282.0 |
| additional_ability_cd_X | match_info | Teamup abbility cooldown timer in seconds | See notes | 282.0 |
| objective_progress | match_info | Display the progress data for different game modes | See notes | 282.0 |
| game_mode_id | match_info | The current game mode ID. | See notes | 287.0 |
| selected_character | match_info | The name and IDs of the highlighted and the selected character | See notes | 296.0 |
roster_xx note
The roster index number will change dynamically between 0-11. To keep track of each player, use the UID number or name parameters.
When playing in Competitive mode with Diamond 3 players and above, all player names will be hidden as ***** until the round begins. Once the round starts, player names will be revealed, except for players who have the hidden names option enabled.
List of parameters:
- name - player name
- uid - User ID
- character_name - character name
- character_id - character ID
- team - team number
- is_teammate - is the player one of your teammates true/false
- kills - number of kills
- deaths - number of deaths
- assists - number of assists
- ult_charge - the player's current ultimate ability charge percent (teammates only)
- is_alive - if the player is alive or dead
- is_local - if the player is the local player this paramaters is true
- elo_score - the player's ELO
- is_disconnected - if the player is connected to the match
Data Example:
{"feature": "match_info", "category": "match_info", "key": "roster_11", "data": "{\"uid\":\"1380486120\",\"name\":\"Jack\",\"character_id\":\"1038\",\"team\":0,\"kills\":16,\"deaths\":7,\"assists\":6,\"ult_charge\":0,\"elo_score\":2949,\"is_alive\":false,\"is_teammate\":true,\"is_disconnected\":false,\"is_local\":true,\"character_name\":\"SCARLET WITCH\"}"}
match_id note
Data Example:
{"feature": "match_info", "category": "match_info", "key": "match_id", "data": "5664983_1735659917_267_11001_50"}