Hi tarr11, thanks a lot for the in-depth feedback, this is hugely helpful for us. I had actually read your blog post when it was posted, and we got a lot of hel

Hi tarr11, thanks a lot for the in-depth feedback, this is hugely helpful for us. I had actually read your blog post when it was posted, and we got a lot of helpful information out of it. Here are some responses to the problems: * When you the browser loses focus, do you mean the code editor or the entire browser? Also, have you kids had any problems with backspace taking them to the previous page? We're trying to diagnose the latter problem and can't reliably reproduce it, but know that it's causing users a lot of frustration. * Syntax is actually our hardest problem for new players, and we're considering ways to make it easier for people to get into the game. One idea is to shorten the method names (say to this.attack(); rather than this.attackNearbyEnemy();) enabling drag and drop or click and insert from the spell editor, etc. Do you have any specific recommendations for changes we might make? * We're definitely shielded from the distraction-quits since our UX testing sessions tend to be either paid or semi-compulsory (classroom time), but I imagine this is a big problem. Do you find that there's a point of reliable minimum interest among players? Say during a particular level or challenge? Again, thanks a lot for so deeply engaging and getting us some areas to work on. If you are interested, we'd love to have someone as communicative and engaged working on the open source when it gets released (hopefully in the next week or so)!