|
|
Post by elwoodps on Jul 28, 2015 18:56:56 GMT -5
I built a handful of Carriers (both Fuel and Repair) in my current game, equipped with Cadar's "Critical Strike" as their primary training (Secondary=Sector Scan 3, Specialist=Multi-Repair 1 or Multi-Refuel 1). Unfortunately, after updating to v2.3.9, none of them have a Critical Strike button anymore (they've been de-fanged, so to speak).  But worse, every time I tap the Load Out button on one of these ships, it crashes the game.  Is there any way I can downgrade back to v2.3.7 until this is resolved? |
|
|
|
Post by fallen on Jul 28, 2015 19:07:53 GMT -5
Fixed for next.
|
|
|
|
Post by elwoodps on Jul 28, 2015 19:19:03 GMT -5
Thanks fallen, that's gotta be the fastest fix ever!  Not to sound ungrateful, but is there any way I can downgrade back to v2.3.7 in the mean time? |
|
|
|
Post by fallen on Jul 28, 2015 19:24:31 GMT -5
Nope  |
|
|
|
Post by elwoodps on Jul 28, 2015 20:02:06 GMT -5
 Oh, well...... Guess I'll be guinea-pigging it with toothless carriers for a while.
|
|
|
|
Post by dashit on Jul 28, 2015 20:31:47 GMT -5
Oh, well...... Guess I'll be guinea-pigging it with toothless carriers for a while. I have the same issue. Have you tried building new ships to see if they are affected? |
|
|
|
Post by Cory Trese on Jul 28, 2015 21:12:46 GMT -5
Just uploading the fix now. Sorry everyone!
|
|
|
|
Post by elwoodps on Jul 29, 2015 6:41:26 GMT -5
Just uploading the fix now. Sorry everyone! As always, Trese Brothers lives up to their motto! Question: Will the fix have a new version number? The play store is still showing v2.3.9 as the latest. |
|
|
|
Post by elwoodps on Jul 29, 2015 6:45:57 GMT -5
Oh, well...... Guess I'll be guinea-pigging it with toothless carriers for a while. I have the same issue. Have you tried building new ships to see if they are affected? No not yet, and Cory Trese's last post suggests that we shouldn't have to. |
|
|
|
Post by fallen on Jul 29, 2015 7:40:41 GMT -5
v2.3.11
|
|
|
|
Post by elwoodps on Jul 29, 2015 17:58:55 GMT -5
v2.3.11 is now the latest in the Google Play store, and it does fix the problem. Thanks again guys! |
|
Oh, well...... 
