I've also thought of this idea, but think about the myriad of games available on Scratch. It would be hard to tell whether a competitor made his game from scratch (no pun intended) or not. Or if a coach helped out. Or anything. Placing everyone in a room and making them crank out a game in 50 minutes is the most fair way by a long shot.JoJojohnson wrote:As a graduating division B student, I've been watching Game On with much interest. I plan to be a video game programmer and have worked in scratch for several years. In my opinion though, I feel as though this event took the wrong approach. I find the idea of making a program and a handful of assets/sounds in 50 minutes restricting. I've seen some projects and though they were good, I'm sure that they could be better if they had more time. So, I thought I'd make a recommendation.
I think that the event should be handled more like a build event than a study event. I think that students should be presented a theme in advance so that they have more time to make their program. Then at the competition, the teams could present their projects to the supervisors individually, during which the supervisors would score the work based on the set criteria (maybe this time could be split into showing the code behind it and the supervisors playing it). This would allow teams to produce programs that have been optimized for the event.
Now when it comes to themes, The frequency of theme changes would most likely have to decrease to provide the time needed to make the game. How many themes would there be? I can't tell, but I was thinking that three or four would be a good number, changing with the level of the competition(invitationals, regionals, etc). I will admit it, having eight to ten months to make a game that would probably be ten minutes long at most is a pretty long time, so the theme should change at least once.
Of course there are several issues with this idea(mainly being that scratch is not the most powerful programming engine, and confirming that the assets used were made by the teams in the scratch editor would be much harder), but it still seems like a better idea then what we have right now. Either way, I am just tossing ideas around and seeing what people think
What I do think would be helpful is a redesign of the rubric so there is little or no ambiguity. Especially the criterion "complex movement." What does that even mean? Like is bobbing up and down and circling "complex?" The rubric from the 2015-2016 season just left too much for the judge to decide.