• Essence_of_Meh@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    7 days ago

    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.

    • Infinite@lemmy.zip
      link
      fedilink
      English
      arrow-up
      3
      ·
      7 days ago

      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.

      • Essence_of_Meh@lemmy.world
        link
        fedilink
        arrow-up
        3
        ·
        7 days 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.