When I first start my computer and play a hearthstone game, the match_type is nothing, but the second game I play, the match_type gets populated, do you know why this might be?
Here is a console log from the events that take place while the app is running:
As you can see, after the first game, the match_type is not found, but then without restarting or changing anything, the second game yield the correct match_type.
Itâs simply possible that when launching the HS client, all the relevant data like that is emptied as ânullâ and gets filled when entering a match.
Nonetheless, we had the match type on my first match after launch.
On the first game, it doesnât seem to look for match_type until the game is ended, but on the second game, it gives me the type before the match_start event is triggered.
I have also downloaded your hearthstone events sample app and it doesnât work on their either.
Iâll give you a plugin that will help us debug this in case this is 100% reproducible on your machine. Perhaps that way we can understand better how to handle this.
Open âOverwolf Games Events Providerâ via the UID under it.
Go to plugins/64 folder and paste the dll there - overwriting the current one.
Once you use this one and the situation still persists - make sure you go to Overwolf log folder (AppData\Local\Overwolf\Log), there you will find a âgep_plugin.logâ file which you need to send over to us.
Hey @ge0r9e,
I went over the logs you sent and it looks like that the Hearthstone power.log file was missing in one of the matches (this is why we couldnât detect the current âmatch_typeâ)
The best way for you to help us would be for you to find out an exact scenario that makes this happen.
Meaning if you changed anything with the Hearthstone folder / I donât know, anything that might affect the power.log in some way.
Itâs hard for us to do anything because itâs a file thatâs created by HS itself.
Perhaps a good place to start would be to re-install HS and see if this continues to happen for you.