|
|
Post by ntsheep on Oct 28, 2015 14:58:13 GMT -5
Just started a new game on Brutal using that nice code you gave us. On the second level of the Tutorial, after I pulled an Engineer, when I got 400 SP saved I went to get a Soldier but couldn't. It use to be that after you got the Engineer, the Soldier class was auto unlocked since it evens say you may want to deploy a second one. This happened on my tablet.
Toshiba ATC-7
Android 4.4.2
|
|
|
|
Post by fallen on Oct 28, 2015 16:07:42 GMT -5
ntsheep - sorry that you are having the problem. Anything else you can share? Tested here and it works.
|
|
|
|
Post by ntsheep on Oct 28, 2015 17:26:22 GMT -5
Nope, sorry. This actually happen to me once during the Alpha also I think. Never could figure out why. When I started a new game it didn't happen. I had started a new game on Normal yesterday, no problem. Had actually started a game on Brutal yesterday also and got that far. No problem. Today start a new game, problem. The only thing different was that code. When I beat the level I had to pay 10 RP to unlock that part of the Requisition Tree and get the Soldier in the next level.
|
|
|
|
Post by Cory Trese on Oct 28, 2015 17:45:38 GMT -5
This would be a total disaster for players -- we'd be getting hundreds of reports since this is pretty much a "game over" type event.
Is this on an Android? Maybe an OS bug?
|
|
|
|
Post by ntsheep on Oct 28, 2015 18:14:07 GMT -5
Yeah it's on Android, just started another game on Ironman and the same thing has happened. Used the code, played first level, started second level. Waited 6 turns and pulled out Engineer. Went to Recruit section again, and only Engineer is showing. No Soldier. If I could, I'd send you the save game now but my tablet isn't rooted so I can get into that section of the memory.
|
|
|
|
Post by fallen on Oct 28, 2015 18:29:45 GMT -5
Yeah it's on Android, just started another game on Ironman and the same thing has happened. Used the code, played first level, started second level. Waited 6 turns and pulled out Engineer. Went to Recruit section again, and only Engineer is showing. No Soldier. If I could, I'd send you the save game now but my tablet isn't rooted so I can get into that section of the memory. Ok, thanks for the info. Will try a few more times here, still can't reproduce it even with the code  |
|
|
|
Post by ntsheep on Oct 28, 2015 18:31:45 GMT -5
I'm digging as hard as I can right now myself. Starting new games over and over trying different things. As your new motto goes, suffer no bugs to live  |
|
|
|
Post by ntsheep on Oct 28, 2015 18:38:59 GMT -5
Ok, just got another game going without using the code and Soldier shows up. I'm sure what it is on my end yet, but using that code and equipping that gear seems to be causing something.
|
|
|
|
Post by Cory Trese on Oct 28, 2015 18:42:35 GMT -5
Good to know. Maybe it is a bug that's specific to that device and version of Android ... and combined with the code?
I guess just try playing without the code. I like playing with the code on my Android, but if it causes you problems maybe skip it.
|
|
|
|
Post by ntsheep on Oct 28, 2015 18:49:03 GMT -5
Well the only problem is that I then have to spend 10 RP to unlock that after I beat the level. Trying to see how I might be able to get into the deep system files on my tablet without rooting it. Going to try one of my Linux disks. What am I looking for exactly on files I would need to send you if I can get them.
|
|
|
|
Post by Cory Trese on Oct 28, 2015 19:01:24 GMT -5
Sorry man, maybe we shouldn't have sent out that code. We tested it like 20 times each, twice on each difficulty but maybe sending it was a mistake.
Probably just skip it if it doesn't work on your device.
|
|
|
|
Post by ntsheep on Oct 28, 2015 19:08:52 GMT -5
Don't feel bad Cory. I'm not mad or anything. The code is working in the fact that I get those Relic weapons and gear and can use them. I'm not sure why it's causing a problem but at least we've now traced it enough to know it's a device related issue. I want to help solve it. I've got no problem trying to squash a bug  |
|
|
|
Post by Cory Trese on Oct 28, 2015 19:13:09 GMT -5
Maybe the next build will fix it. I'll keep testing and hoping that it starts working on your device.
|
|
|
|
Post by Cory Trese on Oct 28, 2015 20:36:28 GMT -5
Suffer no bug to live. I have found the issue on Android. We'll patch tonight.
So sorry
|
|
|
|
Post by ntsheep on Oct 28, 2015 20:55:42 GMT -5
This is why I love you guys. I don't think even the "Big Game Companies" can fix a bug in one day. There's no need to say sorry.
|
|
