Sorry for the hassle this has caused you
I've spent a fair chunk of today trying to reproduce this, and I can't. I've built the Fish Food project from scratch (pun very much intended) several times, and it's worked fine every time. I also tried to find timing or edge-case issues to intentionally cause the problem — e.g. flipping between sprites repeatedly while the project was in various states (model running, model not running, after loading from a file, after saving to a file, etc.) and still couldn't see the problem. I've also walked carefully through the relevant source code looking for a potential bug, without finding anything obvious.
I absolutely believe you experienced this — the screenshots make it clear something went wrong — I just can't pin down what's causing it from my end.
My best guess, based on your description, is that it might be a visual issue rather than a bug in the project itself. When you switch between sprites in Scratch, it has to clear the canvas and then load it with the blocks for the new sprite. My suspicion is that the blocks you saw appearing on the food sprite weren't actually attached to it — they may have been a visual leftover from the fish sprite's workspace not clearing properly.
It's worth trying this first: clear your browser's cache. This is more than just refreshing the page - it's deleting the saved copy of Scratch that you have, so you can be sure you get the current latest version.
- In Chrome or Edge: press Ctrl+Shift+Delete (or Cmd+Shift+Delete on a Mac), make sure "Cached images and files" is ticked, and click "Clear data"
- In Firefox: same shortcut, then select "Cached Web Content" and clear it
- In Safari: go to Safari > Settings > Advanced, enable the Develop menu, then Develop > Empty Caches
And then refresh the page.
If clearing the cache doesn't help and you still see the problem, I'm willing to dig into this further — I'm not trying to brush it off. But to have any real chance of finding the cause, I'd need two things, please:
1.
Browser console logs if you're not sure what the console is, this guide explains how to open it in different browsers:
https://balsamiq.com/support/faqs/browser-console/ . If you can open it before reproducing the problem, then copy and paste anything that appears in there, that would be really helpful.
2.
Precise steps to reproduce the problem As specific as possible — what order you're doing things in, at what point it goes wrong, etc. It's possible that you're doing the one thing I didn't think to try!
Sorry again for the trouble, and I hope clearing the cache does the trick.
Dale