You can do this:

say [text] for (-2) secs

Which doesn't make any sense. You can't wait negative seconds.
Block

wait () secs

will prevent you from adding negative numbers.

It is probably good idea to stay consistent.

Strange… when you do either the think or say blocks, it will show the text and then immediately hide it, I think maybe it is showing for one frame (works both in normal and turbo mode).

RED-001 wrote:

Strange… when you do either the think or say blocks, it will show the text and then immediately hide it, I think maybe it is showing for one frame (works both in normal and turbo mode).

It probably have the same effect as it was 0.

The say block should not do anything if it's at 0… maybe that is the real bug here.

i can even put words in it if i copy paste

Marc92020 wrote:

i can even put words in it if i copy paste

You can do it in every type of white input. That's also a bug.

Hmm… I don't see why this happens. I think it would be a good idea to patch it.

Marc92020 wrote:

i can even put words in it if i copy paste

There's another bug that should be patched.

Can replicate

Yeah but you can't put words in 2.0

There shouldn't even be a negative input either on the number pad on mobile! Maybe this isn't a bug but the Scratch Team just forgot to implement a few things.

This also happens to the glide block.

And even this block?