That's just the way Windows is.
Blockland is busy trying to load and process everything. Clicking it tells Windows that you want to interact with it. But since it's so busy doing a lot of work, it doesn't give a response to the click. Windows then tells you it's not responding. This doesn't mean Blockland stopped working, and that's not what the error implies either. It's just not responding because it's busy. You don't always have to close a 'not-responding' program. It will continue to work and the error will even go away when it resumes being responsive.
