4 ms·
I have, to an extent. I've been working with Blizzard games for almost ten years (I worked on reverse engineering in WoW before), and Blizzard tends to be very
by scrollaway 12y ago
I have, to an extent. I've been working with Blizzard games for almost ten years (I worked on reverse engineering in WoW before), and Blizzard tends to be very cautious with this sort of projects.
In this case, it would be relatively easy to implement a server on top of Fireplace which would communicate with a slightly modified Hearthstone client. This would be a huge no-no for Blizzard and they would try their best to shut it down, so I'm not doing that.
You'll also note that the game files I am reusing in fireplace are actually in a separate repo (hearthstone-data submodule) so that I can take it down separately, should Blizzard request it.
Edit: Part of me also hopes that Team 5, the team behind Hearthstone, is a bit different. They have been incredibly close to the community, much closer than Blizzard has with other games, and I'm hoping that if issues arise, we can work them out peacefully.
- jzelinskie 12y ago>In this case, it would be relatively easy to implement a server on top of Fireplace which would communicate with a slightly modified Hearthstone client. This would be a huge no-no for Blizzard and they would try their best to shut it down, so I'm not doing that. Besides doing something like this, how else would you go about testing this kind of thing?
- scrollaway 12y agoBlack box testing, much like the Wine project does. You can see my battery of tests here: https://github.com/jleclanche/fireplace/blob/master/tests/test_main.py https://github.com/jleclanche/fireplace/blob/master/tests/te... Also, the game has excellent debug logs which I could always generate in Fireplace and compare the two or some such. And if all else fails, I can always peek at the Hearthstone protocol.