[floppy] Floppy can move outside the top screen boundary

Open Beginner friendly
#41 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
c
Domain
game-dev

Research direction

Start by locating the Floppy game entry point and reproduce the issue by holding Space immediately after launch. Inspect how upward movement and the top playable boundary are handled, then confirm the floppy stays within the area or follows the intended game-over behavior.

Written by the indexing model from the issue text.

Description

Description

When starting the game, if Space is held immediately, the floppy continues moving upward and can move beyond the top boundary of the visible game area.

Steps to reproduce

  1. Start the Floppy game.
  2. Immediately hold Space.
  3. Continue holding Space.
  4. Observe that the floppy can move beyond the top boundary.

Demonstration

https://github.com/user-attachments/assets/537bb1c3-4771-4e46-bef7-7e04902cdf42

Expected behavior

I'm not sure whether this behavior is intentional. I would expect the floppy to remain within the playable area or trigger the appropriate game-over behavior when reaching the boundary.

If this is considered unintended behavior, I'd be happy to investigate it further and submit a pull request with a fix.

Dominant language
C
Stars
840
Forks
101
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raysan5/raylib-games

All issues in raysan5/raylib-games

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.