Hasn’t quite been a quarter of a year yet, but @ralph I got a bug to report.
Basically, when you Break Apart a movieclip on a frame that contains figures with the Lock Node Position (or whatever it’s called) on any of its nodes, it’ll go back to the position it was at in the movieclip rather than where it should be on the workspace. I’ll attach some images to help you understand what’s going on.

Original frame

Note the locked nodes

This is the frame in the Workspace

I hit break apart and this is what happened.

On another note, regarding the movieclip auto-deletion, if it is coming, would you say it’ll be coming in a minor update after this one, or will it be included in a later major update?

Well, well, well, hasn\’t it been a while? Quarter-yearly post time. This time, I have a bug report and a suggestion for @ralph

First off, the bug report. This seems to happen most commonly when animating in movieclips at 15 FPS with 1 tweened frame. When you move a figure and add a frame or, basically just try to animate a movieclip normally, sometimes to tweened frame doesn\’t register the change so when playing it back, it ends up flickering between the original position and the actual position. This only appears to happen in the movieclip editor and not the main workspace, which is odd. In case it\’s device-specific, I\’m on a Samsung Galaxy Tab A7.

Next up, the suggestion. I think that, if a Movieclip is set to Play Once, there should be a checkbox option underneath that (only available to check on the Origin frame just like the Play Once and Loop checkboxes) to have the movieclip automatically delete itself when it reaches its end. This would be useful for many things such as effects, as rather than having to go through and delete them afterwards or just having a bunch of blank movieclips now laying around, they just auto-delete. Same goes for things that would be part of a game\’s UI (such as a movieclip of text [using figures] that says, for example, CRITICAL, popping up for a second or two) to get rid of it and save nodes at the end. This isn\’t required, just a sort of QoL thing.

Alright, quarter-yearly post time! So, @ralph remember that bug I told you about regarding the Use Join Parent Filters button? I’ve worked out a way to consistently replicate it.

1. Join a figure (figure A) to another figure (figure B)
2. Enable “Use Join Parent Filters” on Figure A
3. Copy-paste Figure A and move it somewhere
4. You now have your glitched figure

Also, new site decor, rating: 10/10, the Protoge– the Wingidon approves

Yo, uh, @ralph take a look at this.
Pack A:
http://sticknodes.com/sticks/flash-style-blood-spurt-pack-zip/
Pack B:
http://sticknodes.com/sticks/blood-pack-6-zip/

As people in the comments of Pack B have pointed out, the submitter of Pack B has stolen every figure of that pack from Pack A.

Here, you can see the original.

Here, you can see the stolen.

And it’s not even been a day yet but Guigui may or may not have posted the same pack twice.

And again, it hasn’t been a quarter of a year, but @Ralph I got a bug to report. It basically goes like this: This movieclip has 8 frames. It is set to Loop and told to Start On Frame 8. This project has 2 frames. This movieclip continued straight to its own Frame 2 and skipped Frame 1 for some reason.