Boba execute messing up everything
So boba executed 86 and rey killed 88. I tried to revive 88 with je on the next turn but he didn't come back. My best guess is rng chose 86 for the revive and bobas block made it not work. Any...
Forum Discussion
Oh they definitely miss things all the time and I think they apply what people see as "AI cheating" sometimes to cover some things up. I don't think you can separate the two in some instances with what people see as a bug and balancing though. They aren't very good about wording on things either which doesn't help the problems.
It's very difficult to keep everyone happy in a game like this and it's very difficult to keep a somewhat sane balance. I'm sure the dev team run into unrealistic deadlines which make things worse... I'm all too familiar with that. Sometimes I wonder if they would eventually blow things up, homogenize the toons and let the players tweak them as they wished.
I would still say that people shouldn't look at another ability's functionality as a comparison. You have to take balance and intent into consideration on any of this. They probably saw the assist issue as "silly" because they realized immediately the more far reaching affect it had. Execute/revive may very well be unintended as well but it seems reasonable to me that execute would work as it is due to the reduced scope and intent. It may be a bug...maybe not. I think for a toon/ability with such a specific counter it's reasonable for this to be declared WAI.
They really need to get some better unit testing in place. It seems like they rely on the player base too much to identify things... or QA people who may not even play the game and are looking at test scripts which could just as easily be "off" or incomplete. As a developer myself, I know it's not an easy job sometimes due to circumstance. Good game though despite the obvious paywalls and money-based decision making. Happy gaming!
It's very difficult to keep everyone happy in a game like this and it's very difficult to keep a somewhat sane balance. I'm sure the dev team run into unrealistic deadlines which make things worse... I'm all too familiar with that. Sometimes I wonder if they would eventually blow things up, homogenize the toons and let the players tweak them as they wished.
I would still say that people shouldn't look at another ability's functionality as a comparison. You have to take balance and intent into consideration on any of this. They probably saw the assist issue as "silly" because they realized immediately the more far reaching affect it had. Execute/revive may very well be unintended as well but it seems reasonable to me that execute would work as it is due to the reduced scope and intent. It may be a bug...maybe not. I think for a toon/ability with such a specific counter it's reasonable for this to be declared WAI.
They really need to get some better unit testing in place. It seems like they rely on the player base too much to identify things... or QA people who may not even play the game and are looking at test scripts which could just as easily be "off" or incomplete. As a developer myself, I know it's not an easy job sometimes due to circumstance. Good game though despite the obvious paywalls and money-based decision making. Happy gaming!
