|
|
Post by angrytemplar on Jan 20, 2016 22:33:32 GMT -5
Samsung note edge is my phone. Along when I quit and start up the same game, sometimes the colony whips appear outside a different prime world.
|
|
|
|
Post by Cory Trese on Jan 20, 2016 22:36:43 GMT -5
Grab the latest update, that should be fixed. I'm afraid you'll have to start a new game, however, if you've got that bug.
Sorry. Let me know if you are able to continue with v2.5.7 which was released about an hour ago
|
|
|
|
Post by angrytemplar on Jan 20, 2016 22:38:22 GMT -5
Wow! Sorry for bad grammar and thanks for this awesome game. I love this and Star Traders!
|
|
|
|
Post by Cory Trese on Jan 20, 2016 22:42:03 GMT -5
Don't be sorry ... I'm glad you're enjoying it!
|
|
|
|
Post by angrytemplar on Jan 20, 2016 22:48:24 GMT -5
Err. No idea how to get this update. Stuck at 2.5.5 Should have mentioned I have the Elite version  |
|
|
|
Post by fallen on Jan 20, 2016 23:31:35 GMT -5
Err. No idea how to get this update. Stuck at 2.5.5 Should have mentioned I have the Elite version Just keep checking back with your market (Google Play, etc) and watch for updates available! |
|
|
|
Post by someguy on Jan 21, 2016 6:45:49 GMT -5
I got this game for kindle and there is no update for this. Also this bug lets you build as many colony ships as you want but as soon as one colonizes a star, any other ones that are built after will not have any buttons on the right, such as any attack or colonize for the colony. The strange thing is that any colony ships that were built before a colony ship colonizes a star will still be able to colonize other stars. This bug only affects colony ships built after another star has been colonized buy another colony ship beyond any original starting colony ships.
I have only played the tutorial mission, so I don't know if this is in other scenarios other than the into scenario.
|
|
|
|
Post by someguy on Jan 21, 2016 6:54:25 GMT -5
I just checked the version that is installed and it is v 2.5.7 that I have installed on my kindle.
|
|
|
|
Post by alvazir on Jan 21, 2016 9:39:29 GMT -5
I just checked the version that is installed and it is v 2.5.7 that I have installed on my kindle. You should probably start a new game if you started previous game on 2.5.5. I had this bug fixed after updating to 2.5.7 and starting a new game. Edit: quote from this thread - startradersrpg.proboards.com/thread/13123/colony-ships-colonize?page=1&scrollTo=150466:chrisc - thanks for the report. This bug is fixed in the release that just went out tonight, 2.5.7 You'll need to get the new release and start a new game. Any game started on the 2.5.5 release will exhibit these bugs, very sorry about that! |
|
|
|
Post by tenbsmith on Jan 21, 2016 10:00:25 GMT -5
angrytemplar, updates move through the approval process of the different platforms at different rates. For example, Google Play is faster than Apple or Amazon. Someguy, it seems very likely that you started the game in version 2.5.5 and this lead to the weird colony ship behavior. That behavior should be fixed if you start a new game in 2.5.7., but may persist for old games.
|
|
|
|
Post by fallen on Jan 21, 2016 11:04:17 GMT -5
I just checked the version that is installed and it is v 2.5.7 that I have installed on my kindle. Sorry, as tenbsmith was pointing out, updates on Amazon are slower. If you now have 2.5.7, you'll need to start a new game. Saves started under 2.5.5 won't recover from this issue. |
|
