|
Post by Officer Genious on Sept 23, 2014 15:28:53 GMT -5
I explored an anomaly and saw that I could get 100-odd research. I decided to push for more.
Five plus turns later, I never got a notification if it failed or what, but I had crap to do and moved my Explorer off, who apparently wasn't doing anything at the anamoly for the turn as I didn't seem to interrupt anything.
So... Is there a message that should come up should pushing for resources fail? Does it matter that I changed to a more intensive research project as soon as I pushes the explorers to find more stuff?
Think there's a bug somewhere...
|
|
|
Post by slayernz on Sept 23, 2014 23:47:37 GMT -5
I thinks I found your problem Oh wait ... it wasn't a hardware problem ...
|
|
|
Post by fallen on Sept 24, 2014 0:19:53 GMT -5
Officer Genious - can you please explain the issue in a 1, 2, 3 format? I am not sure that I can piece together what you are reporting accuractely.
|
|
|
Post by Officer Genious on Sept 24, 2014 6:12:05 GMT -5
Officer Genious - can you please explain the issue in a 1, 2, 3 format? I am not sure that I can piece together what you are reporting accuractely. 1: Explore Anamoly 2: On the following turn, an explorer event says I can greatly accelerate a research project or push for more. 3: I push for more and immediately change my current research project to one that's more RP intensive. 4: A few (maybe 5 or so) turns pass with nothing else coming from the Explorer. 5: Tired of waiting and suspecting something went wrong, I moved the Explorer. No notifications pop up of an interrupted Exploration. Did my Explorers fail to get more RP and was I supposed to be notified?
|
|
|
Post by fallen on Sept 24, 2014 9:20:14 GMT -5
Thank you, I have added #4X-2686 to look into this. For future bug reports, please consider that the new format (1,2,3) is about 100x more actionable for Cory and I to isolate and fix a bug. It is hard to be clarity when reporting bugs Otherwise, we end up chasing the wrong thing.
|
|
|
Post by Cory Trese on Sept 26, 2014 22:08:01 GMT -5
I figured it out. Fixed in next.
|
|