4 ms·

My partner spoke to some who did and from what I understand there was no resolution. We could maybe have pushed for a refund but I had a bit of time pressure of

My partner spoke to some who did and from what I understand there was no resolution. We could maybe have pushed for a refund but I had a bit of time pressure of her leaving for a trip (and I wanted her to have this game for it). I'm gonna drop their support a link to my writeup, see what happens! Besides, I had a lot of fun playing with it. There were no doubt easier ways to do what I did but I enjoyed digging! :)

ziml77 5y ago
Since you've spelled it all out, I hope they actually take your fix and start shipping it. Not because I want them to benefit from unpaid labor, but because I want anyone else who buys the game to benefit from it without having to find your blog post. This sort of reverse engineering stuff certainly is fun though. As long as the software isn't heavily obfuscated that is. Before WoW died because of the Blizzard harassment investigation, I tried to reverse engineer Battle.net and the game to create an alternate launcher so I didn't have to see the ads in Battle.net. But both were obfuscated and had anti-debugging features. While I'm sure it would have been possible to figure out, it was too much for me so I eventually abandoned that. I love your write-up on your process. I've done a couple short explanations before of how patches I've released work, but your blog post is far more thorough and a great read.
- Slortibort 5y ago
  I hope so too. I could only imagine that they didn't know why this happened and/or didn't have the budget to investigate the problem. They kind of don't have any excuses now. If they've still got the original sources, it should be a 5 minute fix (rounded up to a day with testing and whatever corporate processes they follow). Nothing is uncrackable and it was that thought that kept me going with this. I can imagine that deliberately-obfuscated DRM like Battle.net would be a hell of a lot harder than this was though. Technically, it was all there for me to see from the start but I didn't know the way I should approach the problem. Finding that out was a big part of it. Cheers, I'm glad you enjoyed it. More people have said they liked it than I ever thought would, I'm kinda surprised.

ziml77 5y ago

Since you've spelled it all out, I hope they actually take your fix and start shipping it. Not because I want them to benefit from unpaid labor, but because I want anyone else who buys the game to benefit from it without having to find your blog post. This sort of reverse engineering stuff certainly is fun though. As long as the software isn't heavily obfuscated that is. Before WoW died because of the Blizzard harassment investigation, I tried to reverse engineer Battle.net and the game to create an alternate launcher so I didn't have to see the ads in Battle.net. But both were obfuscated and had anti-debugging features. While I'm sure it would have been possible to figure out, it was too much for me so I eventually abandoned that. I love your write-up on your process. I've done a couple short explanations before of how patches I've released work, but your blog post is far more thorough and a great read.

Slortibort 5y ago
I hope so too. I could only imagine that they didn't know why this happened and/or didn't have the budget to investigate the problem. They kind of don't have any excuses now. If they've still got the original sources, it should be a 5 minute fix (rounded up to a day with testing and whatever corporate processes they follow). Nothing is uncrackable and it was that thought that kept me going with this. I can imagine that deliberately-obfuscated DRM like Battle.net would be a hell of a lot harder than this was though. Technically, it was all there for me to see from the start but I didn't know the way I should approach the problem. Finding that out was a big part of it. Cheers, I'm glad you enjoyed it. More people have said they liked it than I ever thought would, I'm kinda surprised.