Hmm, so the “blocks stuck to my cursor” behavior means there was a crash in the blocks workspace. In this case, it looks like somehow the underlying data for the tilemap was corrupted which causes the tilemap editor to crash when you click it.
The warnings next to the overlaps blocks are also pretty odd–the
img`chest2` text should be something like
assets.tile`myTile` , which we know to intelligently render as the image of the tile. I haven’t seen someone get into this state before! Was the student going back and forth between text and blocks? Or the assets view and blocks?
Unfortunately I don’t see the art in this shared project at all so it doesn’t seem recoverable from this link. If your student still has their sprite art and tilemap on their local machine, they can use ctrl+A and ctrl+C to select the entire tilemap and copy it into a new project to try and save their work.