While you're in the head of a patient, you must turn around and click on the throat to travel down the stomach. When you're in the stomach, you need to hold the button to eat/steal the food from the patient. Ater that, you need to find a new patient to infect. You just have to go up to them and then click on them through the mouth.
I probably spent like 5 minutes trying to get rid of all of the dust bunnies before I realized they'll keep respawning. I really like the Desktop Computer model, it's very detailed!
I just played the version 0.4. I love how almost everything has a sound effect (jumping/sweeping into dustpan/level complete/crouching/etc). The Green dust bunnies in Level 8 are an interesting challenge, I ended up having to sweep up 10 instead of 6! Is there a limit to how many green dust bunnies can be created? One small suggestion is to have the buttons play a sound when you select/highlight them. I found this video to be the most helpful to do this through code:
I think having random spawn points is fine. I don't think it extends the gameplay that much, but it does add variety, even if only a tiny bit. I like the music and have no problems with it being on shuffle. The level where you're penalized if a dust bunny escapes sounds quite interesting, I can't wait to play it! I don't play Itch.io games on my phone, however sometimes, I'll take a look at a game while I'm out and I wonder what the gameplay's like because the creator didn't upload screenshots and didn't create a mobile html version. I say this to encourage you to add those optional on-screen controls that you're talking about. I appreciate you 2 appreciating my feedback.
I just played the newest version and that's actually where I wanted to start. I don't know how far you want to take this game, but displaying the version number in the settings, or just in the corner of the game, would make it easier to find out which version of the game the player is playing. As for my other feedback: - Tables and chairs wouldn't respawn when I knocked them off of the platform. I would complete the level in a minute or less, but I never saw them come back. - I think the respawn point should be anywhere but on the dustpan. When you respawn, you're probably gonna rotate around, so you might knock dust bunnies out of the dustpan. I know they're already accounted for, but it could be worrying for a new player. - In Level 5, there was a dust bunny that kept respawning above the cracked tile. I was able to progress by crouching and then smacking the dust bunny by un-crouching to launch it away. This act of smacking falling dust bunnies could be an interesting mechanic tho - I played level 6 with the bouncing/sensitive dust bunnies and it felt good, it almost feels like I'm playing golf and I have to be precise with my "stroke" - I like the somber music in level 7. It fits the lonely space theme perfectly
I just played the newest version, and the mouse look speed is working great for me. I haven't noticed anything different about the scale of the game, so I guess that was a total success. Great job keeping everything together. I enjoyed knocking down the furniture to get to the dust bunny in Level 7. I think it would be nice if the furniture reset back to its normal position when you restart the level, so I can knock it down again. While not necessary, replacing the keyboard/controller prompts with actual images would look good. These are some public domain prompts: Input Prompts · Kenney. I think you should keep going. I can see Dust Bunny Sweeper becoming a complete (and maybe commercial) game one day.
I like crouching because there's no longer a broomstick in the middle of the screen.
Since there's no real need for the furniture at the moment, I think when you knock it off, it should fall until you can't see it anymore. Your actions seem more permanent that way. If there is going to be a use for furniture definitely respawn it after a few seconds of falling.
I tried the latest build and I set my mouse speed to 1 and it was still kinda fast. 10 was incredibly fast, as it should be. If it's not too fast on your end, then there could be a WebGL bug. Perhaps you could divide the speed by 10?
