im looking for a solution for a leveleditor i want to make, i want to save positional data x y + setting(framenumber)

so i guess i need to put this to an array and then save the arraydata to disk or how do you go about this?

putting things into the array i think i can manage, but where do i go with this data?

R0J0hound

glad you found a solution for this, i do ask myself if this is an engine malfunction or platform issue that can be fixed or there is simply no other way to make this work

hmm should work, can you show a capx?

i think the best way is putting all the basic gameplay,scoresystem, mechanics in includes, so you have the basic "gameengine" all in includes, also the basic layers you need, then copy this layout and build your levels per layout and have extra eventsheets for level dependent actions,because you have the includes you can add events to the "engine" and will work over all layouts

Objects that you use thruout the project you set to globalobjects, it can also be good to put all your globalobjects into one "object"layout so you have an overview, and then you dont have to have them onstage destroying them on start, this helps unclutter you levels

hope this helps!

when dragging the ladder you can replace the object with a non-physics object and when release create the physic object again

no im not, i really cant help with this, i think its inherent off the platformbehavior, because of the gravitysetting, maybe someone else can give you help, or try asking Ashley what he thinks

hey, im a noob 2 youknow :) ask ashley!

no <img src="smileys/smiley4.gif" border="0" align="middle" /> its really a pickle!, dont know how you would fix it, really!

no its when timeleft bigger then (>) 0 substract 1 from timeleft

now you have when timeleft is smaller then or equel then 0

substract 0 from timeleft,   doesnt makes any sense :)

thats a pickle, i think its both, gravity puts it in and when going down, it looses a bit off that gravity + maybe a bit of lag on the objects moving seperatly, hmmm

yeah im sorry, i was too fast,

to restart or go to another level use the "system" "go to layout"

also only substract from timeleft when its bigger then 0

then normally it would be sufficient to use if timeleft = 0

but for safety i used if timeleft is = or smaller then 0

sometimes you can come in a situation where you substracted under 0

so using <= is safer then =

you should do this

when timeleft > 0 | substract from timeleft

when timeleft < 0 or = go to level1 (end game)