Example: So, Scratch is an easy to understand programming language for beginners, right? But lets say… Person12 used scratch before he made a more advanced game that used different sprites. He wants to make the game and get into more advanced programming but he has to learn another programming language first that requires you to use a sprite sheet. He also wants to use sprites for characters, but to do so, he has to learn how to make a sprite sheet. Since Scratch doesn't have them, and he wasn't taught how to use them, he is unable to make his game.

The example above kinda is terrible, i wrote it in 2021. If it is bad, just ignore it xD

So, my suggestion is to make an option called “Advanced Sprites” which would give functionality to use sprite sheets. If you do it while making a project, then maybe it can convert? but with this will be added a block

[costume 1 v] located x: [ ] y: [ ] through x: [ ] y: [ ]::looks

This would basically decide where each costume in the sprite sheet is located. (top left to bottom right)
Or maybe like the

point in direction ( v)

block, it would be a dropdown so u can highlight the area the costume is located.



Well, this was my idea for a sprite sheet!

by the way if u have more block suggestions reply

(sr\orry i forgot editing existed

Maybe this could be a pen feature:

stamp from x: () y: () to x: () y: () from costume :: pen

Use line [3 v] row [4 v] from [Sprite Sheet v] as  :: looks
(Sprite Sheet::looks)

When you show the variable, it would show something like:

and how you would make one:

of course, this is only my opinion.

Steve0Greatness wrote:

Use line [3 v] row [4 v] from [Sprite Sheet v] as  :: looks
(Sprite Sheet::looks)

When you show the variable, it would show something like:

and how you would make one:

of course, this is only my opinion.

Actually, i kinda like that “Make sprite sheet” button!

This may be too confusing

cruncherBones wrote:

This may be too confusing

If you think about it, X and Y could be confusing.

Steve0Greatness wrote:

cruncherBones wrote:

This may be too confusing

If you think about it, X and Y could be confusing.

The

go to x: () y: (0)

Block is quite simple

cruncherBones wrote:

Steve0Greatness wrote:

cruncherBones wrote:

This may be too confusing

If you think about it, X and Y could be confusing.

The

go to x: () y: (0)

Block is quite simple

lol not just the block

their talking about coordinates themselves

but please elaborate on what exactly is confusing

cruncherBones wrote:

This may be too confusing

bump, also I'm asking you again to please elaborate

support, its a ton of work to extract each sprite from a spritesheet

bump

Bmpu

Bump

Support, if the spritesheet order and placement is determined by costume order and when exporting the sprite, it gives you an option to export as spritesheet.

This so confusing, make it yourself

No support

cruncherBones wrote:

This so confusing, make it yourself

No support

What’s so confusing about it, if it auto-compiles to spritesheet based on costume order and let’s you have an option to upload as spritesheet? Not complicated and relatively easy to do (on our side). Also, if you do it yourself, that will not work. Mainly because when doing that, it compiles to one costume when they are all in the same costume, so the sheet would identify that as the only frame.

Please dont make hubs.

Roblox888i wrote:

Please dont make hubs.

It’s not a hub. The user is suggesting something and allowing others to add on to it. It’s not the same