this post was submitted on 27 Jun 2025
844 points (98.6% liked)
Programmer Humor
24725 readers
230 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Honestly back when I was a kid this is how I thought games were made, every possible image of a game was already saved and according to your input it just loaded the next image.
I stopped thinking that with 3d games
I thought that they were managing that stuff on a per-pixel basis, no engine, assets, or other abstractions, just raw-dogging pixel colors.
And before I even played video games at all I was watching somebody play some assassin's creed game I think and I thought the player had to control every single limb qwop-style.
In the first few Assassin's Creed games, they did use the idea of a Puppeteer system for the control scheme, although it wasn't physics-based or anywhere near as hard as QWOP. Each of the controllers face buttons performed actions associated with each limb, and the right trigger would swap between low profile actions and high profile actions.
In the top right of the screen, there was always a UI element showing what the buttons did at that moment in that context, which might've been why you thought it was a QWOP style system. It's not exactly what you were thinking of at the time, but you were closer than you realise.
Not quite "Time Killers" level of limb to button assignment, but a line that I had not drawn in the AC control scheme!
Apparently ai is learning to do that first thing you said about pure pixel management. It's crazy that it works at all