This is your community for everything related to Star Citizen - an up and coming epic space sim MMO being developed by Chris Roberts and Cloud Imperium Games.
All c/starcitizen content must be related to Star Citizen. Content with an indirect relationship must attempt to provide meaningful discussion of Star Citizen.
Be respectful. No personal insults/bashing. Don’t be a dick.
Follow these posting restrictions:
Official Links:
Other Links:
Dev Tracker (Only works with Spectrum at the moment)
Starchives (Query/Search all closed captions throughout all official videos)
Loadout Tools:
Industrial Tools:
This is an unofficial Star Citizen fansite, not affiliated with the Cloud Imperium group of companies. All content on this site not authored by its host or users are property of their respective owners.
I know everyone has gotten comfortable with their favorite armor set, but you might want to swap out for a generic set, or log off naked after every session until the release goes live.
More patch notes here: https://robertsspaceindustries.com/spectrum/community/SC/forum/190048/thread/star-citizen-alpha-4-1-1-ptu-patch-notes-8/7921782
But also... do they not know how to do migration scripts? Is their persistence changing so drastically that they can't even translate "items equipped" to "items in storage"? WTF.
I'm sure there's a reasonable explanation for skipping a seemingly small step, but I'm worried it's closer to "that won't make us money" than "it's technically difficult."
Message in the OP mentions they did manage to fix it in a future build so I don't think it's either of those explanations. I'm just curious what blocks them from merging the fix into 4.1.1 release.
I doubt there's a "fix" so much as a "we're not changing the thing again." This is a classic symptom of a poor data migration: having something that works be moved/changed and lose state but then work for the future.
I'm sure the persistence layer is much more complex than a flat database table, but it's still just item IDs and character slots.
It's already been fixed lol this message aged like milk
That's also possible, I just try not to come up with my own explanations unless there's evidence to do that. They say it's fixed and since I have no access to their codebase I have no reason to think otherwise.