The whole thing runs on real model photos, which is already a weird flex for a browser game. Not renders, not hentai, just this brunette in what looks like a hotel room with bad lighting. She's doing a striptease, but only when you don't crash the PussyCopter into a building. That's the mechanic. You're flying this thing, first person view, through a maze of grey blocks that are supposed to be city streets. The controls have that specific kind of lag where you overcorrect and then overcorrect again and suddenly you're grinding against a wall while a progress bar for some unseen guy's jerk off session slowly depletes.

I spent way too long trying to figure out if the labyrinth was procedurally generated. It's not. Same layout every time, or at least it felt that way after my fifth attempt. The logic tag is doing some heavy lifting here because there's no puzzle to solve, just muscle memory and pain. The arcade influence is clear, that brutal "one mistake and you start over" energy. But instead of a high score you get... well, the striptease progresses. She starts fully clothed, this brunette with an expression that never changes, like she's waiting for a bus. Each successful delivery to the client, who you never see because it's POV, removes another piece. The strip element is tied directly to your performance. No performance, no tits.

What bugs me is the collision detection on the rotors. The hitbox extends like a full centimeter beyond the visual model. You think you're clear, you're threading the needle between two skysc***, and then the game decides nope, that's a reset. The real model aspect gets undermined by the fact that the video loops are maybe three seconds long. You see the same bra removal six times and it starts to feel like a gif from 2007. Still, for a jam entry with this specific combination of tags, it commits to the bit. The PussyCopter itself is just a poorly drawn helicopter with cat ears. I respect that they didn't explain it.