Hi,
1: Some Fsms do not need to do anything when they start, they are only reacting on global events ( defined as global transition in black above a state).
to make this clear, I simply put a SPACE or "idle" as the start state name.
Is that your question? else can you make a screenshot of what you would like to implement?
2: It can indeed be used to save game states DURING RUNTIME. If the user is quiting the app, then it won't persist. For this you would need to use playerprefs or some serialization system that you can save and retrieve from as your player comes back to your app.
3: Yes, I do that in purpose to test that indeed it fires an error, this is for testing, so you also need to make sure it fires errors when it must.
4: Spreadsheets ( .csv) are not hasthables. This is two different concept all together. I do plan on supporting spreadsheet, and I do have working code for this
http://hutonggames.com/playmakerforum/index.php?topic=891.msg3876#msg3876
pm me if you are interested in getting this feature developed to be usable in your application.
ArrayMaker is not a database, totally not. It is simply to wrap arrays and hashtables to be available within playmaker. Database is a totally different fields.
Having said that, I do use arrayMaker to retrieves resulsts from a database query. I do this by defining as much arrayList as there are columns ( one arrayList per column), and inject the result in each one of them. I then simply access the value I need based on the row index and the column name ( giving me a pointer to the arrayList holding this column set of value).
You can't have multiply data per item. instead, do as I mention aboved, have one arrayList or hashtable per type of data you want for a given key. That works very well
If you need a working sample ( try first tho, best way to learn is to try and do it
), I'll provide you with something to get you started.
Bye,
Jean