hi,
do not hesitate to hammer me with question son ArrayMaker
I am thinking of creating a new version of ArrayMaker that will not require a component per array, but that's not for tomorow I am afraid...
As for referencing arrays, this is needed when you have two or more arrays on the same game object, else I can't know which one you want to access. if you have only one array and/or only one hashtable, ignore the reference, tho I would strongly encourage you to always use this, because if one day you need another array on the same gameobject, you don't have to go throught all your actions and put the right reference, since you would have done it to begin with.
Well spotted for this error, It slipped my testings, I forgot to implement a feature in the framework itself... ( it works for hashtable, but forgot to do it for arrays) so please download the file attached and replace it in your project folder, and it will not fire errors when you create an array. Anote to users that wonders about the playmaker error fired by the action itself, simply ignore it, since you are creating the array at runtime, the action warns about the fact that it hasn't found any for obvious reasons. I haven't find a good work around since I can't really control the action UI well enough to accomodate for this.
bye,
Jean