Thanks for the explanation Joel! As a non-coder building this whole game strictly via Playmaker, learning about the Editor itself has been patchwork at best. These details about setting things up for Android aren't obvious so thank-you!
There's a triangle of logic I'm trying to get my head around as I implement this recommendation:
(My Unity Editor is setup with the EasySave3 Runtime Settings Location/Directory to 'File'/'Persistent Data Path'. So by default, all ES3 Playmaker actions are pointing to that persistent path when I try to save/load as I understand it now.)
Does this mean for save/load to work on Android, I need to:
- Keep my editor Runtime Settings pointing to File/Persistent Data Path
- Load .CSV from my Resources folder
- Save .CSV via the Persistent Data Path
- Somehow copy my saved files from the Persistent Data Path to my Resources folder so that when I load again, I get the newest data (maybe using the ES3 Copy File action?)
- Somehow use the Resources path when trying to load, even though the editor (and thus build) is pointing to the Persistent Data Path (maybe using the 'Override Default Settings' on the action trying to load in my FSM so it uses the Resources folder instead of the Persistent Data Path?)
Because my Runtime Settings are already setup to File/Persistent Data Path, all saving and loading seems to universally try to use that file path. I understand leaving it set to the Persistent Data Path because that's the only path Android can write to (thanks again for clearing this up for me!), but to then copy my saved data over to the Resources folder, would I use the ES3 action 'Copy File'?
If so, I'm guessing "Old File Path" is already rooted at the Persistent Data Path, but what exactly would be the "New File Path" knowing that it will be on Android? The Resources folder currently has my typical C:\\Unity\. . . type path but when this builds for Android, is there some kind of naming convention for the Resources path everyone just knows (that I'm probably missing out on because of doing this all via Playmaker
)
Also, once I get the .CSV copied from the Persistent Data Path to the Resources folder, would I have to activate the 'Override Default Settings' on the action trying to load in my FSM so it uses the Resources folder instead of the Persistent Data Path?
I'm sorry this thread is going on for so long! I honestly don't mean to be a bother. Maybe there's an Easy Save 3 demo using Playmaker I could reference that already works on Android? Or even more, I'm willing to hire you for 30 minutes to connect over Discord and just walk through the fix? I get the feeling this is something really simple and it's just me not understanding where things need to be clicked/setup. You're gonna look at this project and be "Peter, look, just put this path here, click this button, now build. It should work." Like, this is probably such a simple fix it would take a guru like you 3 minutes to solve.
But so far, I've been struggling to understand the setup between the player sitting in the Android game wanting to save/load some data and the build not having either the Persistent Data Path (to save) or Resources folder (to load) setup correctly (this is the triangle of confusion I was mentioning earlier). If you don't think this can be explained-out here, I'm serious about hiring you and connecting over Discord just to solve my ignorance, please let me know!