PyWeek - |Gunboy - feedback

Not much control (if any) over the character.

...

Unfortunately I couldn't quite figure out what to do even after reading the instructions
(which I was glad to see) twice. How does a powerup help me destroy a gun exactly? Anyway, you're
new to this and your goal was to learn something. I'm certain you've succeeded at that goal, so
this is good. Looking forward to next time!

Not bad for the first game you've ever written.

It seemed like there was no way to destroy the cannonns I got the red thing and immediately walked over all the cannons but the never disappeared. The background was odd and it could have used some sound effects.

How do you destroy the cannons?

Very strange game...

Not a bad first attempt. Once you get the feel for things it gets much easier and the games get better.

not much of a game but it ran well without problems :-)

I had a hard time exiting - the quit button didn't work some of the time, and closing the window didn't work.

Not exactly sure what to do here, the readme says to destroy the cannons with the red powerup, but I can't figure out how. :(

nice idea.. but the execution was bad.. the graphics could have been done better.

Not quite sure what to say. I got bored after a minute of very easy bullet dodging, so tried to crash into the bullets. Then I won. How did I win? I don't know.

I couldn't figure this game out because the instructions were limited. The game seems complete though, however, so it's a decent effort for someone just starting.

Hey! Well done on your game. I'm sure you know all of your game's faults, but I'm going to try and capitalize about the things that you did right.
I really like how you kept a small scope on the project. So many times, people try to plan for more game than they can handle, and I think that by doing something as reasonably sized as you chose on this project, that really helped.
Going along with the above, I'm glad that you got both win and lose conditions in the game. That's the first step in making a complete game, and that gives you something that you can build on. That's great!
Also, good job keeping up on the documentation. The readme was very helpful and complete, and that is good to complete.
All told, good job! I look forward to seeing how you grow and develop as a programmer -- despite what it may look like on the surface, I really think you did a *lot* of things right with this PyWeek, and you've really got a fantastic base of habits to build from in the future.

Keep learning, I'm glad you figured out collision detection.

simple

I'm sorry. I thought it was terrible.

I found this game hard to play.

mmmm....

Cool you did this game without all source directly in the main.py file whithout even a function! Thats the way to go in speed coding competitions :)

.

Better luck next time. :)

Well, it's playable and worked easily off the box, which is better than with some of the other games, but I wouldn't call it very much fun. The easiest way to win seems to be just getting the red powerup and then leaving the game running until you hit all the bullets.

Yeah, no. I looked through the source code and it appears you blitted everything to the screen instead of using the sprite classes, which is why everything flickers so much.

Also, I got the red powerup, but had no idea how to actually blow up the cannons.

For a first game it looks good, but this game definitely needs some more developement ;)

Hey, thanks for being a part of pyweek...

I tried your game out but didn't find it very much fun to play. I read through your diary entries and it looks like you've been fighting some issues with PyGame. Tough break, man.

Being that I'm looking at a game that you probably didn't finish, I'll try and keep my suggestions to things that were probably done:

1. You put a one pixel thick black line around your sprites. This makes things look overly sharp. If you look at some of the nicer entries, they put thicker outlines around the graphics which gives a cleaner look, but also allows them to round the corners a bit.

2. The big man that was repeated over and over again looked like part of the foreground. Consider doing muted colors for the background, or something to give it some depth.

3. The games that are fun to play have some way of indicating what you need to do. For instance, if the character has a chopper on his head, you should probably try to get him to fly. Others have explicit instructions.

4. The games that are fun to play often indicate why you want to play. In one game it was to escape the bad guys after you rescued your kidnapped cat. In another, it was to save your friends by escaping from a volcano. A game like yours (mine had this problem too), I start it and I'm like, "why the **** do I want to dodge these things? What's the point?"

Like me, the first time wasn't all you had hoped for. I know next time I'll set aside time at the beginning for a menu, a scoreboard, fonts and maybe some music. These are basic things that are in most games and being able to code these in a short period of time will be transferrable from one pyweek to the next. I hope to practice a bit and be able to do these in under an hour.

Thanks for making this game and contributing it to pyweek!

Err... well it confused the hell out of me but definitely good for a first shot.

Pretty nice for a first-time game.

Very good for a first time. My first was terrible, glad you did better.

Flawed presentation, not very much fun, seemed incomplete.

Umm... Not sure what happened here.

Hmmm, WTF?

didn't find how to destroy the cannons

Well, it is somehow innovative.

Didn't really understand how the cannons were destroyed.

I read the instructions, but the game just isn't fun. Also, it was a bit flickery.

Way too easy, until you reach a certain time, and the 1st cannon becomes impossible to avoid.
This game is like Frogger only without enough obstacles(more bullets?) or
control(up/down). Anyways, learning aa language is tough. I give you a 91 for effort.