I have a very different suggestion. This codebase (RPI Engine[1])is what I initially cut my teeth on and I learned a lot about good program design just by view

I have a very different suggestion. This codebase (RPI Engine[1])is what I initially cut my teeth on and I learned a lot about good program design just by viewing what works and what didn't work. Reading and understanding code that's stood the test of time can also be quite valuable because you can see which patterns can survive lots of people touching it and which patterns start to fall apart when the original designer isn't available to onboard new people - MUDs develop through time with a few concurrent developers at most, and generally have stretches where there are no active developers, or the people executing code changes are learning it as they go. I'd suggest this codebase as an excellent lesson in how bloat and complexity enter into the picture over time - I wish the actual commit history was available, but unfortunately the open source release was just a snapshot in time. 1. https://github.com/webbj74/RPI-Engine https://github.com/webbj74/RPI-Engine