Stencyl 1.2 - (Released Oct 26th)

I'm actually working on an idea for once and lightweight actors seem perfect for this

But why no mochi coins blocks? Mochi stuff looks like it'd be another tab in the game section of blocks.

As I mentioned earlier there is no way to bring in Actors or anything else, already created (local). So if you need to re-use actors/behaviours etc. you are forced to first Upload them to the forge and only then can you bring them into your new game.

There should be a system so that I can add an actor I already created, from my local hard disk. This ability to open/add local files is present in almost every system so why not Stencyl?

It is definitely a planned feature, but I do not have a time-frame for you, unfortunately.

There should be a system so that I can add an actor I already created, from my local hard disk. This ability to open/add local files is present in almost every system so why not Stencyl?

I wouldn't say that reusing an Actor from game to game in Stencyl is equivalent to opening a local file like in another program/system.  An Actor is not a simple file that's stored by the operating system -- it's a series of images, possibly linked behaviors, etc... So comparing it to a MS Word file (for example) is not really a fair comparison. 

That said, as Cole mentioned - there are plans to make this easier.  Just wanted to get the point across that it's not as simple as allowing you to open a file. 

Does this version contain auto cancel of periodic tasks? the "do every x seconds" block is driving me crazy.

Does this version contain auto cancel of periodic tasks? the "do every x seconds" block is driving me crazy.

Nope, this preview doesn't. I still need to get to that.

Ah alrighty. I guess I have to fix third boss of DD later.

Keep up the good work!

Ah alrighty. I guess I have to fix third boss of DD later.

Keep up the good work!

Out of curiosity - are you waiting for later because it would be a lot of work to fix your existing behaviors?  I just ask because everything that will be done with the canceling of periodic tasks can currently be done with blocks in design mode.

If we didn't say this before - the link provided is actually a snapshot of our latest code drop, so you're getting the latest and greatest (sometimes not so great if you catch us at the wrong time!).

Here's a changelog from the time of the first post.


Major

- Import Libraries into Engine (Flash). iOS coming soon. Very rough first cut by Mike. I'll make a second pass and clean up the UI this weekend.


Scene Designer Improvements

- Actor Palette > Search
- Typing in Actor palette should jump to appropriate entry.
- Control the palette while using pencil/fill tool using keys
- Space swaps between select, pencil, fill


Other

- Automatic Casting for Object, Text, and Number types.
- Add CCD setting to Physics > Advanced page.
- [Flash] Reycled actors should obey the layer that the create recycled actor block says
- Enable actor <-> actor collisions by default for new games
- [SW] Eliminate "reupgrade stencylworks" option.
- [SW] Move extensions folder to workspace.
- Custom blocks no longer throw Implicit Coercion error when placed in blocks using their return type


After iStencyl launches, and we put out StencylWorks 1.2. We'll pick up the development pace on StencylWorks as we move towards 1.5 (or 2.0) and make some sweeping improvements to StencylWorks. If you thought we were moving quickly, you haven't seen anything yet...

Add CCD setting to Physics > Advanced page.

Didn't know where to suggest this, but shouldn't Always Simulate be "upgrated" to a setting in the Physics page as well?

I wouldn't say that reusing an Actor from game to game in Stencyl is equivalent to opening a local file like in another program/system.  An Actor is not a simple file that's stored by the operating system -- it's a series of images, possibly linked behaviors, etc... So comparing it to a MS Word file (for example) is not really a fair comparison. 

That said, as Cole mentioned - there are plans to make this easier.  Just wanted to get the point across that it's not as simple as allowing you to open a file.

Hi Greg

I appreciate that it is not the same since the data is stored in the XML file. Besides Actors are not the only files. There are heaps of other types that can be brought in, behaviours for one.

But the process to do so is already there. It must be, since I can "import" actors, behaviours etc. from the Forge into my current project.

Therefore all that should be needed is to allow local packaging of the object in Q and instead of having to d/l and then import the package, I just point to a local package instead and the current code should do the rest.

Anyway apparently this is in the works so I don't mind waiting or I just might tear the XML apart and write my own function to do this.

Add CCD setting to Physics > Advanced page.

Didn't know where to suggest this, but shouldn't Always Simulate be "upgrated" to a setting in the Physics page as well?

Yes, we'll do that in a following release along with a bunch of other settings-posing-as-blocks.

Tonight's improvements

- Zoom In/Out of the Polygon Editor
- Zoom In/Out of the Collision Page
- Drag points in polygon editor.

We're hoping to put 1.2 out in final form this coming week, so we can start talking about 2.0 and our major plans to make vast and rapid strides in improving StencylWorks.

Second blog post about 1.2.

http://blog.stencyl.com/?p=311

So...no mochi API? It was mentioned in the original 1.2 blog post, but hasn't been since.