u/Mr_ShortKedr

I made a tiny single-player Agar.io-like game in C++20 + OpenGL.

Repo:
https://github.com/ShortKedr/ugar-io-opengl

It was mostly a personal experiment: I usually work with engines, so I wanted to make a very small game directly with C++, OpenGL, GLFW, and CMake.

Now I want to clean it up into a nicer open-source project and would appreciate C++ focused feedback.

Things I’m curious about:

• Is the code structure easy to follow?
• Is the separation between game logic, rendering, and input reasonable?
• Is the CMake setup acceptable for a small project?
• Are there any obvious C++ smells or design decisions I should fix early?
• What would make the repo more pleasant to read or contribute to?

The project is intentionally small. I’m not presenting it as an engine or a finished game, just as a small C++/OpenGL project that I want to improve based on real feedback.

Roasts are welcome, but useful roasts are even better.

I made a small single-player Agar.io-like game using C++20 + OpenGL as a learning/project showcase.

Repo:
https://github.com/ShortKedr/ugar-io-opengl

It started as a "what if I make a simple game without Unity/Unreal?" experiment, but now I want to clean it up and make it a better open-source C++ project.

The project uses:

• C++20
• OpenGL for rendering
• GLFW for window/input
• CMake as the build entry point
• simple project layout with src, include, resources, and build instructions

I’d love feedback specifically on the C++ side:

• Is the project structure readable?
• Is the CMake setup okay for a small cross-platform project?
• Are there obvious bad habits in the code organization?
• Would you split the rendering/game logic/input differently for this size of project?
• What would you refactor first if this was your small C++ project?

I’m not trying to pretend this is a big engine or production-level code. It is a small learning project, but I want to make it cleaner and more useful as a public repo.

Any code review comments, issues, suggestions, or architecture advice are welcome.

I made a tiny single-player Agar.io-like game in C++20 + OpenGL.

Repo:
https://github.com/ShortKedr/ugar-io-opengl

It started as a small “what if I make a simple game without Unity/Unreal?” experiment, and now I want to turn it into a cleaner little open-source project.

It uses OpenGL for rendering, GLFW for window/input, CMake as the build entrypoint, and the repo has a simple project layout with src, include, resources, and build instructions. From the README, it is positioned as the simplest single-player copy of Agar.io made with C++ and OpenGL.

I’d love feedback on:

• Is the C++ structure readable?
• Is the rendering code sane or cursed?
• Is the CMake setup okay for a small cross-platform project?
• What would you add first: better AI, particles, multiplayer, UI, score/progression, or something else?
• What would make you actually star or fork a tiny project like this?

I’m not trying to pretend it is a huge engine or a finished game. It is a small learning/project showcase thing, and I want to improve it based on real feedback.

Issues, suggestions, code review comments, and stars are all welcome.

Roast away.

I kept writing this kind of code:

foreach (var resource in resources)
{
    if (resource.SearchString.Contains(query))
        results.Add(resource);
}

So I extracted the idea into a small C# search index:

https://github.com/ShortKedr/string-search-engine

It is intentionally simple right now.

The library builds an inverted substring index from resources, then resolves search queries through dictionary lookups instead of scanning every resource every time.

The target scenario:

mostly-static data + frequent searches

Not the target scenario:

constantly-changing data + one-off searches

Right now it supports:

• building an index from resources
• incremental add/remove
• substring key generation
• direct lookup-based search
• documented constraints and tradeoffs

The current version is more of a focused search primitive than a full search engine.

I’m trying to decide what should come next:

1. Keep it tiny and focused
2. Add ranking/scoring
3. Add better tokenization
4. Add generic payload support
5. Add fuzzy typo-tolerant search
6. Add benchmarks and NuGet package

What would you expect from a small embeddable C# search index?

Stars/issues/API criticism are very welcome. I’m trying to figure out whether this is useful to anyone besides me.

Taking notes from the comments on my previous post. The IK and rider pose are still pretty rough, but the scooter handling is starting to feel better.