Fpga Platformer
D 56 completed
Other
unknown / vlang · tiny
15
Files
954
LOC
0
Frameworks
2
Languages
Pipeline State
completedRun ID
#1037170Phase
doneProgress
0%Started
2026-04-15 11:33:29Finished
2026-04-15 11:33:29LLM tokens
0Pipeline Metadata
Stage
SkippedDecision
skip_scaffold_dupNovelty
16.51Framework unique
—Isolation
—Last stage change
2026-04-16 18:15:42Deduplication group #47631
Member of a group with 18 similar repo(s) — canonical #1576798 view group →
Repobility (the analyzer behind this table) · https://repobility.com
AI Prompt
Create a hardware platformer game simulation using Vlang. The game should run on a Nexys4 DDR board, displaying graphics over VGA at 640x480 resolution and 60Hz. I need the core logic implemented across several modules: a clock divider, VGA timing generator, button debouncing logic, a game controller for physics (handling movement, jumping, and gravity), and a renderer. The renderer must draw the player (red), platforms (brown), ground (green), and background (dark blue) with specific draw priorities. The top-level module should integrate all these components, taking inputs from the board's buttons (BTNU, BTNL, BTNR, BTNC) and generating the final VGA outputs.
vlang fpga hardware vga game digital-design simulation verilog hardware-platformer
Generated by gemma4:latest
Catalog Information
Create a hardware platformer game simulation using Vlang. The game should run on a Nexys4 DDR board, displaying graphics over VGA at 640x480 resolution and 60Hz. I need the core logic implemented across several modules: a clock divider, VGA timing generator, button debouncing logic, a game controller for physics (handling movement, jumping, and gravity), and a renderer. The renderer must draw the player (red), platforms (brown), ground (green), and background (dark blue) with specific draw prior
Tags
vlang fpga hardware vga game digital-design simulation verilog hardware-platformer
Quality Score
D
55.5/100
Structure
49
Code Quality
71
Documentation
41
Testing
0
Practices
78
Security
100
Dependencies
50
Strengths
- Consistent naming conventions (snake_case)
- Good security practices — no major issues detected
Weaknesses
- No LICENSE file — legal ambiguity for contributors
- No tests found — high risk of regressions
- No CI/CD configuration — manual testing and deployment
Recommendations
- Add a test suite — start with critical path integration tests
- Set up CI/CD (GitHub Actions recommended) to automate testing and deployment
- Add a linter configuration to enforce code style consistency
- Add a LICENSE file (MIT recommended for open source)
Languages
Frameworks
None detected
Embed Badge
Add to your README:
