How do I downgrade back to 1.0.2?

I upgraded to 1.0.3 and found a handful of bugs in my game in a matter of minutes that definitely weren't there before the update. I want to go back to 1.0.2 - where can I find the download link?

You can't go back to 1.0.2.  What bugs are you experiencing? Perhaps some are not bugs and are rather changes/features that you might think are a bug.

Wow - seems very unprofessional to give an innocent little update notice when you load up the program without any warning of it being non-reversible whatsoever. Surely any and all updates to Stencyl are going to affect people's games? Isn't it absolutely crucial to ensure that they are all reversible?

And no, they are bugs in my game. It's possible that my game previously relied on bugs in 1.0.2 to work and now those bugs have been fixed, it's affected my game.

Let me quote what I said on the main thread:

Is it possible to change back to 1.0.2 from 1.0.3? I don't have a back-up and 1.0.3 changed my behaviours to the new blocks etc so I'm not sure it'll downgrade?

I'm sure 1.0.3 is an improvement but I've found loads of bugs in my game after the update and should have known better than to update mid-way through development...

EDIT:

No games should break.

This isn't true. Many parts of my game are working differently, and I only played through the first few levels - there could be more bugs that I haven't spotted... Some examples: my switching scene behaviour stopped working properly after the update, I can no longer push actors up a ramp (it just refuses to move after reaching the base of the ramp), I have a series of tiles with one of the tiles replaced as an actor (with identical appearance and collision boundaries) but if I try to walk right from a tile to the actor, my player somehow collides with something and won't move forward so I have to jump over it...

EDIT: Okay - I redownloaded Stencylworks 1.0.0 and unsurprisingly the downgrade from the new blocks to the old blocks wasn't perfect. The controls don't seem to work properly (eg the difference between 'is pressed' and 'is released' etc etc). Also, most of the 'play sound' blocks are missing, but not all of them, strangely... All the bugs I mentioned above were fixed, so 1.0.3 is definitely the cause of those problems.

Since I don't have a back-up, I guess the only thing I can do now is find out where I can get the 1.0.2 upgrade then just work out which blocks weren't downgraded properly and attempt to get the game back to how it was.

EDIT: I redownloaded 1.0.3 and oddly, all of the sounds and controls were fixed (). So I have a scenario where I can reinstall 1.0.0 and see that there is absolutely no 'play sound' block in the behaviour, just to upgrade to 1.0.3 and have the sound block magically reappear (although obviously the 1.0.3 specific bugs appear too). Weird. Anyway, that gives me hope that upgrading from 1.0.0 to 1.0.2 will also sort the problem and I'll be back to where I was.

Any chance of a download link for 1.0.2?

If I can't get a download link for 1.0.2 then I'll just use 1.0.0.

If that's the case, then is there a way that I can download both versions of Stencyl (1.0.0 and 1.0.3)? That way I can check every single one of my behaviours across both versions and do the block backtracing myself. Fun.

Well, you have quite a few issues going on here, so we should probably do some troubleshooting.

1.  press   ~   to see if there are any errors in the console while testing the game.
2.  what exactly is not working with the switch scene behavior?
3.  for your random collision issues, I've experienced something similar before. I recommend you download game debugger on forge and use it to check the collision bounds in game.

In terms of downgrading to 1.0.2, you need to realize that we are still technically in beta, it is just a public beta rather than private. This means you are likely to experience bugs with the application. If you do, then report them. Unless a section on the site contains archived versions of SW, it is likely you won't find older versions, not now or in the future, or unless someone has a copy available.

Also, there are plenty of programs that make updates without advising its irreversible.

Oh and in regard to the missing strings/blocks, etc. it is because different features exist in different versions of sw. Example would be that 1.0.2 introduced different sound blocks, hence their lack of avilablity in 1.0.0. 1.0.3 introduced a block reduction which means language packs were updated, thus making it so strings were missing in 1.0.0.   these changes, of course make it hard to just reverse the version you are using.

I don't see the relevance of saying that the program is in Beta. My problem wasn't with bugs in the application, it was with giving an update that changes people's games without letting people know that it changes their games, then not letting them go back to the old version when they find out. There is a difference between iTunes (for example) releasing a non-reversible update than a program where the update can ruin weeks or months of work.

Thanks for trying to help troubleshoot my game but I'm not going to attempt to fix the 1.0.3 version. The game worked perfectly in 1.0.2 and making changes to collision boundaries, behaviours etc is only going to interfere with my level design.

To confirm - it is impossible for me to get hold of the 1.0.2 update? I'm not asking for it to downgrade from 1.0.3 - I'm asking for the upgrade from 1.0.0 to 1.0.2.

To summarise - the two questions I have currently:

1) Can I get hold of the update from 1.0.0 to 1.0.2?

2) Is it possible to install Stencyl twice and open both programs at the same time? This is necessary for me to open my game in 1.0.3 and then open it in 1.0.0 (or 1.0.2) and change the blocks that didn't downgrade properly.

There's no way to recover 1.0.2 short of asking someone who has it to provide it. Someone on the extended team might have it, or might have an earlier copy. I know for fact that Irock is holding on to an older version.

Even if you grab the binaries to try and patch over your copy, it will not work because of the language pack changes, which we don't tie to a single version but continually update.

At this time, unless you're using two different computers, you can't open multiple copies. It is one of the items we're working on for 1.1.

You haven't indicated at all what the actual problems are - it's likely that they're a simpler to resolve than you think and may involve little to no changes on your part.

There's no way to recover 1.0.2 short of asking someone who has it to provide it. Someone on the extended team might have it, or might have an earlier copy. I know for fact that Irock is holding on to an older version.

Even if you grab the binaries to try and patch over your copy, it will not work because of the language pack changes, which we don't tie to a single version but continually update.

At this time, unless you're using two different computers, you can't open multiple copies. It is one of the items we're working on for 1.1.

You haven't indicated at all what the actual problems are - it's likely that they're a simpler to resolve than you think and may involve little to no changes on your part.

If I can't open two different copies, then it seems I have no choice but to move onto 1.03. I still think it's wrong that my behaviours were irreversably changed without warning, but it's too late for that now.

I actually did mention some of the problems I encountered, although the list is almost certainly not exhaustive as I only played for perhaps two minutes. In the first 4 levels of my game I encountered 3 bugs that were not there before. The main issue I have isn't that these particular bugs are hard to fix, but that I spent a long time debugging my game only to find that I now have to start over - all that time was pretty much for nothing now I have a new fresh load of bugs, probably including many that I won't find for a while. Then of course fixing those bugs will spawn fresh ones. It's just annoying when it should be completely unnecessary - I had a perfectly working game and now... I don't. Ah well.

If you haven't saved the game with the behaviors open, the behaviors won't be changed, and the game will open in 1.0.2.

Glancing at the issues, except scene switching, these seem unrelated to the block simplification (which I thought was the culprit). I'll have Mike and Greg take a peek.

You may have luck using 1.0.3 but sticking to the 1.0.2 of the engine itself, which I'll have someone post up here.

Edit: 1.0.2 Engine is attached. Stick into plaf/flash/

Could you upload a zip of your game, or send it to me in a PM if you don't want it public?

If you haven't saved the game with the behaviors open, the behaviors won't be changed, and the game will open in 1.0.2.

Glancing at the issues, except scene switching, these seem unrelated to the block simplification (which I thought was the culprit). I'll have Mike and Greg take a peek.

You may have luck using 1.0.3 but sticking to the 1.0.2 of the engine itself, which I'll have someone post up here.

Edit: 1.0.2 Engine is attached. Stick into plaf/flash/

Thanks. I did save the game with the behaviours changed but this solved most of the problems. My scene switching now works and I can now push my actors up ramps. Another problem that I forgot to mention was that actors seemed harder to push around with 1.0.3, although I can't say 100% whether that was just a feeling I had, but with the 1.0.2 engine it seems back to normal. I'm still having the weird issue where my player is walking into an invisible object (the bug only exists in 1.0.3) but I'm looking into it now.

Could you upload a zip of your game, or send it to me in a PM if you don't want it public?

Do you still want me to send this now that it's solved?

EDIT:

I solved the weird invisible collision problem. In 1.0.2 there was a bug with tiles which meant that if the bottom of my player character's collision boundary (eg the bottom line of a square) wasn't a downsloping line, it would only register bottom collisions once every 3 frames (). It seems that this bug is fixed in 1.0.3 but - now actually having downsloping lines causes collision problems. Once I make the collision boundary back to a square, it's solved. Thanks for your help!

We actually would, so we can debug the issues you ran into and do a "diff" between 1.0.2 and 1.0.3. Thanks!

I can't figure out how to attach to a PM so I'll attach here then take it down. EDIT: I saw 1 download so I took it down. Post if you'd like me to reupload.

The bugs might require preknowledge of the game to find though...

Left/Right = move
Up = Jump
Down = Duck
Z = Shoot

Press A to be invincible for that level (a test feature)

For the first 'bug', jump up to the hill thing on the far right of the starting scene and slowly move towards the edge of the screen. You'll notice that instead of spawning in the next scene, it kind of spawns in the next scene then quickly puts you back in the starting scene. In 1.0.2 this doesn't happen.

On the fourth scene to the right there's a ramp. You can shoot blocks to move them. If you try to push a block up the ramp by shooting it, it'll collide with the base of the ramp and not go up. In 1.0.2 it slides up the ramp easily. I also think the blocks are harder to push in 1.0.3.

Something is up with tiles.  It's like they shifted down and right one pixel between versions.  If you move your ramp down a pixel (or two) the problem is fixed in 1.0.3.

Something is up with tiles.  It's like they shifted down and right one pixel between versions.  If you move your ramp down a pixel (or two) the problem is fixed in 1.0.3.

Interesting. So every single tile was shifted? I didn't notice... And I assume the scene switching problem is a different issue? I used some print statements in my 'New Map' behaviour earlier and when switching scenes it definitely spawns my character in the right place, then for some reason moves it to the left which triggers another scene change.

These are probably related, and a new patch should be coming for them tonight.  Found what was causing the problem.