74 karma · joined July 11, 2017
For Hockey Slam you can look for the entrypoint in Windows:
https://github.com/Mknsri/HockeySlam/blob/main/windows/win_m...
or Android:
https://github.com/Mknsri/HockeySlam/blob/main/android/app/s...
Then start tracing through, looking at any function calls that look like they contain anything interesting. Additionally in this project you can jump straight to the entrypoints of the game code:
https://github.com/Mknsri/HockeySlam/blob/main/game/game_mai...
Or the rendering code:
https://github.com/Mknsri/HockeySlam/blob/main/ogl/ogl_main....
Another way would be to look at the files and see if anything catches your interest, for example if you want to learn about the UI system, you could look at how a button is defined:
https://github.com/Mknsri/HockeySlam/blob/main/game/imui_sys...
Fabien Sanglard has great articles on studying classic video game engines, and could be used as a guide on how to approach codebases: https://fabiensanglard.net/quake2/index.php
“If you wish to make an apple pie from scratch, you must first invent the universe” :)
Edit: As for the release, I think it barely broke a couple of hundred downloads. I didn't do any real marketing and had no real goal of really getting the game out there as it was a learning experience for me first and foremost.
Do vim users know if there was anything like Select next occurrence in vim? Feature discovery is not one of vims strong suites
EDIT: More specifically by multi-cursor editing I mean selecting multiple occurrences of a word, and then editing in place. For example selecting all occurrences of the word user -> (getUser, setUserId, variable declarations with user) and then replacing them with account. This can be done with vim but is nowhere near as fast, since every change needs to be done one-by-one. Or selecting all the above occurrences, and pasting them somewhere for an interface declaration.