PyWeek - kfc - feedback

The game needs a little bit more gameplay, and the ball is buggy sometimes, but the ending was pretty cool. :)

Game felt really buggy. Although I finished the game. I'm confused. Almost everything seems out of place...literally.

THE GRAPHICS ARE VERY GLITCHY, I SEE PARTS OF THE PREVIOUS SCENE ON TOP OF THE CURRENT SCENE, THE BALL PICKUP SOUND IS SO LOUD THAT I'M NOT ALMOST DEAF, THAT'S WHY I'M SCREAMING HERE!!!

The controls and collision system are really wonky, at least for me. I think some sort of obstacle or something could have made the levels at least somewhat challenging in a way that didn't feel unfair. The gameplay is a bit incomprehensible, but I get the impression that's an artistic choice.

Ball has tendency to spazz out on contact with walls.

💯💯

Some weird, weird stuff - which is very enjoyable. The artwork is naive and grungy.

The gameplay of the basketball maze part feels unfinished. Clipping into a wall seems to reverse your controls, which can mean the ball shoots off-screen never to be seen again, and the game needs to be restarted. But there's not a lot of enjoyment to be found in moving from A to B to C.

The boss section, by comparison, feels more challenging. It's just lacking an indication of how you're doing. I could see myself losing lives, and that's bad I guess? But not sure how close I was to winning or what I was actually trying to achieve.

My game went into an infinite loop when the ball went out of bounds. I tried a few times and it happened again so I might not have seen that much of the game.

I liked my prizes I got from each chest: best part of the game. OMG they were so hard to open though, it was like pixel precision required. Were blue un-rendered areas intentional? Also the collision avoidance on the ball was super buggy, I kept flying off into the walls and having to re-start the game. I didn’t understand what was happening at the end.

Some strange collision detection bugs (the ball went far away... then I realized why 'r' is there).

$ python main.py
pygame 1.9.5
Hello from the pygame community. https://www.pygame.org/contribute.html
Traceback (most recent call last):
File "main.py", line 513, in <module>
main_loop()
File "main.py", line 471, in main_loop
pygame.mixer.music.load(getPath("assets/bb.mp3"))
pygame.error: Unrecognized music format

It was OK, but a little dull.

```
Traceback (most recent call last):
File "main.py", line 513, in <module>
main_loop()
File "main.py", line 471, in main_loop
pygame.mixer.music.load(getPath("assets/bb.mp3"))
pygame.error: Unrecognized audio format
```

Kind of glitchy but interesting graphics

Yet another stunning presentation from the madman speedlimit35! You have an interesting art style, and the game gave me an interesting experience as well with it's sound and graphic effects. However, the game did have quite a lot of hitbox glitches, hopefully you can implement a better hitbox algorithm next time!

What a strange story. It crashed at the end, but it seems the game was over after solving the 6 riddle (boss fight). I read your day 2 diary entry, it seems coding came back to you well enough after that. Thanks for making a game, and congrats for finishing Pyweek.

Here is the error which occurred after "game won". I didn't let this affect your score, since I finished the game.

you win
new chest_checklist [True, True, True, True, True, True]
Traceback (most recent call last):
File "main.py", line 513, in <module>
main_loop()
File "main.py", line 494, in main_loop
game.game()
File "main.py", line 178, in game
tileBox = level_one.render_level(tiles)
File "main.py", line 133, in render_level
hi=self.draw(self.tileX, self.tileY, tile[1],True)
File "main.py", line 111, in draw
screen.blit(tile, (tileX,tileY))
pygame.error: display Surface quit