Saved attributes/tables after updates to app

jiffwjiffw Member Posts: 42
edited June 2012 in Working with GS (Mac)
My game works in the following way. When a player installs the game and plays for the first time they start with 20 "coins". As they play the game they can gain more coins which gets saved to a table and an attribute, meaning when they return to the game they will have as many "coins" as they did when they stopped playing. What happens though when I release an update to the app? How can I ensure the player's "coin" value doesn't revert back to the starting 20 "coins"?

Best Answer

  • IsabelleKIsabelleK Posts: 2,807
    edited June 2012 Accepted Answer
    Thank you for your help. One more question, what if in version 1 i had the starting coins as 20, but then in the update increased the starting coins to 50. Would the 50 then overwrite the players saved coins or would the saved coins prevail?
    It depends on your rules - if you have a rule that loads player's coins, and overwrites the starting number (50) - it will work.

    It should look like this:

    Load Attribute game.Coins

    and

    Timer, after 0.5 seconds:
    Rule: if game.Coins<50 (this will check the loaded attribute);
    Then: change game.Coins to 50;
    Otherwise: do nothing.

Answers

  • IsabelleKIsabelleK Member, Sous Chef Posts: 2,807
    If you don't change this saved attribute while making an update (like change its name, remove it, or something like that) it will work as before, and players will have their saved coins.
  • jiffwjiffw Member Posts: 42
    Thank you for your help. One more question, what if in version 1 i had the starting coins as 20, but then in the update increased the starting coins to 50. Would the 50 then overwrite the players saved coins or would the saved coins prevail?
  • jiffwjiffw Member Posts: 42
    thanks for clarifying
Sign In or Register to comment.

© Vanilla Keystone Theme 2025