Skylab Upgrade Bug

Discussion in 'General Archive' started by ¤»ĐЯΣΔΜ†ÐΣМΦИ«¤SLK, Mar 11, 2015.

Dear forum reader,

if you’d like to actively participate on the forum by joining discussions or starting your own threads or topics, please log into the game first. If you do not have a game account, you will need to register for one. We look forward to your next visit! CLICK HERE
Thread Status:
Not open for further replies.
  1. Small issue, but still figured i'd point it out. The other day i was doing upgrades on a ship i have on another server, USA East 3.
    During the upgrade process of things, i kept getting an error message, but everything always worked. I also noticed the Prometium having less in storage then the others.. So tonight i noticed why.
    First off: Notice how much it takes for upgrades. See how much is in storage.
    [​IMG]
    Next: You get the little error.
    [​IMG]
    Finally: You see what the error is, and what's going on...
    [​IMG]
    I'm sure you can all see from this. It is only taking from the Prometium.

    User ID: 161136199
     
  2. DosEquis

    DosEquis User

    I have seen the exact same thing for a week or so.
     
  3. I have had this issue also, on GA1 server. Its not a massive problem as you still need to wait for the resource to collect, but it is a bit annoying.
     
  4. Ddraig

    Ddraig bp_phrase_Forum_General

    Hi there ¤»ĐЯΣΔΜ†ÐΣМΦИ«¤SLK,

    I believe that this issue has been fixed as of an update today, i have checked myself and everything seems to be in working order again and the correct amount of ores are being deduced. I hope that with your next upgrade, that this is true for you also.

    ~Ddraig
     
  5. I'll find out when i log into that account tomorrow morning to do more upgrades and let you know. Too tired for that right now, haven't slept in 24 hours lol.
     
  6. Doing upgrades right now, it's still doing the same thing.
     
  7. Ddraig

    Ddraig bp_phrase_Forum_General

    Hi ¤»ĐЯΣΔΜ†ÐΣМΦИ«¤SLK,

    Ah, i think i may have had a brain fart there. I checked the issue on GB1 which is currently testing a new update, therefore it was possible that the new update contained the fix to this issue.

    However i did just try to upgrade something on US4 and everything seemed to deduce correctly, therefore it is possible that the issue has now been fixed across all servers. If this is not the case then please post again and i will pass the information on further.

    ~Ddraig
     
  8. Seems to be back in working order Ddraig, you can close.
     
Thread Status:
Not open for further replies.