hey lucid.
In your Object array actions for object position, dimension / angle super array
can add one more parameter animation names.
Sorry for the late response. At the moment superbusy with the animation project, but I will try to remember to go back to this thread, when I next update the plug
I found a bug.
for some reason when ever I save and/or load a .txt files that contain super array, that have objects and strings arrays info s plug expression don't read global or private variable.
look at this
+ System: Is global variable 'd' Equal to 1
+ System: Trigger once
+ System: For each Sprite
-> Sprite: Set 'number_animation' to global('set_animation')
-> System: Add 1 to global variable 'set_animation'
-> Sprite: Set animation to S.s({"master_animation","tiles",Sprite.Value('number_animation')})
if
({"master_animation","tiles",0}) = grass
({"master_animation","tiles",1}) = water
({"master_animation","tiles",2}) = lava
({"master_animation","tiles",3}) = grass
take this expression for example S.s({"master_animation","tiles",Sprite.Value('number_animation')})
if
sprite 1 Sprite.Value('number_animation') = 0 it should be grass
sprite 2 Sprite.Value('number_animation') = 1 it should be water
sprite 3 Sprite.Value('number_animation') = 2 it should be lava
sprite 4 Sprite.Value('number_animation') = 3 it should be grass
but S.s({"master_animation","tiles",Sprite.Value('number_animation')})
don't read Sprite.Value('number_animation') so it stay at 0 which is grass
Hmmm. Ill try to take a look at this, sorry the response is so late but if I'm understanding you correctly it should be some other problem going on, there's nothing I can do with th sdk to change the way it reads expressions, so it should automatically read those correctly. Ill read thi agagin later to try an interpret
I'd like to try the plugin, are you still working on it? Should I download the alpha or wait for beta. Could you move it to the plugins section? It always takes me a while when searching for it.
Ill try to move it when I get home. Its fine to use now. Only broken feature is pointers, but they are not needed, just a shortcut
Just a suggestion if you ever add anymore to S.
How about a way to save an array within S itself?
Something like this:
+ System: For "x" from 0 to 5
-> S: insert number {1,2,3,4,5}@loopindex("x") to {""} at "end"[/code:2vapn45h]
With out the need of a loop.
That's definitely, possible. But yeah, at the moment focusing on the ultimate engine of doom, but when that's over remind me again and ill add that