I have never had this problem before, but Scratch has been a little glitchy the past few days (for me, at least). Well, here it is: https://scratch.mit.edu/projects/146123658/

when green flag clicked
wait until <(Love and Fave)=[true]>
set [cops911 v] to [happy]

That's a little thing called the floating point decimal.

It works now…wierd

when green flag clicked
wait until <(Love and Fave)=[true]>
set [cops911 v] to [happy]

I suspect you hit this Scratch bug in modified operator blocks.

It means that if you have an operator block that you've changed (i.e. you right/shift-clicked and chose a different operator symbol, e.g. changing it from add to subtract), then when you duplicate that block (or any script containing it), it will ‘flip’ back to showing its original operator symbol – but it will still *behave* as the operator you changed it to.

In other words, what it shows for the operator symbol is ‘out of sync’ with what the block actually does.

Fortunately, it's only temporary – when you reload the project, the operator block shows the correct symbol (which is probably why it started working again).

TheLogFather wrote:

It means that if you have an operator block that you've changed (i.e. you right/shift-clicked and chose a different operator symbol, e.g. changing it from add to subtract), then when you duplicate that block (or any script containing it), it will ‘flip’ back to showing its original operator symbol – but it will still *behave* as the operator you changed it to.

YES! I was also having problems with it changing to something else, but when I tried to change it back, it changed a completely different operator that I didn't even click on.

when green flag clicked
wait until <(Love and Fave)=[true]>
set [cops911 v] to [happy]