Hi, Maxsu! Thank you for this library! Thank you very much! I have a humble request through: could you please make an INI for Getter Plugin, in which I can change default INI-folder's name? I would say also, that having ability to mark specific INI-file names for mods inside DATA root folder would be nice too. By Marking I mean write them in main Getter config file. Anyway, again, huge thanks for this mod! I waited for this because get used to a classic INI config style
Well, however, Isn't that more convenient when put all custom INI-files inside a specific folder?
You only need to package your custom INI-files inside ""Data\MaxsuPapyrusINIGetterFiles", not need to care about any other things.
But if you want to specific the custom INI files name by write in main config file, that means all of your mod's users have to write down the specife name of your mod's INI file inside the main config file by themselves after install your mod. Won't that bring more trouble to the users?
was recently thinking what if there were something to use custom ini-s ini-s aren't so needed for presets, since there are .json and .xml solutions. PapyrusUtil, for example, also allows to store forms and lists of int/float/string/form. however it can be usable for configuration files that are supposed to be edited by users, since the syntax is much more simple. though the folder name is... you could use something like "INIs" or at least "INIGetter"
10 comments
Please ensure your custom INI files are all put inside "Data\MaxsuPapyrusINIGetterFiles" folder!
I have a humble request through: could you please make an INI for Getter Plugin, in which I can change default INI-folder's name?
I would say also, that having ability to mark specific INI-file names for mods inside DATA root folder would be nice too. By Marking I mean write them in main Getter config file.
Anyway, again, huge thanks for this mod! I waited for this because get used to a classic INI config style
You only need to package your custom INI-files inside ""Data\MaxsuPapyrusINIGetterFiles", not need to care about any other things.
But if you want to specific the custom INI files name by write in main config file, that means all of your mod's users have to write down the specife name of your mod's INI file inside the main config file by themselves after install your mod. Won't that bring more trouble to the users?
For end users, we probably don't need to worry about this until a future mods directs us here to install it as a requirement.
ini-s aren't so needed for presets, since there are .json and .xml solutions. PapyrusUtil, for example, also allows to store forms and lists of int/float/string/form.
however it can be usable for configuration files that are supposed to be edited by users, since the syntax is much more simple.
though the folder name is... you could use something like "INIs" or at least "INIGetter"
About the folder name, I just don't want to confuse the names, if there are also other mods that add a new custom folder relate with INI file.