Scratch

Generally I think it runs faster but there comes a point where scratch doesn't like having a script that long and can slow down in the designer. Or at least it has that point for me.

scimonster wrote:

Depends what you're shooting for.
If you want to use as few scripts as possible, do the long one.
If you don't really care, I say it depends on your computer speed and your patience.

For the last one:  Wha?

I'm trying to accomplish performance rather than a minimal number of scripts.

The thing in particular that I'm doing is having multiple classes/roles all crammed into the player. It is about 18 if-blocks per class, but assuming if there are like 10-15 classes, that's a bit to have constantly running in the background- just from simply walking...

I can separate each set into several smaller bunches, which would be triggered via broadcast. So that not all that extra code is having to be ran constantly.

But I'm unsure which one uses less processing, or if there is even a difference.

OK.
Last time I made a 1s1s, the designer got REALLY slow. I have never had that problem with multiple scripts.

I find multiple scripts easier to find and fix bugs, but that is just my opinion.

Xzerie wrote:

I'm trying to accomplish performance rather than a minimal number of scripts.

The thing in particular that I'm doing is having multiple classes/roles all crammed into the player. It is about 18 if-blocks per class, but assuming if there are like 10-15 classes, that's a bit to have constantly running in the background- just from simply walking...

I can separate each set into several smaller bunches, which would be triggered via broadcast. So that not all that extra code is having to be ran constantly.

But I'm unsure which one uses less processing, or if there is even a difference.

Breaking it into broadcasts will run considerably faster. Each 5 if loops added to a forever loop can reduce the Frames Per Second by as much as 1 - 4. Having broadcasts will cut out a lot of the lag.

Also not, never have a small script that simply says:

When <greenflag> clicked
forever
if foo
bar
end

Instead, replace the if with a wait until block. For whatever reason, this speeds the program up immensely.

I try to put them in one script, but it really depends on what you're trying to achieve... for example, two scripts running at the same time can check for two things at the same time but two if blocks in a forever in one script can only check for one thing at a time.

Xzerie wrote:

henley wrote:

Personally, I think that several medium sized scripts would do well. Several long ones would be too laggy.

And too many scripts in general is laggy. Example.

What I noticed was that they were using a lot of [[green flag clicked] blocks], then a long list of things in some [forever] blocks.

How do you suppose I change that? By not making the project?