PyWeek - Coffee Maker Time, Please wait. - feedback
Fun | Prod | Inno | Disq | N/W | Comments |
---|---|---|---|---|---|
2 | 2 | 3 | I think this could become a fun educational game, but it needs a story or something to make it engaging. |
||
2 | 2 | 2 | Interesting game. Not sure how to decide whether a match will be correct apart from adding numbers! Many thanks! |
||
2 | 2 | 2 | This could make a good educational game, if there were more incentives to keep the users attention. Even simple things like arithmetic can be addictive with the right rewards. Just like in Pachinko machines |
||
2 | 1 | 2 | This game is a bit too simple. In the other Pyweeks, your games had some particular aspect that was interesting, but in this one, I find none, unfortunately. Also, visually, it's not attractive. I think the problem is that the central mechanic is not very interesting, at least for me. I hope next Pyweek you find something more interesting. |
||
2 | 2 | 2 | It took me a little while to figure out what I was supposed to be doing. There didn't seem to be much point either. |
||
2 | 2 | 2 | Game needs a little more of everything -- especially extra elements to the game play and eye candy. |
||
2 | 3 | 3 | The game is quite repetitive. A faster increase in difficulty would add variety and make it more fun - e.g. add an extra number or make the calculation more complex at every level and increase the size of the number list. Colour-coding the numbers would make them stand out more -- then the player could spend more time working out the calculation and less time trying to tell the numbers apart. Of course, you could drop the colours at a higher level to make the game harder again. |
||
2 | 1 | 1 | I could commit numbers twice, match counter goes up. Shouldn't a commit count only once? |
||
1 | 1 | 1 | "Right but not match?" |
||
1 | 2 | 1 | It needed some feedback to be more than just working through the possible combinations. |
||
3 | 2 | 2 | There are a few implementation problems with this game, but the general idea is sound. The most obvious issue is that the title screen gets displayed over the game screen. These should be separate screens that the game swaps between rather than just drawing one over the other. |
||
2 | 1 | 1 | It's perhaps your most intuitive game so far. Although "right, but not match" is cruel, especially on "a + b + c" levels. |
||
2 | 3 | 3 | . |
||
2 | 1 | 4 | Better production could have improved the overall user experience of the game. |
||
1 | 2 | 2 | Game requires pyglet but this isn't mentioned in the documentation. The most annoying feature of this game: getting the right answer is not enough! Other than that, it's a pretty standard arithmetic game. Not my idea of fun (I |
||
1 | 2 | 2 | You find a set of numbers that work. Then it tells you to find another one because the one you chose isn't the one it wanted. Bleh. |
||
3 | 2 | 3 | This game was ok. I like math games. |
||
3 | 2 | 3 | I didn't understand why my answer was sometimes "right", sometimes "right but no match". But very interesting game. |
||
2 | 2 | 2 | I don't understand what "match" means. |
||
1 | 1 | 3 | That made me think, and I'm pretty good at arithmetic. I wasn't expecting to have to think that much. I also like that your game has a clear goal and is easy to understand. It's an improvement over your previous games in that sense. Thank you for that. But I think you should make something with graphics and sound. It would probably be more fun. |
||
1 | 1 | 1 | add the numbers and wait for the countdown to reach 0. milker, i know you can do better than this. |