Printable View
So I'm making an action RPG and was wondering about saving functions. The save frame position seems to be a little too good to be true hehe. It saves Everything and loads all values saved etc. But how will it be as the game grows bigger? Using an ini seems soooo difficult when you need to have quests saved...inventory...NPC's values (quest givers etc) What is the best way to save? I like the save frame position but I don't want it to crash in the middle of the game :)
I would avoid it.
Ini or Array is the best choice
Gaahhhh...[censored] :D Is the best way to go to keep doubles of all important values to save in one room? I mean...like...you get a quest from a guy in a town and later you want to save. So on that frame where you save you have all counters and characters etc that you want to save or how the [censored] does it work? :D
That don't help me one bit because i am a moron ;D
My opinion is use the save game feature.
If you encounter a problem with it please report it to the bug box -- We want it to work 100% so getting people using it would be helpful.
Do you mean the save game object you can create? because i tried it but nothing seems to happen or did you mean that save frame position? Just want to be clear :D
Yes the built in saving routines in the storyboard object
I realise this post is two years old but if Jeff is talking about the Save frame position and Load frame position when referring to "saving routines in the storyboard object" these are bugged. Using them causes any objects with movements set to stopped at the start of a frame to move when the frame position is loaded, though not all of them it seems - just randomly. And it also sometimes crashes the running frame or application.
Using Arrays and Ini's for my game is out of the question because it would take twelve months to enter all the data for all 3,500+ objects their positions and values 90 times for each of the rooms where the player can save.
I guess I made my game impossible for adding a working save system - not that I intended to from the start.
Soopytwist - Not necessarily. If you assign all your objects a qualifier, spread a value, you can then save/load in just one event... I suppose it depends how it's structured and how you want to use it. Could be worth a shot...
I dunno Danny, I think I might have shot myself in the foot. Had I planned to add a save feature from the start I'd have done things differently.
Anyway, my game is almost complete just adding a few extra things after the incredibly tedious coding all possible player respawns. Perhaps someone could take a look and see if a saving feature is still a possibility.