[fix]Searing Blaze:damage opponent without creatures in play

[FastEddie]

Describe the Bug:
Searing Blaze allows opponent to be damaged although opponent has no creatures. This ends in a deadlock.
Also there is no request/dialog box to target a creature after targeting the player.

Which card behaved improperly?
Searing Blaze

Which update are you using? (date, name)Which type? (duel, gauntlet, sealed deck)
Test Manalink 3.0 Build as of 01-Aug-2019 updated till Nullstone Gargoyle in commit 01e3541. Duel

What exactly should be the correct behavior/interaction?
Damaging the opponent should not be possible as long as opponent has no creatures in play.
After targeting the player a request/dialog box should open and ask to target a creature or cancel.

Are any other cards possibly affected by this bug?
No.

[Aswan jaguar]

Fix it doesn't load prompt for target creature in commit 12973fb3 so now you can cancel if target player doesn't have creatures in play.

[FastEddie]

Can you pls post a link to the Git repository? The search function is no help for 3 letter words and if I go through Google I end up with the Forge repository.

[Aswan jaguar]

Did this test update fix your windows 10 issue?
Which card are you trying to search for?
Try to search for that cards (name + Unsearchable) you might find it this way.

About git repository it is a private one that is hosted by Korath and only he can give you access to it and unfortunately he is not around the last few months.
Moreover the server for the past few months has issue and we can't connect to it so in fact the changes are committed only on my local repository and not pushed upstream.

[FastEddie]

Ok, that answers a couple of questions I had. So we have to wait for a new test version and I have to live with the bugs for the time being.

The test update fixed the Windows 10 issue, but now the drawcardlib.dll error occurs every time. I did two new installations from scratch but both didn't work (after starting magic.exe nothing happens and after 30 seconds or so I get an error message and have to close the program). Seems like my installation is thoroughly broken but it is not the installation itself causing the issue .