WARNING: Test it out before using, it isn't very consistent ---HOW DOES IT WORK? First, the main script resets the timer, and runs the test, and this loops forever. Secondly, under the "test" message hat block, it resets the timer again, it waits a certain time, then sees if the timer is over that certain time. This sounds stupid, but remember, the timer resets. And, as found out by @ego-lay_atman-bay , (whose system was my base so thanks to them) when we look inside a project, all code stops running, but the timer still works. What that means is when we look inside here, the timer has a chance to go over the required time and set it off (so it is basically just a lag detector). Finally, when it has detected, you can put anything you want to happen under the "seen inside" message hat block. ---Update log: v1.1: Just added improvements to the code. ---Credit: CREDIT IF USED AND YOU MUST IT'S NOT OPTIONAL. ---Other stuff: Shall i make scratch crash when you see inside >:) I'm proud. It's semi-detector-bug-proof so don't try. It'll reset it but when you click it triggers.
