because there a 2-reply limit unless someone replies.
new blocks!
performance tip if you want to squeeze every bit of performance:
use <t> primitive [reportNewList V] or <t> primitive [reportBoolean V] instead of report (input) in blocks that return thier first input
Why? It’s barely faster at all…
only useful if you are trying to squeese every drop of performance out
… and if you don’t mind that we explicitly don’t promise that those PRIMITIVE block calls will continue to work as they have in the past (as opposed to the regular blocks, for which we do try to maintain backward compatibility).
new blocks:
updates:
blocks with gears are in wip.
the extra category has a different color.
all variables block expect 1 has been moved into the data category.
Do you mean OUTLINE WIDTH rather than OUTLINE LENGTH?
outline width
($gearBig-2 find the average of (42) @<:> ::operators)
Just do:
($gearBig-2 find the average of [num...] ::operators)::define+ report ((sum (num)) / ([length V] of (num)))
To get the sum () block, just drop another block into the arrows of the () + (). If a red halo appears, you are about to get that block.
Why is “true”, “” as a boolean?
Their block is intended to only report TRUE/FALSE if provided a Boolean value, otherwise, even with 1/0, it reports an empty string.
New blocks!
unrelated but can someone convert this
into a scratch list?
here’s the converter:
I’m trying to make a 3d game inside scratch
update: the inputs category was updated, and turn into binary is no longer on wip!
//before (@gearBig-2 turn <t><t><t><t><t> @<@:@> into number::operators) //after ( turn <t><t><t><t><t> @<@:@> into number::operators)
Found a bug with the AM block. It needs to be “less than” and not greater than
new blocks
New blocks