No need for Load Behaviours for game attributes?

gyroscope

Hi, well I never, I said: I'm using Save and Load behaviours for scene and self attributes and all works well as usual (ad hoc on an iPad (1)).

Then after using Save and Load behaviours for game attributes, it's not loading any saved changes after quitting the app and then opening it again... I've spent two days scratching my head trying to sort this (I almost resorted to using a Table but decided to plod on trying to solve the Load for game attributes conundrum...)..

Anyhow, I've only just solved it: for game attributes, all I need is the Save Attribute Behaviours .... it seems that Saved game attributes don't need the Load Attribute behaviours for them to be remembered when opening the app again... just like Tables...

Has it always been this way? (If it has, I'm not sure how I missed that!) Or is it a sort of a bug/oversight that's actually an advantage? Any help or light shed on this matter appreciated, thanks! :-)

mounted88

Interesting, thanks for sharing

LumpApps

It would make sense, why save when you don't want it to load? I don't know if it is intentionally. It didn't use to work like that before.

artfish

I haven't tried removing them from my game lately, but before I had completed my load list (last year, fall maybe, not sure what build.) if I didn't load them, I would get the default values and not what was saved.

gyroscope

@mounted88 @LumpApps @artfish

Thanks for your comments and observations, guys. :-)

As it stands now, I think I made a mistake... (surprise, surprise... ;-) ) By that I mean it's not loading game attributes without the Load Attribute behaviour after all... (well, wadda you know... as you said, @LumpApps)

So there must be a bug with Loading game attributes... that's all I can think... unless I'm doing something so obviously wrong I'm blinded to it...

I'm off out in a quarter of an hour so will investigate more when I get back. In the meantime, if anyone's got any more comments about Load Att. Behaviours and game attributes, cheers.

JSproject

I think that load attribute will always be needed in order to load a saved attribute. It would not work to implement some kind of automatic loading of attributes for several different reasons.
One being e.g. that you may use save attribute at some point but then expect certain conditions to be valid before loading the attribute (in which case the attribute can't be loaded by any automatic system). The values in tables work the same way in that they are not automatically loaded, you "load"/ call upon the table values yourself when you need them.

Just my 2 cents..

gyroscope

I think that load attribute will always be needed in order to load a saved attribute. ...

Yes, you're absolutely right; it can't ever be anything different.... I've no idea why I was thinking game attributes could be "magically" loaded without a load behaviour... so desparate for a solution, I believed it to be true, I guess!

I've yet to continue testing, but I'll try using the Load Attribute behaviours right at the beginning of the app, in my splash screen (instead of at the beginning of the scene where the game attributes are used) and see if that works.

But if still not, there's surely a bug with Load Attribute behaviours for game attributes, I'll mention again... (unless anyone can tell me different and tell me where I'm going wrong loading game attributes...)