Bad plays list - things to improve

[AutomaticCoding]

It is beta, but still they are lying to customers or at least mislead them into buying a product that is not stable at all.

Also the whole page says nothing about this being beta phase - Hearthbuddy - The Bot for Hearthstone
Either I am blind or it is nowhere stated that this is beta. It also isn't stated anywhere on checkout - you do not get any warring at all that you are buying beta software in price of full product. That's just lying. It's probably the reason why they are not selling it in Germany - in fear of law suit or anything.

I am giving it some time but they need to push it to a usable level in next week.

The Buddy Team offer a one week no-questions asked refund policy, just so you know, so, if you really think they lied to you, I'd take them up on that offer.

Other than that, the only issue I see here is a slight stability issue at your end (And poor logic), don't get me wrong, it's not your fault, but, it is something you're going to have to live with until it can be addressed, it's not a fundamental issue in the code, as, the bot works amazingly for me (Left it on and got 30 wins over the period of a day, for my 100 gold reward, not a single crash, ~ 60 games in total).

 

[bigboy54]

i havent crashed yet either over 20 games so far

 

[Fibula]

The Buddy Team offer a one week no-questions asked refund policy, just so you know, so, if you really think they lied to you, I'd take them up on that offer.

I'm sure they do. Not that it matter at all I am sure they would give a refund without any problems at this point. It's just unfair and I am quite sure also illegal in EU to mislead your customer into buying a beta product without notifying him about that.

Other than that, the only issue I see here is a slight stability issue at your end

Crashing at every mulligan is a "slight" stability issue? My end? From what I see on support forums it's not just "my" end - it's many people "ends".

the bot works amazingly for me (Left it on and got 30 wins over the period of a day, for my 100 gold reward, not a single crash, ~ 60 games in total).

Have you done it on release .17? Because that's the one I had problems with. It's unfair to quote a guy on an old version and claim it's working for you when you'r using updated one Today I found out that there was update, now I have .22 currently checking it out. At this point it crashed only 2 times out of 5 mulligans. We'll see how it goes

 

[AutomaticCoding]

Crashing at every mulligan is a "slight" stability issue? My end? From what I see on support forums it's not just "my" end - it's many people "ends".

Yes. It's a slight issue, it doesn't effect everyone and it's in beta software, I never said it was great, but, it's what I'd consider slight. 'Many people' are just as good as saying your end, you all have something in common, maybe you're not using the English Hearthstone client, or, not using a x64 operating system, or, using a slightly newer version of .net that Hearthbuddy crashes on. It's beta software, I can't tell you it's not annoying, as, it must be, but, it's still something unique to you(r group).

Have you done it on release .17? Because that's the one I had problems with. It's unfair to quote a guy on an old version and claim it's working for you when you'r using updated one Today I found out that there was update, now I have .22 currently checking it out. At this point it crashed only 2 times out of 5 mulligans. We'll see how it goes

I've used all of these versions extensively with a grand total of three crashes, all three of which occurred when I was either starting, or, stopping, the bot:-

On 0.1.175.22, I'm currently on the eight hour mark without touching it, 50 total games, 26 wins, 24 losses:-

I got something similar on 0.1.159.17, however.

 

[hankerspace]

Actually, game localization and kind of OS (x64, x86...) has no influence on bot crashes or issues.

The only crash reason can be a reallllly slow computer : if your game loading (once game found in queue to the mulligan display) take more than 30secs, some behaviors can be unexpected...

If its your case, just tell us, maybe we can add a "slow computers" checkbox to handle and manage such behaviors...

And actually, a low-memory virtual machine can have the same issues...

 

[zuche]

Actually, game localization and kind of OS (x64, x86...) has no influence on bot crashes or issues.

The only crash reason can be a reallllly slow computer : if your game loading (once game found in queue to the mulligan display) take more than 30secs, some behaviors can be unexpected...

If its your case, just tell us, maybe we can add a "slow computers" checkbox to handle and manage such behaviors...

And actually, a low-memory virtual machine can have the same issues...

My computer is not slow but who knows, may be it will help. Also Im using mine main pc so no problems with low memory, so dunno why its happening

 

[Fibula]

AutomaticCoding - we have different idea of what "slight" issue is. What if it's the other way around - maybe it's you and few others that are "special" and their bot actually works? May be it's something in your spec and settings.

Actually, game localization and kind of OS (x64, x86...) has no influence on bot crashes or issues.

The only crash reason can be a reallllly slow computer : if your game loading (once game found in queue to the mulligan display) take more than 30secs, some behaviors can be unexpected...

If its your case, just tell us, maybe we can add a "slow computers" checkbox to handle and manage such behaviors...

And actually, a low-memory virtual machine can have the same issues...

It's not slow nor is it top tier. It's just regular ;p I also thought about that waiting time but I failed to see any connection between that. I also played with resolution and details level to see if it will help - nothing changed. If it's easy to add that "slow" option then you should add it, especially for VM uses. If it wont solve the problem it will at least tell you something. Also it's a nice feature. Still your Bot of Stone is working without any problems for hours and only crashes from time to time. I know it's different injection method, etc. I just wanted to let you know.

 

[DaSoul]

I've run into so many problems with this bot:

• Hunter's Mark locking out the game for both players when there is no enemy minion to target, the timer runs out but opponent cannot play anything as the target for it is still present in board.
• Abused sergeant and others being played then returned constantly, if that doesn't alarm people to detecting a bot, I don't know what will.
• Bot will play a charge minion but not use the charge upon placement.
• Update: Hero will not attack with equipped weapons

.

There are constant other logic issues here that aren't even near advanced logic that I'm a bit tired to recall exactly at this hour, will edit as I come across, I understand that logic will be terrible at the start but this bot is currently unplayable unless you sacrifice a lot of game winning cards due to so many restrictions to which cards actually work. Its definately alpha at best and unsure whether the sales value for such a rough release should be marked along the price of the other buddy releases.

I'm not being funny but the early version release of Bot of Stone played more cleanly than this.

Dude seriously...


Nobody, absolutely nobody forced you to buy a bot that IS NOT finished. Seriously what the **** do you expect?

Software in the beta phase will generally have many more bugs in it than completed software, as well as speed/performance issues and may still cause crashes or data loss.

Either you don't know what a beta is, then it is your fault buying something you don't know what it means/is or you have some serious big understanding problems what a beta version is.

And seriously complaining about ~20€ you paid for a lifetime product... ridiculous.


You know how i see this? With this pre-sell we support them, we help them getting new developers paid(if needed) for faster or more qualified work(4-eyes principle).


Some people these days ...