define proc
proc

// You can use instead of the two above broadcast blocks, they work the same way
add [] to [list v]
delete ( v) of [list v]
<[ v] contains [thing] ?>
if <> then

else

end

Jonathan50 wrote:

Please read the OP. The goal is to find the fewest amount of blocks you can recreate any Scratch project with (and it's nearly two years old!)

 
change x by ()
=
move () steps

when I receive [loop v]
...
broadcast [loop v]

badatprogrammingibe wrote:

Jonathan50 wrote:

Please read the OP. The goal is to find the fewest amount of blocks you can recreate any Scratch project with (and it's nearly two years old!)

I was just showing what was needed to create a turing machine.
I never said that was all you need for every project, but I just thought that could help someone

when I receive [loop v]
...
broadcast [loop v]

badatprogrammingibe wrote:

define proc
proc

// You can use instead of the two above broadcast blocks, they work the same way
add to

• delete ( v) of < contains ?>
  if <> then
  
  else
  
  end
  
  
  These 6 blocks should be enough to implement a basic turing machine.
  If scratch had proper bignumber support you could do it in 5.

ScratchLover1029 wrote:

so

 
change x by ()
=
move () steps

?

define workaround for move (steps) steps in direction (dir)
go to x: ((x position) + (([sin v] of (dir)) * (steps))) y: ((y position) + (([cos v] of (dir)) * (steps)))

_nix wrote:

ScratchLover1029 wrote:

so

 
change x by ()
=
move () steps

?

Yup, almost – but the difference is that, if your sprite is pointed in a different direction, move () steps moves them forwards according to their direction. So the complete workaround is a bit more complicated:

define workaround for move (steps) steps in direction (dir)
go to x: ((x position) + (([sin v] of (dir)) * (steps))) y: ((y position) + (([cos v] of (dir)) * (steps)))

(Note that I also used “go to x: y:” instead of “change x by” and “change y by” separately – if I used them separately, and the pen down block is used before “workaround for move () steps in direction ()”, then a jagged line would be drawn instead of a straight one.

...

((((((((((((((((((((((((((((((((((ScratchLover1029))))))))))))))))))))))))))))))))))

what block should we recreate?

define block

...

block

ScratchLover1029 wrote:

define block

...

block

CodingWorker wrote:

The entire ‘More Blocks’ section is unneeded, as if you can define your block with Scratch blocks, you can copy and paste those Scratch blocks to where you wanted your custom block.

define play sound from list at (FREQUENCY) Hz
set [play v] to [0]
repeat (length of [sound v])
change [play v] by [1]
if <(item (play) of [sound v])<[0]>::control
set volume to ((item (play) of [sound v])×[-100]::operators)%
play sound [negative sample v]
else
set volume to ((item (play) of [sound v])×[100]::operators)%
play sound [positive sample v]
end
wait ([1]÷(FREQUENCY)::operators) secs

jokebookservice1 wrote:

PullJosh wrote:

CodeLegend wrote:

set rotation style (keep track of direction and rotation style and simulate rotation style)

Pretty sure this one is for flipping left/right.

You can just have two costumes, but I suppose that increases the file size so you can't perfectly emulate a very big project that is close to the file size limit.

ihgfedcba wrote:

CodingWorker wrote:

The entire ‘More Blocks’ section is unneeded, as if you can define your block with Scratch blocks, you can copy and paste those Scratch blocks to where you wanted your custom block.

But what if you have recursion? Then that would need infinite code?