Importing/Exporting behaviors is not reliable in S3.4

Especially if one has global variables (and even in the target app one has the exact same variables), importing/exporting
is not reliable. Even making it with only local variables, it does not seem reliable.
It was more reliable in S3.1 and S3.2

And definitely NOT possible with custom code

Any plans to fix this?
And any  expectations to leave the 3.4 Beta status?

Thx

has this been addressed at all since you posted? I'm getting frustrated that i can't just export a behavior from one game and import it to another. It makes this idea of creating "training" games that i'm just goofing off in less attractive. Because everything i learn i have to hand move to another game. especially since you can't have 2 games open either, so copy and paste might not even work.

right now, the "export" button in scene behaviors literally exports the image you used to identify it. very unhelpful.

jexadox, the .png file itself is your behavior. Stencyl stores exported asset data in the .png file's metadata, so when you export a resource and it appears as a .png, that's the expected result. Just drag that .png file into Stencyl with another game open and the behavior will import.

ggbboo, if you can specify the problems that behavior importing/exporting has, that would be helpful. Please file an issue on the tracker with the following attachments:
- a screenshot of your behavior before exporting from the original game.
- the exported .png file containing the behavior, so I can import it for testing.
- a screenshot of the behavior after importing into another game to be sure that we're getting the same results.

Thank you.

Thanks a lot Justin.
It's been a month of different projects and regarding the game, we've decided to do everything from scratch, as the previous game had been the same for a couple of years, accumulating hidden glitches.
We will go over test apps with the exporting/importing issue and get back here, but we definitely tried it several times about a year ago creating behaviors from scratch and then exporting them to new app, the then eventually get many variables scrambled, even that we had the global variables created on the new game... I'll talk again to my partner and see if he had newer tests. We'll eventually post

Alright, thanks.