onelonecoder/olcpixelgameengine

The official distribution of olcPixelGameEngine, a tool used in javidx9's YouTube videos and projects

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 59 minutes ago
Added to GitGenius on September 16th, 2026
Created on September 2nd, 2018
Open Issues & Pull Requests: 141 (+0)
GitHub issues: Enabled
Number of forks: 915
Total Stargazers: 4,249 (+0)
Total Subscribers: 137 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.7 hours
Mean response time: 32.8 days
90th percentile: 17.0 days
Tracked items: 20

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 10
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 484 days
Stale 30+ days: 9
Stale 90+ days: 7

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • wontfix (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

olcPixelGameEngine is a C++ graphics and game development library designed for creating 2D pixel-based games and interactive applications.

The engine addresses the need for a lightweight, accessible way to handle graphics rendering and game loop management without the complexity of larger frameworks. It provides a simple API for drawing pixels, sprites, and shapes to a window, managing input events, and running a game loop. The approach emphasizes ease of use and educational value, making it straightforward for developers to focus on game logic rather than low-level graphics details.

The tool suits hobbyist developers, students, and those learning game development fundamentals. It works well for 2D pixel art games, visual experiments, and educational projects where simplicity matters more than cutting-edge performance. The engine is particularly valuable for following along with video tutorials and learning resources that demonstrate game development concepts step by step. Developers should expect a minimalist feature set compared to full-featured engines; this is intentional and keeps the library lightweight and easy to understand.

The project maintains active engagement with its user community through video content and educational materials. Development activity shows consistent refinement of the core library with attention to stability and usability. The codebase remains focused on its core mission without feature creep, and updates address both bug fixes and incremental improvements to the API based on user feedback from educational contexts.