[Emmet_]

Quote:

Originally Posted by [uL]Pottus I should have mentioned not to get me wrong INI still has some uses where it might actually be desirable but overall compared to other tools that can be used it is very primitive another comparison would be dcmd to the likes of zcmd/ycmd. Look at Texture Studio's script it can be noted that it is all SQLite and the only time any file functions are used is for importing/exporting and some extended functions to show some files in a folder. But most new scripters will start with INI because they don't know any better and it is a lot easier for new scripters to be able to open their INI file in any text editor and edit it. So it's good to know INI of course but remember wise man once said "know your db".

Good point!

Personally, I think that INI files are only reliable for saving settings - which is the sole purpose of an INI file in the first place. For accounts, I rely on SQLite since backing it up is just a simple click and drag operation, rather than copying 2,000 user files to your Dropbox.

This tutorial is just to inform people that dini is out of date and should ALWAYS be avoided for personal use. Every week people are releasing gamemodes that use dini and people are using it, thinking that there won't be any problems, but then you end up with a thread full of "What are these part files in my scriptfiles?", "Why isn't user data saving on logout?", "Why can't I login?".

y_ini would also be great for saving player data, since with the tag feature, you can set the tag to the player's name and simply write to the file.

Irrelevant: The past week, I've been writing a library that allows converting INI files to a SQLite database and it should help out users a bunch (it would also automatically create the database and the columns which corresponds to the fields within the file).