You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The type of a custom block in the block palette should persist after leaving the sprite and re-entering it.
Actual Behavior
Note: this only seems to affect large projects/sprites and/or projects originating from sb3 project files made in turbowarp. I tested it in a new project and it seems to work as normal.
all custom reporter blocks in the block palette incorrectly display and act like normal custom blocks (like not being able to be placed in reporters and being able to be placed in a stack) and blocks placed in this state stay in this state until deleted. the same custom block as a reporter before performing the glitch stay as reporters. The glitch only affects the palette, and all custom blocks.
Steps to Reproduce
Note: this only seems to affect large projects/sprites and/or projects originating from sb3 project files. I tested it in a new project and it seems to work as normal.
open a project/sprite that fits one or both of the two descriptions in the note above (if the description of a project you tried doesn't work, try another project fitting the other description.) if the sprite it opens when you load the editor has blocks that are supposed to be reporters but aren't, even with return blocks, that's the bug. Otherwise, switch to another sprite that has blocks that are supposed to be reporters. if those blocks that are supposed to be reporters aren't reporters, even with return blocks, that's the bug.
Operating System and Browser
Windows 11 22H2
OS build 22621.2361
Google Chrome
117.0.5938.134 (Official Build) (64-bit) (cohort: Control)
The text was updated successfully, but these errors were encountered:
Expected Behavior
The type of a custom block in the block palette should persist after leaving the sprite and re-entering it.
Actual Behavior
Note: this only seems to affect large projects/sprites and/or projects originating from sb3 project files made in turbowarp. I tested it in a new project and it seems to work as normal.
all custom reporter blocks in the block palette incorrectly display and act like normal custom blocks (like not being able to be placed in reporters and being able to be placed in a stack) and blocks placed in this state stay in this state until deleted. the same custom block as a reporter before performing the glitch stay as reporters. The glitch only affects the palette, and all custom blocks.
Steps to Reproduce
Note: this only seems to affect large projects/sprites and/or projects originating from sb3 project files. I tested it in a new project and it seems to work as normal.
open a project/sprite that fits one or both of the two descriptions in the note above (if the description of a project you tried doesn't work, try another project fitting the other description.) if the sprite it opens when you load the editor has blocks that are supposed to be reporters but aren't, even with return blocks, that's the bug. Otherwise, switch to another sprite that has blocks that are supposed to be reporters. if those blocks that are supposed to be reporters aren't reporters, even with return blocks, that's the bug.
Operating System and Browser
Windows 11 22H2
OS build 22621.2361
Google Chrome
117.0.5938.134 (Official Build) (64-bit) (cohort: Control)
The text was updated successfully, but these errors were encountered: