PyWeek - CashFlow - feedback
I like the overall idea - even if it seems not very original - and the simple controls. I think more difficulty would have helped. The 0's are a good idea but ultimately not that hard to handle. Maybe more frequent hazards that only remove 5,000 cash. Just one possibility.
Not sure, I think I had to catch all those fast falling things (maybe not all). But I got the feeling that the game was running to fast (could only move far left to far right and back and could not catch any falling object in the middle).
Too fast for me.
Hmm, well I ran into the framerate issue too. The game's ok, but some of the things that you collect are a little odd. The 'drop fire from the sky and die with no escape' is :|, similarly the large coins that actually reduce your score.
I didn't manage to get to 50k, my score kept going down but I couldn't figure out why.
I'm not sure I get the logic of the black thingy: if not taken, the score drops to 0, but if taken, it's literally impossible to avoid dying. So it looks like you just have to pray to not have a black thingy, and winning is just a matter of luck.
(I used the clock.tick fix)
Without "self.dt = self.clock.tick(30)" it runs to fast to be playable for me, with it a bit too slow to be challenging. Kicking out of the game for loosing - but, you didn't have to cut me off.
I'm #1! Me and my green beard got the trophy! There is something happy about seeing a deluge of gold coins...not sure what it is. Thanks for the clock.tick() tip, it helped. Congrats on your tidy little game. :)
It was fun until I noticed that the score was resetting to zero. It was not clear from gameplay why this was happening. I eventually figured it out - choose between score resetting to zero and a barrage of negative points that are impossible to avoid and kill you... not much of a choice :)
It honestly felt like a troll - see if you can get 50,000 points when I keep randomly resetting it to zero mwa ha ha!
I could see it being funner with some tuning though.
Had to change the framerate, but a good solid simple game.
cool but needs some big bens
Was good to see a game got made: but didn’t really seem to be much to do: wasn’t much challenge in it.
I didn't understand the game and had to read the code to understand how to play. I'd strongly recommend you publish a README.
The ding of collecting coins, particularly as you pass through the showers of a zillion coins, is very pleasing.
Overall I think the game is much too easy, once you know how it works.
Good job on finishing PyWeek. Not a bad execution of an otherwise simple and not particularly original game concept, although there were some performance issues with the game, and the game is not very well-balanced; I also had to modify the source to even get the game to run normally. I can't really rate it too highly as a result, but nice work nonetheless.
i played the game on windows machine, looks like the game objects' movement is tied to the framerate and not time. The game was un-playable in terms of fun to play.. the coins would vanish before i realize what was going on.
The game move *way* to fast to be playable. Changed "While True:" to
on line 84 of game.py. So the black thing that appears. If you pick it up it rains down death; if you don't, it resets your progress to 0. And its entirely random
neg_bonus_time_gap = numpy.random.exponential(12000)
I'm not too sure how this game fits the theme other than the title.
Assets don't seem to be made for this competition (which is fine, but is taken into account for scoring).
Coins fall from the sky, and you have to collect them with your paddle, controlled by the left and right arrow keys. It's possible to make fun games starting with these mechanics. However: the coins fall almost instantly, being onscreen for only a frame or three. And your paddle similarly moves almost-instantly, so for all practical purposes it only has two positions: flush-left and flush-right. I was literally unable to ever stop in the middle, despite trying to tap the key as fast as possible.
After a random amount of time, fire tiles rain down across the entire screen and the game is over.
It's possible this game is playable and fun on very slow computers, or on other operating systems. I tried on two different reasonbly-fast laptops running Pop!_OS, which is basically Ubuntu, and it behaved the same on both. My experience: it was completely unplayable and zero fun.
I could only judge the innovation and production so far, but given that playability is part of production, I think I'm being generous saying it was below average. I also gave it a "below average" for innovation, which I feel strikes a balance between "I saw zero that was innovative" and "the game was unplayable so I can't really tell if it did anything new".
I finished a game. It was fun.
Game looks simple and I saw some games like but can't remember.
Game works well, but lacks polishing and levels.
- when I started the game, FPS seems too high. I added time.sleep() in game.py.
- looks like the game crashes sometimes after I pick up a bomb.
There was no README, so you're lucky it ran first time! At first, the game ran unplayably fast (about 600 FPS) so I added `self.clock.tick(30)` to your game loop, and it then worked fine. The only problem was the black circley things. If I hit them, fire came out and then the program exited. If I missed them, my score was reduced to zero. I don't know which was intended, but I had good fun trying both possibilities! The inclusion of music is nice, as are the rotating 'big coins'. It seems like this could have been a pretty decent game if you'd had a bit of extra time (maybe the start of the challenge :-) ).
It's a simple game, but that sound of collecting coins is addictive. :) (By the way, this was going way too fast before the time step fix.)