I thought merging it with origin/master (cs10 origin) would insert everything, but I have no idea why only the date changed and things like the date block and flatend lines didn't go through. Oddly though, the newest additions with the searching for blocks feature is present. I don't understand...I'm sorry--should definitely have inspected it more instead of being excited that there was only 1 merge conflict (the date) and then pushing!

Okay, so I've fixed the rotation/moving sprite issues, and the effects now should apply everywhere. I've JSlinted, and everything is looking tidy--used my discretion though..basically ignored some errors that I didn't think was relevant...but let me know if something that isn't okay. I need someone to teach me conventions! :)

Since this branch is effectively dead I'm going to push to it the recent changes so that I can see better what to c+p onto the new branch. But just in case I need revision history I don't think I should  delete this branch just yet. This is just a heads up that my pull request will come from a fresh fork and please ignore this one 

I agree though, @jmoenig I saw this thread in my email with all these comments and that was a very very scary moment for me as well... I think this is why everyone is making a branch in cs10 and not forking from snap directly, because if something happens like this and then I accidentally push to master on the actual snap repo...that would be very bad...though actually maybe this isn't irrelevant because don't you need collaborator access to modify branches...? Well anyway i liked the idea of having a buffer between my experiments and the real repository :)