Re: What do you look for in a ROM?
The most important aspects of a potential codebase depend primarily on the skill and desires of the one who will be developing a MUD with it. When I first started learning to code I favoured a heavy feature set in a codebase. Without the skills to create what I wanted from scratch having features and snippets of something related to my ideas allowed me to tweak and adjust to slowly develop what I wanted.
Of course that was over a decade ago. Now that my skills have grown, I prefer a stable, bare-bones codebase that offers proper documentation, and all the necessary building tools that I might need/require down the road.
That being said, with whatever codebase I sink my teeth into, I always find I'm having to develop my own set of world balancing tools.
Tools such as:Hope some of this helps...
|