My browser / operating system: Windows NT 10.0, Chrome 78.0.3904.97, No Flash version detected
hello fellow scratchers. I have seen the worst bug in scratch I ever seen!! look here HERE yes,

if (item ( v) of [list v] :: list) then

end

look in the PROJECT

For those who don't want to look inside the project, basically, he's demonstrating that

<(item ( ) of [list v] :: list) and (item # of ( ) of [list v] :: list)>

can fit in boolean slots.

PkmnQ wrote:

For those who don't want to look inside the project, basically, he's demonstrating that

<(item ( ) of [list v] :: list) and (item # of ( ) of [list v] :: list)>

can fit in boolean slots.

Yes thank

Wow !

ok for anyone not believing or thinking that I am a JSON hacker but no try this your self. crazy huh.

[/qu ote]

a

a

haydenledean wrote:

Wow !

please answer with multi-words. Please

coolkidguything wrote:

haydenledean wrote:

Wow !

please answer with multi-words. Please

don't spam

I actually like this bug.

Victoriix wrote:

I actually like this bug.

bugs are bad and this bug is a JSON bug!!

My browser / operating system: Windows NT 10.0, Chrome 78.0.3904.108, No Flash version detected

I saw your project, and there were lots of bugged blocks. From the Scratch editor's point of view, they don't even make any sense.

I tried adding an item to the “Sprite1: bugs” list which contained the text “true”. Then when I clicked on a block that would stay highlighted forever, it stayed highlighted for a second. “ Waiting until ‘true’ ” doesn't even make any sense

This shouldn't even be a thing.

whaaaAHHHHH WOW. How??

(open mouth to gape at you)

LuckyLucky7 wrote:

My browser / operating system: Windows NT 10.0, Chrome 78.0.3904.108, No Flash version detected

I saw your project, and there were lots of bugged blocks. From the Scratch editor's point of view, they don't even make any sense.

I tried adding an item to the “Sprite1: bugs” list which contained the text “true”. Then when I clicked on a block that would stay highlighted forever, it stayed highlighted for a second. “ Waiting until ‘true’ ” doesn't even make any sense

This shouldn't even be a thing.

that's how society works *haha*

shadowsapphire wrote:

whaaaAHHHHH WOW. How??

(open mouth to gape at you)

haha

This Scratch Bug is the Worst

I don't think this is a bug at all as Scratch behaves exactly as you would expect for boolean operations - as might be used in C++ for example.

In the case of using “item n of list” it will return TRUE if there is an item n. If there is not, in other words if n is 0 or more than the number of values, then it will return FALSE. This is completely logical and is a quick way of checking both failing conditions at once.

In the second case of using “item # of n in list” it will return TRUE if n is in the list, and FALSE if not. Again this is completely logical.

You could probably achieve both of these more easily using other blocks, but basically there is nothing wrong with having these in boolean slots however illogical it may seem to a non-programmer. Yes the shape is wrong, but the logic is fine.

vinntec wrote:

I don't think this is a bug at all as Scratch behaves exactly as you would expect for boolean operations - as might be used in C++ for example.

In the case of using “item n of list” it will return TRUE if there is an item n. If there is not, in other words if n is 0 or more than the number of values, then it will return FALSE. This is completely logical and is a quick way of checking both failing conditions at once.

In the second case of using “item # of n in list” it will return TRUE if n is in the list, and FALSE if not. Again this is completely logical.

You could probably achieve both of these more easily using other blocks, but basically there is nothing wrong with having these in boolean slots however illogical it may seem to a non-programmer. Yes the shape is wrong, but the logic is fine.

well if that is true it's not for beginners for example and I reported this bug to the ST and they look that they understand