'Save Table' issues
Paxton
Member Posts: 89
Hi there!
I have a save table behaviour... which is problematic. By default, row 1 is 'true'... row 2 is 'false' - row 2 turns to 'true' if LVL 1 is completed. There is a save table behaviour to save this.
However, if exit the game and launch it again, all table values will be returned to "false" - even the first row, which is "true" by default and there is absolutely no rule in the game giving it the option to be turned to 'false'.
??? I am EXTREMELY confused.
Comments
I forgot to mention: this worked properly when I last worked on the game last month, so it got buggy after the iOS 8 GS update.
Are you loading the table cell values to each attribute when you start the game?
@Rabid Parrot There is no "Load table" attribute - there is only a Load Attribute behaviour working in conjunction with the Save Attribute one.... Should there be something like that?
In the rules there is a table cell function that you use to retrieve the value from a table, are you using this to set the values for your actor? That is what @Rabid Parrot Is referring to. Also what rules do you have for saving the table data?
@Back2Code After you finish level1, row2 is set to 'true' and there is a "Save Table" behaviour - that's it. It worked flawlessly before the iOS8 update...
I am not using "Save Attribute"/"Load Attribute", and not retrieving anything with "table cell function".
The load / save attribute behaviour is for storing variables without tables.
If you are not using the table cell function how do you know if level 1 etc is unlocked? You have to read it from the table you are storing it to.
If it worked before I am guessing you were using game attributes not table values? But unless save and load attribute was used it would never remember after a game reset.
@paxton are you using GS version 12.4? This is a bug for that version that I recently had the same problem with, my tables were being erased when I reloaded a game. The release candidate version 12.6 fixes this. Try it out. http://gamesalad.com/download/releases
www.rossmanbrosgames.com
@Back2Code Saving tables works differently to saving attributes. If you save an attribute, you have to load it when you re-launch the game. On the other hand, if you use "Save Table", it saves the table for good - it loads by default to the last save point, without any load behaviours. Every save to a table overwrites the previous save. To reset the table, you have to delete the game from your device and re-install it.
When it worked, it worked with "save tables". I know when rows are "false" or "true" because each row corresponds to a level. When I can access level 1, row 1 must be "true". So, I know that my tables get messed up when re-launching with all values being defaulted to "false", because every single level is locked. This is exactly why it makes no sense, because level 1 should ALWAYS be unlocked (i.e. row1 is always be "true") - there is not a single piece of code giving it the possibility of becoming locked, and yet it does get locked when re-launching the app. So my tables MUST be somehow deleted by a glitch.
@RossmanBrothersGames Yes! That's the exact version that I am using. I was suspecting this was a bug, since it worked before and now it doesn't - using the exact same rules. And the logic of the code is 100% correct, I think I spent half the night analysing every single rule related to these tables.
Do you know if this release candidate is safe for using? I remember loads of cases when users downloading release candidates and corrupting their gameproj files, or not being able to submit to apple (i.e. binaries would get rejected). Thanks!
I know they released version 12.4 as stable then realized this bug, but a lot of people switched to it obviously, that is what I am currently running since I just hit update when the option came. So hopefully there are no serious file corrupting issues with that I haven't heard of any, would hate to go back to an earlier build. I know the RC makes you save it under a different extension so it doesn't ruin the old file. I have started using the RC since my game builds work fine off of it and they don't under 12.4
www.rossmanbrosgames.com
@RossmanBrothersGames Thanks! I will personally just continue with other things on my "to do" list for this game, using 12.4. Perhaps by release date, 12.6 will become stable.
At least now I can stop obsessing about the code thinking that there must be something wrong in it and not knowing what
0.12.6 wont corrupt your file. I think what you have heard and understood are two different things.
If you was currently using 0.11.1.11 and then opened your file in 0.12.6 and saved it, It would add a change to the file that makes it not able to open in 0.11.1.11. This is perfectly normal and deliberate, not a bug or corruption. Its design to protect your files as each major update (0.10 to 0.11 to 0.12) add features that wont work in previous versions.
That said, if you are using 0.11.1.11 I would suggest staying on this version until a stable release is released. If however you are using 0.12.4 or 0.12.5, upgrading to 0.12.6 will fix some of the many bugs in these releases.
@Paxton my apologies it sounded like you weren't using the table cell function to read the table value which is saved by the save table behaviour.
I submitted my app to the store with 12.5 after a lot of testing on ios, 12.6 is more stable and I will be releasing an update from 12.6 when it is finally reviewed by apple (14 days today
@Back2Code No worries. On another note, I know that the waiting times have been horrendous lately, probably because many developers submit updates for iOS8 and iPhone 6 and 6+. I had to wait 12 days only to get an app rejected because I ticked the wrong box before submitting
(the ad identifier... I thought that iAds use it, and ticked that I have that. I didn't.)
@gingagaming Thanks for clearing things up. I simply remembered people on the forums complaining that when using RCs they corrupted their files, it was enough for me to be cautious.
I thought iAds did as well, I have submitted another app with just iAds and it was approved with the ad identifier ticked, I hope this gets approved as have it ticked for iAds and chart boost ads.
Anyway 12.6 rc works well so good luck.
The first version of my app was accepted as well, with the ad identifier ticked. The second version had the exact same boxes ticked, and it got rejected. I guess it's down to luck. I looked at the T&Cs, and indeed they do mention that iAds do not use the identifier. Odd.
Chartboost - if that's another ad provider, they DO use the ad identifier! Only iAds do not use it, the others do.
Sooo.. I just encountered some sort of saving issue in an app I just updated (wasn't found by Apple...)
Should I switch back to saving and load attributes instead of dealing with tables for now?
I'm on GS 0.12.4.... Doesn't show any updates. Will 0.12.6 fix these table issues?
@TomCoffee
It may be worth checking recent developments and discussion to see what has transpired in:
http://forums.gamesalad.com/discussion/73211/release-candidate-0-12-8-is-available#latest
and then, more importantly, this for the latest:
http://forums.gamesalad.com/discussion/73392/release-candidate-0-12-9-is-available#latest