Apologies if this is more appropriate for the Mission Makers tag, but as this is pretty niche and very much about persistence, this seemed the one to use.
Does the persistent database provide me with any variable or function through which I can write my own data to be stored across sessions? I don't even have specifics at the moment of why I might use it, this is more of a "well, I know I'm going to want this sooner or later for something..."
As an example off the top of my head, suppose I have some sort of vehicle requisition system. Think Bon's Infantry spawner but for vehicles, and I want to let players replace their (empty, not AI-crewed) vehicle losses over time. I would probably want to store some overall force pool value and modify that based on their time/frequency/type of vehicles requisitioned (spawned) that I would track. (I'm not actually proposing this, ALiVE logistics lets me do this already. It is merely a convenient and easy example.)
Is there some particular variable or function into which I can dump this arbitrary array of whatever I might want to save, and on reloading a session with persistence enabled, ALiVE will spit that back into Arma that I might access and sort it out again for my various purposes?
I know the Combat Support module does have the "CS_code" setvariable. I'm not sure if that gets saved and carried over across sessions or if it is just used when respawning a Combat Support asset but is set afresh from the module each time a mission is loaded on the server. (And would need to be reset each time a new Combat Support asset is manually registered by some other script.) It would be a hell of a hackjob, but if that does get updated and persists across sessions, I imagine I could try to inject my overfilled-array-of-whatever in there.
If this isn't something I can do, does anyone know if there are any other options available to me? I know I could run iniDB on my server, but that seems like such a waste when ALiVE is already doing so much fantastic storage for me.