Ok, after working with it all I can say is that Save/Load in system object just doesn't work or I'm missing something here. I've used on key press Save to AppPath + "name.sav" and the same
for loading. It does create the sav file in wherever the game is located but pressing L to load will freeze it or crash it with
'App terminated, report the bug to team, etc.' message.
So, here, I'm reporting it.
For the test, I took just a basic box, made it run around the empty screen and using the same technique from above, saved the game then loaded it back without any problems. Now, my game has 6 layouts and a lot of sprites/stuff, maybe the saving system is not yet optimized to handle that much? Memory issue?
Dunno, but I would really like to see this fixed because saving/loading is such a basic and expected thing in any game, it shouldn't be such a problem to make it work. So I hope someone from team will notice this. I can send my cap to anyone in team if that can help, otherwise I'll just have to remove saving altogether which sucks as it might be really hard for some people to play it then.