INI vs Array

It depends on how complicated you want your save to be. Ini is probably better for simple things like configuration and array probably better for things like spreadsheets but I'm not 100% sure. I'd stick with that information if you find it's correct. Just go with what I said for now and wait for another 'answer' to crop up on your thread.

Hope this helps

I think array would be best to use if you have data that is very complicated that spreads across two/three dimensions while INI is good for if you just want to store specific values like score, lives, health, etc. of one object. I would use array however if you want to save these types of values for multiple entities.

Recently faced this question myself, and ended up rewriting an entire complicated saving system due to poor research on my end. INI is good (as others have said) for storing simple data. I used to employ INI all the time for stuff on the PC runtime and I loved it. But once I got accustomed to using the array object, it's just as effective. INI also has a size limit of something like 42kb? IDK.. I never tested this but it seemed to be the consensus.. and I couldn't risk it so I switched to the array object. Point is if I have to choose from now on between the two on iOS, I'm probably going to stick with the Array object main game data.. and INI for stuff like lists of savegames and their associated info. Hope that helps.

Also if you are saving both text and numbers then you might wanna go with an ini, unless you change the array over to a text array, and then you need to make sure you save everything to text. Then you'd just convert the text to values using Val()

After many years of using both... I would say Array is the best all around, just because the method of accessing the data seems easier to do. Especially if you are trying to load up tons of stuff in a loop.

I also prefer arrays to INI, if only for the last thing Konidias mentioned. It's REALLY easy to load/unload lots information from arrays using fastloops which is something I do in CoI, often. XD

Ini files are more "human-friendly" - you can open them up and read them in notepad, and you can refer to groups and items by name, not just a value.
Arrays are much faster and more efficient, and are perfectly suited to storing any kind of tabular data - but they can be more awkward to use in some situations, and it's not so easy to pre-load data into them or modify saved arrays (which is why I created an Excel<->Array converter).

I've wrote a dialogue (following the Dialogue Tutorial) but I got a question: how do I store the .ini INSIDE the .exe ?
I don't want to leave the dialogue.ini lying around (biggest concern). Another problem is that I must send the .ini with the .exe, what makes a bit "boring" to test on other computers.