// the find
OneLoneCoder/Javidx9
The official distribution of Javidx9's YouTube videos and projects
This is the companion code for javidx9's YouTube game-programming videos: dozens of single-file C++ examples and multi-part projects, including a software 3D renderer, a client/server networking example, a driving game with Lua scripting, and a role-playing game, all built on his olcPixelGameEngine. The older console engine is kept for reference. It suits people following the videos, or anyone who learns better by modifying working programs than by reading a book.
- The multi-part projects are split along video boundaries (Engine3D Part1 to Part4, Networking Parts1&2 and Parts3&4, CarCrimeCity Part1 and Part2, Worms1 to Worms3), so you can see how a codebase grows from one part to the next.
- The CarCrimeCity Part2 project embeds Lua 5.3 with a config.lua and external .city and .obj assets, which shows a scripting boundary that most tutorial repos skip.
- The networking file split (net_tsqueue.h for a thread-safe queue, then net_message.h, net_connection.h, net_server.h and net_client.h) suggests a sensible layering, not one monolithic socket file. I have only seen the filenames, not the implementation.
- The archive/ folder keeps the older GL and SDL console-engine variants, and the README links a community port from ConsoleGameEngine to PixelGameEngine, so the history of the engine stays readable.
- Binaries are committed next to the source: lua53.dll, liblua53.a, SpriteEditor.exe and olc_sprite.exe. The RPG project is a Visual Studio .vcxproj, so the non-Windows path is manual and not documented in what I could see.
- olcPixelGameEngine.h appears in several project folders (CarCrimeCity Part1, CarCrimeCity Part2, SavingSedit) instead of being referenced once. Nothing ties those copies to a version, so engine fixes will not reach the examples.
- Much of the code is dated. The README says the console engine is deprecated, and the last push was in August 2025. Treat it as reading material and use the PixelGameEngine repo for anything new.
- The visible tree has no build files, tests or CI. Each example is a standalone file you compile by hand, so getting an example to build is often the first real obstacle. The license is OLC-3, a custom BSD-style text, so read it before copying code into anything you ship.