this post was submitted on 07 May 2025
27 points (100.0% liked)

Star Citizen

507 readers
2 users here now

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.


Rules

  1. All c/starcitizen content must be related to Star Citizen. Content with an indirect relationship must attempt to provide meaningful discussion of Star Citizen.

  2. Be respectful. No personal insults/bashing. Don’t be a dick.

  3. Follow these posting restrictions:


Useful links/tools/info

Official Links:

Other Links:

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.

founded 2 years ago
MODERATORS
 

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

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 2 months ago (1 children)

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."

[–] [email protected] 2 points 2 months ago (1 children)

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.

[–] [email protected] 3 points 2 months ago (2 children)

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.

[–] [email protected] 3 points 2 months ago

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.

[–] [email protected] 1 points 2 months ago

It's already been fixed lol this message aged like milk