No idea how to implement support for those.

I'm guessing he had a game idea and immediately started working on it without considering its viability.

It's like jumping into water without checking its depth.

Yeah, that should to the trick. I didn't really have such small tiles in mind when I developed the plugin, I was mostly working with larger tiles of variable sizes, but not that small, so I never noticed those issues you're having now. Sorry about that!

Thndr: unfortunately I am no longer maintaining the plugin, as it's gotten beyond my capabilities. I've not worked on it in quite a while, so all I can offer right now is advice.

• try to keep at least 1 px empty space on borders within individual tiles
• it is safe to make object size larger than what you want to display; in that case, control the displayed size via properties (e.g. fixed width)

See if that helps.

Check the start of layout events in all sheets.

Wow, people are still using the extra expressions plugin?

There is EaseTween behavior, which contains numerous interpolation methods, but it's more for tweening purposes. Figure you could use it for boomerang pathing, just keep the start and exit angles in mind.

Would be great if there was a way to insert such functions into a project, the plugin SDK is an awkward way. Not everyone can churn plugins out like a certain rex!

Sounds to me like a garbage collection issue, likely caused by flawed logic in events (such as creating new variables/objects every tick). I'm sure someone will paste a relevant link, but for now it's hard to tell what is going on without taking a glance at the actual logic.

I have no idea how you're using the pin behavior, but that probably doesn't matter at all. Adjust the sprite's hotspot for individual frames.

ArcadEd: Wouldn't surprise me, as CocoonJS has been covering more and more ground. Spritefont uses in-memory canvases and certain 2d/webgl drawing function that may not have been supported before.

lunarray: well, I can't exactly reproduce this, but I'm tweening objects between fixed positions. The angle tweens properly, but not position - it doesn't move even though I set starting and target positions. Force starting it didn't work either.

That reminds me - when tweening angles, it seems to rotate in one direction, often going full circle. Would it be possible to tween in the direction with smaller angle difference?

E.g. tweening from 0 to 270 runs 270 degrees, rather than 90 as desired. Perhaps I should use -90 as target using relative mode, but then I'm using fixed angles.

AMEND: Disregard the position tweening issue, I am an idiot. The object in question was pinned to another object's position, so of course it couldn't tween. The pin behavior kept it in place. Tweening the object it is pinned to solves the issue.

Yes, I am a blonde. <img src="smileys/smiley5.gif" border="0" align="middle" />

I am trying to tween several properties at the same time (position AND angle), however using two EaseTween behaviors at the same time seems to be glitchy at best. If I tween angle first with one behavior and tween position with other, the position doesn't change at all, even though I make sure to set initial and target positions.

What am I doing wrong?

CSS comes to my mind.