I have URL information for services (dozens of them) that I want to store in a Unity3D web player project. What is a good practice for storing it. (please don't say hard coding them)
I've recently joined a large scale Unity 3D project in the business world. I've noticed that there is no configuration file of any type. I.e. All URLs for service calls are hard coded. (among other configuration settings that are not typical for player editing)
While looking for a good solution to store/load, I'm seeing that: 1) Unity does not appear to have any kind of AppSettings. I.e. like Visual Studio dlls/exes/services might. (PlayerPrefs expressed in #3)
2) Web Player (which the project uses) does not support File IO, to store my own config.xml/config.json type file.
3) PlayerPrefs appears that it will remain isolated to the local machine. Updating the project does not replace the player prefs, and new variables are supposed to be hardcoded to populate the PlayerPrefs if those variables didn't already exist.
4) Hard Coding the values creates a hefty inconvenience, as we push our solutions from Dev to Test to Staging to Prod, we have to make sure to replace a code file. (typically systems are designed to change config files.) Additionally, once the code was built, we wouldn't be able to reasonably change the settings to experiment with different servers or other configuration changes.
What would you recommend?