Nightly Patches (Discontinued in Sept 2011 in favor of better methods)

[Edit: September 3, 2011 - We're discontinuing the practice of applying patches manually in favor of an automated system in 1.2. If you'd like to get the latest, you can use the following 2 links, but they may be discontinued without notice when the new system is rolled out.]

http://static.stencyl.com/nightly/sw.jar (replaces [SW_DIR]/sw.jar)
http://static.stencyl.com/nightly/engine.swc (replaces [SW_DIR]/plaf/flash/engine.swc)


=====================

On occasion, we may ask you to download a patch that will fix a problem on the spot.

Here's how you apply a patch. Most of the time, only (2) is necessary to do.

---

1) Debug > Reupgrade StencylWorks
This will grab the language pack updates.

2) Grab and replace [SW_DIR]/sw.jar

http://static.stencyl.com/nightly/sw.jar

3) Grab and replace [SW_DIR]/plaf/flash/engine.swc

http://static.stencyl.com/nightly/engine.swc

Jon, side question: Maybe you could make Update Language Packs so it'll also download english ones? This way we won't have to download SW two times (once by reupgrading and second when downloading patch)

Just so that you know, I had my previous engine.swc file in [SW_DIR]/plaf/flash/engine.swc
I renamed the old one and put this one there. I hope I did it right.

Yeah that is fine gmvasco. Personally I just overwrite the file, but renaming the old one for a backup works too.

Jon, could you make changelog for patches so we will know what are we downloading?

The original instructions said to put the engine.swc file in the plaf folder -- but it actually needs to go in plaf/flash/.  I updated the original post.  So if anyone has tried downloading the file and put it in the wrong folder -- you're probably not seeing the most up to date engine functionality. 

Jon, could you make changelog for patches so we will know what are we downloading?

+1 Yea, I don't know when its updated as well.

Patches are generated very often. I could post major changes as they come (like the block reduction), but not for small ones that may only be in response to an internally filed bug.

I've updated the patch to what we're going to put out as 1.0.4 tomorrow. It's possible that we'll update the patch again tonight.

So far, it fixes these issues

- [Bug] Tiles offset to bottom and right, and other general mangling of tiles/collisions that was causing collision issues

- [Bug] Use of the get-font-height block made games untestable

- RPG Platformer Kit > Actor Behaviors > Save Point wasn't loading. We're still analyzing what went wrong here, but it may easily be causing other game's behaviors to not load up. We've patched the issue and are working on a longer term fix to this.

- There's been an internal reworking of animation/tileset/background importing to support resolution independence (for iStencyl). To the normal user, nothing should have changed. I want confirmation that nothing has broken in that area.

Thanks, I'll wait till the next update!

FYI, I downloaded Stencyl 1.0 osx and installed it for the first time today, every time I launched the app, I'd get "Warning: Stencylworks is already open or was unexpectedly closed.  Would you like to continue?"  Even tho the app wasn't running previously, even occurred after a reboot.

Also if I tried to update, I'd get "Stencylworks was unable to complete the update process.".  And I wasn't able to download anything from Stencylforge.

Long story short, applying the patches from this thread fixed my issues and Stency is running fine on my Macbook now. 

That's interesting. Thankfully, the codepath involved there is being ditched, as we're moving to allowing multiple instances of StencylWorks to be executed.

So to be clear, applying the patch also solved your network connectivity problems with StencylForge?

i downloaded Stencyl 1.0.0 and try to update but i got the same msg....
i try to replace the files but i got the same msg :/

I'd stick StencylWorks into a writable directory, until we fix that whole situation. It's the most common cause of a slew of issues along these lines.

If you've manually updated and want to shut off the updates, you can edit prefs/boot.txt and set this line:

prefs.autoupdate

to false.

I hope we will get 1.1 soon...