Catch with Creative Coders

Last week I presented the Catch Game project to my group of coders that meets at the library once a month.  This group has a different vibe than my weekly Code Club.  Some of these coders are a bit older, some were in my Code Club when they were in 4th grade and we have new members each month.

We are also using online Scratch accounts on the library Chromebooks instead of Scratch 2.0 offline editor.  I’ve set up a teacher account and a class. Members can use one of the pre-set 15 student accounts or their own Scratch account if they have one.

Each month I set up a studio for them to add their projects. Then we can all try out and play their projects at the end of the session.   I’ve had a bit of trouble with adding studios.  Sometimes they have not been available to the students to see or to add their projects, but I think I’ve figured out why.  There are two ways I can set up a studio in my Scratch Teacher Account – under My Classes and under My Stuff.  If I can set up a studio inside My Classes, that will automatically allow my students to be curators of that studio.  If I set up the studio under My Stuff then only I am set up as a curator of the studio.  Interestingly, I can see all of the studios from My Studios. The difference appears when I look in the Curators tab.

Screen Shot 2018-01-13 at 10.16.53 AM.png

We emphasize creativity in their project design and encourage sharing and playing each other’s projects at the end of each session. I like to display each one on the big screen as well, as we want to celebrate each coder’s hard work. So I was a bit frustrated when no one could see the studio I set up.  One student helped me out on Monday by setting up a studio from his student account and adding to it all the shared projects.

 

Screen Shot 2018-01-13 at 10.21.57 AM

Catch the snowflakes

 

 

Screen Shot 2018-01-13 at 10.34.17 AM

1000 bonus points for catching the soccer ball!

 

They are a pretty creative bunch and didn’t have much problem with the project.  One student seemed to strive to annoy everyone with “creative” sound effects.  Others were making the screens fill with falling pugs or watermelons.

One student asked about keeping a high score list.  I think I’ll need to look into that request.  I know I’ve seen instructions about that somewhere.

Advertisements

Checking Up on Individual Projects

We have two weeks until our Showcase of Projects and I’ve been checking in with all of the Code Club members to see how they are doing.  There are no team or pair projects this round which I find surprising but this year’s 4th-graders are very much unique individuals.  I tried putting two students together on one project, but they just couldn’t work together.  So they each have a similar project.  This does mean that there will be a lot of projects to present at the Showcase.

 

Screen Shot 2018-01-07 at 2.50.43 PM

Keep away from Bendy

 

The character Bendy from Bendy and the Ink Machine game is featured in a couple of chase games.  How these nine-year-olds know about this horror game, beats me.  I hadn’t heard of it, but then again, I don’t like scary things.

 

Screen Shot 2018-01-07 at 5.09.06 PM

Virtual Pet Dragon

 

Most of the students are in good shape.  The two virtual pet projects just need a few tweaks. The trivia and math quiz projects seem fine.

 

 

 

Screen Shot 2018-01-07 at 2.47.26 PM

Answer the riddles 

The Riddler is well coded, but I think I need to show this coder how to make his own blocks for the “you answered it wrong”.  He has duplicated his code in each “else” loop. Perfect opportunity to teach code reuse or refactoring. Now I finally have a reason to show them how those dark purple blocks work.

 

 

Screen Shot 2018-01-07 at 2.49.42 PM

This code shows up in each of his “else” statements.  

 

 

The flying cat and maze games could use some more work, but now that I’ve seen the state of everyone’s code, I think we might spend some time this week talking about game testing, how important it is, how to do it well and how to fix the glitches.

Equally important as testing for bugs, is to test for fun-ness.  We want our games to be fun.  Yes, we do.