News PLEASE READ: Module storage and unique modules!

Status
Thread Closed: Not open for further replies.
Hi everyone,

We've come across an issue with the module storage that can affect CMDRs when unique modules are stacked onto a ship. Firstly, PLEASE DO NOT do this as the outcome is a Commander Data error. This will mean you'll be unable to load the Commander!

If you move a unique module from your storage (Shield Gen, D.Scanners, and others that you can only fit one of) into a ship that already has another module of that type in a different class slot, this is when the issue will occur. For example, moving a Class 7 Shield Generator from storage when the ship already has a Class 5.

If this is something that you've experienced and you're unable to access the game because of it, please contact our Support team with as much detail as you can provide so that they can resolve the issue for you. The dev team are working on a fix and we'll resolve this issue ASAP.
 
Indeed, what our Support team can do is remove the offending module and refund its value. This, however, means that the module - Engineers upgrade and all - is removed.

We ask that everyone tries to be careful when transferring modules from storage to the ship to avoid this being a problem. :)
 
Just for clarity. This only affects Optional modules that you can only fit one of. Not core modules, hardpoints and utilities?
 
looks like the answer is to ensure that the 'original' unique module needs to be a direct swap, ie if i have a class modified shield, and i want to put a class 7 from storage on, i need to ensure the class 5 shield is in the slot i want the class 7 to go into.
 
Is a fuel scoop a unique module? I don't remember ever attempting or failing to place one while another is already placed.
 
We can not possibly add more than 1 fuel scoop so yes it is Unique so may have this issue.
I did test trying to have 2 Scoops in Beta 7 and it did not allow it but also did not crash your CMDR file.
 
Last edited:
Hi everyone,

We've come across an issue with the module storage that can affect CMDRs when unique modules are stacked onto a ship. Firstly, PLEASE DO NOT do this as the outcome is a Commander Data error. This will mean you'll be unable to load the Commander!

If you move a unique module from your storage (Shield Gen, D.Scanners, and others that you can only fit one of) into a ship that already has another module of that type in a different class slot, this is when the issue will occur. For example, moving a Class 7 Shield Generator from storage when the ship already has a Class 5.

If this is something that you've experienced and you're unable to access the game because of it, please contact our Support team with as much detail as you can provide so that they can resolve the issue for you. The dev team are working on a fix and we'll resolve this issue ASAP.

st-tng_phantasms.jpg

Couldn't resist. Sorry.
 
"Of course the one thing from the update I'm excited about gets bugged," comment is commented. My update bingo card is off to a great start! ;) It'll get fixed GroundxZero, try flying some passengers while you wait.
 
We can not possibly add more than 1 fuel scoop so yes it is Unique so may have this issue.
I did test trying to have 2 Scoops in Beta 7 and it did not allow it but also did not crash your CMDR file.

Thank you
I haven't attempted to fit a second scoop on my ship so I should be okay as long as I don't do that. Hopefully this will be fixed very soon.
 
So can I move a power plant from my python to my Ana with no problem ?

NO.

Don't risk it. I'm posting this as widely as I can, but I had my Commander corrupted an hour ago by moving a shield to an empty Beluga. Nothing else except a few engineered Core Internals were loaded, and the Optional Internals were completely empty. The shield was the first thing I was going to load, but it immediately bricked my game.

It's possible the problem is Engineered Items are classed as Unique, or that having 2 uniques in storage is the actual issue, but I definitely didn't have 2 shields on the Beluga, as I'd sold everything off, stored modified things from other ships, and was just about to start moving them across.

DON'T USE THE STORAGE UNTIL THE ACTUAL ISSUE IS UNDERSTOOD AND FIXED. Stay safe, Commanders, and wish me luck getting my account back...
 
NO.

Don't risk it. I'm posting this as widely as I can, but I had my Commander corrupted an hour ago by moving a shield to an empty Beluga. Nothing else except a few engineered Core Internals were loaded, and the Optional Internals were completely empty. The shield was the first thing I was going to load, but it immediately bricked my game.

It's possible the problem is Engineered Items are classed as Unique, or that having 2 uniques in storage is the actual issue, but I definitely didn't have 2 shields on the Beluga, as I'd sold everything off, stored modified things from other ships, and was just about to start moving them across.

DON'T USE THE STORAGE UNTIL THE ACTUAL ISSUE IS UNDERSTOOD AND FIXED. Stay safe, Commanders, and wish me luck getting my account back...
Sorry, but i am not sure that what you say is 100% correct. Some player is already check this. And while his ship was really emty - he have no issue at all. Hope your problem will be fix soon cmdr :)
 
Indeed, what our Support team can do is remove the offending module and refund its value. This, however, means that the module - Engineers upgrade and all - is removed. ...

Instead of deleting the module Frontier Support should just move it back to storage.
 
Interesting. Surely Support will compensate us. This did not happen even in Beta 7 as it did not allow more than 1 Unique Item to be added.

Compensate? I thought "claim culture" applied to "flash for cash", "crash for cash", PPI, injury, legal and H&S legislation. Surely it doesn't need to expand to cover bugs in games?
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom