Race the outside of the pipe.
This is where bugs, ideas and feedback for HyperPipes are collected. The game's source code lives elsewhere — this repo is just the tracker.
- Click Report a bug.
- Pick the template that fits.
- Fill it in and hit submit.
You need a free GitHub account — that's the only requirement, and it's the same account you'd use to comment on anything else here.
| Template | Use it when |
|---|---|
| 🐞 Bug report | Something is broken, wrong, crashed or froze |
| ⚖️ Feel and balance feedback | Nothing's broken, but it's too hard, too easy, or doesn't feel right |
| 💡 Idea or feature request | You want the game to do something it doesn't |
The single most valuable thing is how to make it happen again. Everything else is a bonus. But if you have them, these help a lot:
- A screenshot. In game, press H to hide the HUD, then F2 (or click
the right stick, R3) — the shot saves to your
Pictures/HyperPipesfolder. Drag the file straight into the issue box to attach it. - Which track and mode you were on, and the difficulty.
- Keyboard or controller, and which controller.
- Which build you were playing — the date you downloaded it is fine.
Don't worry about polish, or about filing something that turns out to be already known. A duplicate costs me ten seconds; a bug nobody mentions can survive for months.
Every report gets read. Roughly, they get sorted like this:
| Label | Meaning |
|---|---|
bug |
Confirmed as something broken |
feedback |
Balance, feel or difficulty |
idea |
A feature request |
cannot reproduce |
I couldn't make it happen — more detail welcome |
fixed |
Done, landing in the next build |
wont fix |
Deliberate, or not worth the trade-off — I'll say why |
If an issue goes quiet it isn't ignored, it's queued. Feel free to nudge it.
HyperPipes is made by one person, and testers are the only reason it gets better. Genuinely — thank you for taking the time.