Basically what this element does is opens a new save page when sparked. Lets say you have a save that is too large to fit in a single save. This element will fix that by opening the second save after the first save has been shown. So if you have an electronic maze for instance, it would be continued without any problem on the next save. But of course, you would have to make sure that everything is running in the next save correctly in order for it to continue. Please keep the flaming down to a minimum and I would love to hear feedback.
I suggested this before...for some reason they didn't understand. O_o
So basically, this would allow for automated sim. transitions? Nice idea, though i dont know if its possible to code. I really don't know when anything is possible to code anyways, i dont know why i say that.
I think it is possible, but I need to know what file opens saves, not the one that makes them. If you put that in an element function, it may work. (maybe, depending on how saves are opened)
EDIT: Much better idea, open the save with the element (id plugged into a property) the same way they are opened from the website.
I am glad someone has actually understood what I am saying. I think this would be useful to those people that want to make extenstions of saves.
No, people would use this to advertise their saves by forcing people to load them.
That would defeat the purpose... perhaps there can be a limit of exactly 1 LINK pixel per save?