Hey all, we are aware of this issue and are looking into it right now. I don't have any info to share at the moment, but stay tuned!
Can't anyone in this company do anything right? How many months going on years does it take to get people to actually do their job right. they're in year 7 of raking in the dough, so they've done their job for their parent company. This all is far more entertaining than the actual game at this point.
Can't anyone in this company do anything right? How many months going on years does it take to get people to actually do their job right.
Kabam really needs to follow some code deployment SOPs.Code versioning , checkin , checkout, Unit testing ,Integration Testing , Regression testing.At this juncture they should do parallel testing between old version and new version in test environment.
@Kabam Miike Doesn't seem like this is an isolated issue.There's nothing in the release notes about intended changes to the inputs in this release, but it seems that several of us who have been unaffected are now having a lot of issues.Could you check with the team to see if something slipped in that could be causing this? ....and ripped out in a hot fix? There's never anything in the release notes about input changes. It's just a effect of them advancing the game. Some piece of software they use got updated somewhere and is now effecting people who weren't previously before. I.E.. a bug. It's not an easy fix like you're making it seem. Just shut up for once
@Kabam Miike Doesn't seem like this is an isolated issue.There's nothing in the release notes about intended changes to the inputs in this release, but it seems that several of us who have been unaffected are now having a lot of issues.Could you check with the team to see if something slipped in that could be causing this? ....and ripped out in a hot fix? There's never anything in the release notes about input changes. It's just a effect of them advancing the game. Some piece of software they use got updated somewhere and is now effecting people who weren't previously before. I.E.. a bug. It's not an easy fix like you're making it seem.
@Kabam Miike Doesn't seem like this is an isolated issue.There's nothing in the release notes about intended changes to the inputs in this release, but it seems that several of us who have been unaffected are now having a lot of issues.Could you check with the team to see if something slipped in that could be causing this? ....and ripped out in a hot fix?