You Know What Would Be Great? Adding Some Sort Of Little Room A Camera Could To Take Place In This Way No Longer Shall People Hesitate About Making A Scroller Project Like I Am Because Coding Scrolling Projects Always Take Up A Lot Of Coding And Space Which Also Makes Anybody's Scrolling Game Load For Even LONGER That's Isn't Even Counting
Enemies, Collectables, Cutscene Triggers And Handling And With Any Other Character Object That Might Be Involved In The Cutscene, AND MORE!

While I Do Support The Work Of Scratch Team I Don't Know If Scratch Cares About Scrolling Projects, If They Did The Would've Did Something To Help
Maybe Do What The Game Making Tool GMS2 Did It Gave You A Big Room That You Could Change The Width And Height To Your Hearts Content
The More I Think About It The More I Think Scrolling Projects Aren't For Scratch

Not Trynna Offend Anyone Or Even Scratch Team Just Spittin Some Facts Here

Can you simplify it a little bit because I don't understand it.

Rendangbike2 wrote:

Can you simplify it a little bit because I don't understand it.

I think they're talking about adding something like this

YES You Get It That's What Scratch Team Should Be Focusing On Right Now Because It Will Make Things So Much Easier

TheBlueScratchCoder wrote:

YES You Get It That's What Scratch Team Should Be Focusing On Right Now Because It Will Make Things So Much Easier

Please don't use shift on every word.

Please speak like a normal person so I can actually read the suggestion.

From what I could understand: making scrolling projects isn't really that difficult. I think that teaching kids how to overcome coding hurdles is much better than handing the answer to them. JavaScript does have an equivalent to this though, so maybe it does have some merit.

*, wrong topic

the2000 wrote:

Please speak like a normal person so I can actually read the suggestion.

Fine i'll speak like a normal joe but you won't be able to tell if there's a hacker on my account or not

Anyway what's more important children Having UNESSESSARY load times On Their Cool Scrolling Game Or giving them a solution so there games can have MUCH more content? Remember that's not even counting big levels, enemies, and much much much more Maybe limitation breeds creativity But some times i feel like i'm making a game for some janky plug & play console

This all boils down to 1 thing scratch needs to help scrolling games
ACTUALLY Why doesn't scratch use some sort of compression system to better fit huge projects?

Why are you capitalizing every word? I capitalize the months of the year(which according to google isn't grammatically correct), but this is just plain crazy.
Also why are you speaking in riddles? There's no need to make it literally impossible for people to know what you're saying.

TheBlueScratchCoder wrote:

YES You Get It That's What Scratch Team Should Be Focusing On Right Now Because It Will Make Things So Much Easier

Griffpatch_tutor makes coding easier, not this.

I don't make platformers(I've made one, didn't enjoy it), so this would just be another thing to learn

Steve0Greatness

Griffpatch_tutor makes coding easier, not this.

Do you realize the cost of Griffpatch_tutor's Code? lots and LOTS OF L O A D I N G…Scratch constantly puts you at a position where you are always saving space and decreaseing loading time whenever and wherever you can and games on scratch suffer the most

TheBlueScratchCoder wrote:

Steve0Greatness

Griffpatch_tutor makes coding easier, not this.

Do you realize the cost of Griffpatch_tutor's Code? lots and LOTS OF L O A D I N G…Scratch constantly puts you at a position where you are always saving space and decreaseing loading time whenever and wherever you can and games on scratch suffer the most

I don't think you understand how the code works. Compacting all those scripts into just one block would not make it faster to load. Also, scrollers are a skill that all programmers should know how to do.

I made the suggestion easier to read!

You know what would be great? Adding some sort of little room a camera could take place. In this way, no longer shall people hesitate about making a scroller project, like I am, because coding scrolling projects always take up a lot of coding and space which also makes anybody's scrolling game load for even longer. That isn't even counting enemies, collectibles, cutscene triggers and handling, any other character object that might be involved in the cutscene, and more!

While I do support the work of the Scratch Team, I don't know if scratch cares about scrolling projects. If they did they would've done something to help. Maybe do what the game-making tool GMS2 did. It gave you a big room that you could change the width and height to your heart's content. The more I think about it the more I think scrolling projects aren't for scratch.

Not trynna offend anyone or even the Scratch Team, just spitting some facts here.

Support, this is something simple that's too difficult for most to do in Scratch. In fact, there was some point in development when scrolling was possible, which means the Scratch Team already has the code to implement this (I think).

PkmnQ wrote:

clear explanation snipped

Thanks for that. OP, please try to put a bit of grammar in to make it clear.

–

Scrolling projects are not hard. Griffpatch did 1 on his YT channel 2 years ago, and it has scrolling horizontal and vertical, good player movement, collectables, lava, and you can tweak the code to implement more stuff, like a bounce pad or water.

Look, sometimes, you actually have to put effort in a project and not just do it magically with 1 block.

dertermenter wrote:

Look, sometimes, you actually have to put effort in a project and not just do it magically with 1 block.

There’s quite literally no need to say stuff like this. While I’m not 100% on the practicality of OP’s suggestion, this isn’t Reddit. Making snide “clever” comebacks isn’t how you post feedback in this subforum.

Anyways, OP: Yes, Scratch is naturally slow. It’s a natural consequence of simplified block based coding. However, there are lots of great tutorials on YouTube and elsewhere that can teach you how to do scrolling projects. Because of the effort involved, yes, the loading times will be longer and the frame rate probably won’t be as good, but once again, natural consequence. As time goes on, you’ll learn to optimize your code more and have things run better.

Bacteria999 wrote:

I don't think you understand how the code works. Compacting all those scripts into just one block would not make it faster to load.

actually, due to the way scratch runs it would make the project faster

No support, not everything can be premade; imagine this:

Also, please don't type every word with a capital at the beginning; it's really annoying and hard to read.

NanoRook wrote:

Making snide “clever” comebacks isn’t how you post feedback in this subforum.

Judging by how most other people talk here, yes it is

Bacteria999 wrote:

TheBlueScratchCoder wrote:

Do you realize the cost of Griffpatch_tutor's Code? lots and LOTS OF L O A D I N G…Scratch constantly puts you at a position where you are always saving space and decreaseing loading time whenever and wherever you can and games on scratch suffer the most

I don't think you understand how the code works. Compacting all those scripts into just one block would not make it faster to load.

Actually, it would, since it wouldn't need to load all the individual Scratch blocks.

That being said, I still don't like this suggestion. Cameras aren't that hard to program from my experience; you can just make variables for the camera X and Y and then subtract those from all coordinates. griffpatch made a suggestion to allow sprites to scroll off the screen which I would link but don't have the URL for. If you need to do it right now then just draw a transparent, horizontally and vertically symmetrical shape which is centered on the costume and larger than the costume itself.

At this point it isn't even about how scrollers make your game load even longer anymore it's about how scratch doesn't use some way to save projects a better way You could for example do it like this

So when you save your super awesome scrolling game with no limits on scope the process is to compress the whole thing and make the file size as tiny as possible

Now when someone starts up your super awesome scrolling game with no limits on scope the first step is to decompress the whole thing
and do a block check this basically tests all the blocks in the project to make sure the blocks don't glitch out

I'm a genius Am i right?

TheBlueScratchCoder wrote:

At this point it isn't even about how scrollers make your game load even longer anymore it's about how scratch doesn't use some way to save projects a better way You could for example do it like this

So when you save your super awesome scrolling game with no limits on scope the process is to compress the whole thing and make the file size as tiny as possible

Now when someone starts up your super awesome scrolling game with no limits on scope the first step is to decompress the whole thing
and do a block check this basically tests all the blocks in the project to make sure the blocks don't glitch out

I'm a genius Am i right?

Scratch projects already use zip compression and it's really easy to prove this for yourself: Just take a Scratch .sb3 file and change the file extension to “.zip”, then open it in your program of choice. You'll see all of the block data and assets from your project right in front of you. Compression isn't just some magic thing which can make huge files tiny. Even it has a limit, and under some circumstances some compression algorithms can even make your files bigger.

(Also, if your decompression algorithm needs a function to check whether or not it decompressed properly then you're decompressing wrong. What do you mean “blocks don't glitch out”? Scratch blocks physically can't return errors.)

the2000 wrote:

Compression isn't just some magic thing which can make huge files tiny.

well that depends on how much quality you are willing to sacrifice, its not magic but it can make huge files tiny