File corrupting bug / error list / prevent saving?

[mchlnix]

Dario: There is a serious bug that corrupts the file, so that the test with the emulator fails and if it fails it means that if the user gives the save command it would irreversibly corrupt the file.
I think for this reason it is necessary to have two lists of errors because it would serve to report errors during the game, graphics errors but which do not cause damage if you click save, graphics errors and generic reports also quite important but not risky, a list that lights up in yellow, with the yellow triangle, another one that is always off and rarely lights up and red that signals a serious and risky problem for the file, a list that, if active, blocks saving by the user. There are two or three cases, but for now I'll tell you one and then I'll tell you the others, that's why this novelty is needed.

The risky bug could compromise the file and that doesn't allow the test with the emulator because the data are corrupted even if they are in the ram, this is what happens when you want to put a white, orange, orange "block platform" in a plant level, green or blue above an underwater ground, thinking it's the same because only the color changes is an error that involves an important and dangerous bug, whoever knows about this could make this mistake and create irreversible damage to his rom file. This is one of the few similar comosco that deserves a different list and that blocks saving, I would do it next, changing the brightness of the current list to yellow and leaving red for the serious errors list.

Another bug is in the world level 4 object, the giant wooden block like other similar ones, during stretching they multiply the initial object and then add the enlargement is correct, it moves normal, this means that if I have three blocks horizontally and I want to widen the first step will be an addition of three more blocks on the right and then it will be normal, the addition or subtraction will always be one in the next movement.