Hello happy constructors,
[quote:2zzihyss]Whats wrong exactly with save/load?
Why and how behaviours colides with save/load?
What are the effects of this collision?
Each object/behavior has code in it to handle saving and loading of it's state when using the Save\Load action. I'm pretty sure the issues that come up with Save\Load action is because many of the object/behaviors don't save and load all of their state. The question is which plugins/behaviors?
Irbis you identified two:
1. Sine behavior: The source code isn't avaliable so I can only speculate that it's not saving the state of it's angle or opacity at all so with repeated Loads the angle and opacity will change.
2. Bone behavior: I looked at the source and it does no saving/loading so when you use the Load action the bone behavior is reverting to it's original state.
Also be advised that many 3rd party plugins don't save/load their state, my "Resource Plugin" included. So issues with them going back to their original state when Loading can be a problem.
[quote:2zzihyss]How to avoid problems with this issue?
For objects that you don't want to save\load you can give the "No Serialize" attribute in the editor.
[quote:2zzihyss]and why a broken feature is NOT disabled???
It works quite well with many objects such as sprites.
-cheers