Listening to a talk on YouTube: 9 Secrets for a Future-Proof Game Engine - Isadora | Vancouver Game Dev Series by Isadora Sophia about her C-Sharp game engine Murder. Here’s some notes I jotted down.
- Make a Game
- Don’t Crash
- Make errors obvious
- ex: using error assets
- Logging
[CallerMemberName][CallerLineNumber]
- Debug.Assert for catching programmer errors early
- Nullables
- Make errors obvious
- Only do it once it’s a bottle neck
- As a rule: “we only automate tools after hitting it at least 3 times”
- Exception: “or whenever we notice we didn’t add something cool to the game because it was too bureaucratic”
- Scale Horizontally
- ECS
- Meta-Programming
- Abstract Implementation
- Pick your battles
- Don’t reimplement everything yourself
- Prototype, Implement, Refactor
- Don’t overthink design