07-21-2014, 05:51 PM
The reason why I mentioned JSON is because JSON is easier to work with when writing other applications, so what I'd really be doing in addition to adding my own custom data types is decoding rv3data files to JSON as well, so that I can access that data in another custom built application that will output a JSON file that can be read/encrypted into the game. I'm basically writing a script that governs a simulated and triggerable in-game economy, which will require an external configuration tool to generate the economy files which control individual map, region, and global economic modifiers and prices. Hence JSON.