Support for this game has been deprecated, following a lack of usage in Apps.
This page is being kept for historical documentation purposes.
Please read the overwolf.games.events documentation page to learn how to use Overwolf game events.
Sample Apps
Available Features
This is a on-going development. All events and info updates can be target to changes.
- gep_internal
- me
- match_info
- matching
- character_selection
- kills
- announces
- game_objects
- day_change
- move_regions
- scoreboards
- damages
- level_ups
- routes
- equipments
- restriction_timers
- match_ends
Game event status
It is highly recommended to communicate errors and warnings to app users.
Check the current game event status here. Alternatively, you can easily check that status from your app itself, using our API.
gep_internal
Info Updates
| key | Category | Values | Notes | Since GEP Ver. |
|---|---|---|---|---|
| gep_internal | gep_internal | Local + Public version number | See notes | 143.0 |
gep_internal note
Data Example:
{"info":{"gep_internal":{"version_info":"{"local_version":"157.0.1","public_version":"157.0.1","is_updated":true}"}},"feature":"gep_internal"}
me
Info Updates
| key | Category | Values | Notes | Since GEP Ver. |
|---|---|---|---|---|
| player_info | me | ID of the local player. | See notes | 148.0 |
player_info note
Data Example:
{"info":{"me":{"player_info":{"user_num": 144222} }},"feature":"me"}
match_info
Info Updates
| key | Category | Values | Notes | Since GEP Ver. |
|---|---|---|---|---|
| team | match_info | ID of the team player in the match. | See notes | 148.0 |
| roster | match_info | All other player info is known to the local player. | See notes | 159.0 |
| match | match_info | ID of the match. | See notes | 159.0 |
| region | match_info | Starting location of all the users (if selected). | See notes | 159.0 |
team note
Data Example:
{"info":{"match_info":{"team":{"ally1" : 1003024, "ally2" : 144240}}},"feature":"me"}
This distinction of ally1 and ally2 will be used as a reference point in later events.
The team info update does not work for premade teams.
The user number will return 0 as a value if there are none.
For example, in solo mode, both ally1 and ally2 will return 0.
roster note
Data Example:
{"info":{"match_info" : {"roster" : [{"player_name" : "TestSubject1", "is_ally" : false, "player_character" : 12, "player_skin" : 1}]}},"feature":"me"}
"roster" includes information on all 18 players in the game.
"is_ally" will specify whether the subject is an ally or not.
This info will contain the local player itself.