Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • C core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 81
    • Issues 81
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • dulst
  • core
  • Issues
  • #106

Closed
Open
Created Nov 03, 2023 by Andrei@gibbit

Saving still overwrites old data even inside namespaces

Been testing the namespace saving for 2 hours now and it still overwrites data, it is better now that it was before because we do not have to worry about the data outside the namespace we are saving to but it's still a really bad issue. I'll link the game i've used for testing this here and a quick example.

Link to the testing game

These are the relevant rulecards.

gameMode

Story: Manage Data is the one with the save code. It has a reset property that when set to 1 will set the story namespace to null and it will create a variable outside the story namespace to check whether it's deleted or not, so far i haven't seen it be deleted.

afterReset

This is how it looks after first reset, both values are in the save property of the player and are saved under the story namespace.

after_save

This is player data after saving and loading, player save data is empty and player data is as it's supposed to be nothing missing, so far so good.

Now if i say increment battle by 1 (i set ending turn to increment) i get this.

saving

And after reloading.

loaded

After reloading chapter value is gone and battle is saved as it should with the new value.

Edited Nov 03, 2023 by Andrei
Assignee
Assign to
Time tracking