This was originally suggested by mingorau. I wasn't fan of the idea at first, simply because it added extra steps for end users and introduced the possibility of bad Arena2 folders caused support problems. But after some thought, I'd like to admit this idea has great merit and have introduced it as an option starting from version 1.3.10. I think this will also greatly simplify the process of creating standalone builds for developers. Here's how it works:
- In builds (i.e. not in editor) the application bootstrap will look for a valid Arena2 folder inside your Application.dataPath folder. For example, this would be AppName_Data\arena2 in Win/Linux builds. Web builds are sandboxed and cannot load from local filesystem.
- The FileProxy search order will remain Resources first, Arena2Path second. This means that if you want to use an Arena2 folder in your data path, there must not exist a .bytes version of that same file in Resources. This gives you the option to override specific binary files with your own .bytes version in Resources.
Such a simple change opens up a lot of new possibilities. I'm sorry I resisted this earlier.