Save / Load attribute randomly stopped working.. I'm going crazy!

charliehgreen

Ok so randomly my Save and Load just completely stopped working and I know the code is done right because it was working fine and I was testing for over 5 months on my phone with it working.

I have a code on each enemy that basically says when hit points equal or fall below 0 change game.TotalScore to game.TotalScore+1. Then also theres a code that calls to save it game.TotalScore - Key TotalScore

So basically it will save the TotalScore

And on the loading screen I have an actor that loads everything for example;
Load Attribute
Key - TotalScore Att - game.TotalScore

And this worked FOREVER!!! every time I went to test my game, my score was always the same as when I left, so thats how I know the code work 100%

Last week I had to do a phone restore and wipe my iphone and I had to update X-code on my computer. Once I updated and re-installed the GS viewer on my phone. NOTHING would save and load. Could someone please help me figure this out.

I'm really frustrated!!!!

charliehgreen

Anyone?

gyroscope

Hi @charliehgreen I can understand your frustration, especially as the Save & Load behaviours were working before…

I'm not sure I can help though, except to say I wrote to GS Support about not being able to load game attributes… scene attributes Save & Load without any problem (don't know about self attributes) but as I say, any game attributes don't work. Unfortunately I didn't get any response that confirmed this as an actual problem/bug though…

So I don't know where that leaves us with saving and loading game attributes…

I guess that any future saving will have to be done via tables until the problem is sorted, though that doesn't help your/our immediate problem...

charliehgreen

@gyroscope Thanks!

I hope they will soon acknowledge this and do something about it. I really need this to work

KillerPenguinStudios

Hey @charliehgreen, out of curiosity, have you tried testing it on another device??? Just a thought!

BigDave

So i have a similar issue. I never tested it before I did save/load like in Tshirtbooths video.
So what i would suggest to test first is.

Solution attempt:
Type all "keys" new into all behaviors. Dont use the "e" expression editor. Use the text field.
One case of used expression editor could prevent all other load/save from working properly. As I experienced that one missing sound file can mess up all sound of the game too.

gyroscope

Hi @BigDave as much as your solution attempt is appreciated as a sign of help, it might muddy the waters concerning this particular problem: if you read the first post by @charliehgreen he says that loading game attributes has been working fine up until recently (the same for me); I wrote I had problems with loading game attributes too ( and I didn't do anything different that I've always done, usig the text field, all lower case too, for the keys, for instance).

So I'll say again to highlight it: there really does seem to be a problem with Load Attribute behaviours – with game attributes – that were programmed using GSC 0.10.4 and 0.10.4.1.

There's still a chance there's user error here but the odds are stacking up against that when it comes to load game attributes…

It'd be great to have an official word from someone at GS HQ to confirm or deny this.

BigDave

@gyroscope
You tested it with saving tables? Does it work, if i will just do that. Doesn't matter to me as long my work will not be wasted time. If not tested yet then i will do it quckly.

gyroscope

@BigDave

Hi Dave, yes, saving via tables still is absolutely fine… so is saving and loading scene attributes and (as far as I know) self attributes too… just game attributes don't seem to be loading with Load Attribute behaviours all of a sudden…

A small point to add concerning saving attributes via tables: if you want give your user the ability to start a fresh game as well as carry on from where they left off, make sure you copy the table, and use this one for saving your attribute updates… otherwise you'll be overwriting the start attribute values and won't be able to start "fresh" again...