Ways for INIs to save multiple game files?

You need to set a value in the INI before it's saved out (use Set Group - Item - Value or a similar action). If you set the current file of the INI but then don't do anything with it, then it won't create a new file.

Yeah, that would make sense. I think there's just something wrong with the whole path-saving thing. Can someone please explain a little more about saving the ini's to a certain folder but still letting the user name it with the whole Apppath$ thing? Like when you said it goes to your game, does that mean the .mfa or to a folder with your game title? Thanks...

Oh, I also wanted to ask if there could be another way to save its path while letter the user name it that may be simpler, like if there was a specific object or something.

Create a profile folder for the playername
eg %your app%\profile\%playername%
You will need to make some conditions for overwriting existing profiles YES / NO

Quote:

---

Originally Posted by Jdsfrog

Thanks... I tried it but only found that it wasn't saving the ini anywhere. The path to my game folder is C:\Program Files\Game Title. Now I have another folder in the game title folder that holds save data. So here's what I put whenever the user either types a new name or loads a saved game:

Set current file to
Apppath$+"Game Title"+Edittext$("Edit Box")

Of course with the "Game Title" name being my game folder. First I just want to see if it will at least save the ini into the game folder, then try the game data folder within the game folder. Is there something I'm doing wrong with the code or is there another way? Thanks.

---

If your MFA, or EXE file is in the C:\Program Files\Game Title, then you don't have to add "Game Title\". It'll be specified by Apppath$.
In that way you made it, it would save INIs to folder
C:\Program Files\Game Title\Game Title\
Also, you have to remember to add "\" after adding some folder to Apppath$. For example:
Apppath$+"saves\"+Edittext("Edit Box"). Otherwise it would save it to folder C:\Program Files\Game Title\savesname_of_the_file.ini

Thanks Pasiunia, now I can control where they are saved to... But the only problem is it never saves the name the user types in the edit box, so every time you go to make a new game it automatically overwrites the other file which is not titled anything. Here's my code:

Start button clicked | Set current file to
| Apppath$+"Gamedata"+Edittext$("Edit Box")
EditLineCount("Edit Box")> 0 | Set Group-Name-Value(Of course the names are in those places)

If anything looks wrong please let me know. It's saving everything to the right folder, it's just not naming them anything. Thanks.

I was also wondering if maybe there are different ways to save data instead of using an ini that may be easier, like the Data Store 2 object or the easy grid object. :confused:

Quote:

---

Originally Posted by Jdsfrog

Thanks Pasiunia, now I can control where they are saved to... But the only problem is it never saves the name the user types in the edit box, so every time you go to make a new game it automatically overwrites the other file which is not titled anything. Here's my code:

Start button clicked | Set current file to
| Apppath$+"Gamedata"+Edittext$("Edit Box")
EditLineCount("Edit Box")> 0 | Set Group-Name-Value(Of course the names are in those places)

If anything looks wrong please let me know. It's saving everything to the right folder, it's just not naming them anything. Thanks.

---

It seems that you didn't add "\" after "Gamedata".

Yeah, sorry about that, it was a typo.... I really did have the \ before the "Gamedata" thing. Right now I'm pretty sure the problem is it's not naming the file whatever is in the edit box, it's saving the data but the name is always blank so that's why it won't load the data. When you load it sets the current filename to whatever text in the list object is selected, but since it's name is nothing it won't load the info.

Well, I can't do much more without looking at the source :( If you want to, you can send me your MFA file and I'll try to tell you what's wrong.