|
There is no question about it. We have all at some point thought of creating our own MUD. Our minds race and fill with ideas but at the end of the day, ideas can only bring you half way. The internal matrix of a MUD, its codebase is what brings your ideas to life but unfortunately there are those out there, despite their profound creativity, are crippled by the lack of knowledge for coding.
They could always find a coder to do all the technical work for them or possibly learn basic coding and get a few months or years practice on another MUD. Although, no one is as dedicated and/or eager to the creation of a MUD as its creator. The coder becomes the catalyst to your MUD and a master to your domain, and since you don't know a thing about coding MUD, the coder is burdened with all the objectives you want him to complish and you are burdened with inconvience. Plus, you can only create when the coder can code.
And inconsideration to being employed by another MUD, your ideas are withheld and abilities limited to the MUD. While your swimming in your ideas and goals, your attention is focused on your employer's creation and fufilling his standards. It is definately an awesome way to learn coding and practice until you can create your own but what about those you just want to jump into creating their own. But hey, this is only my point of view.
What I ask for is a simplified step-by-step guide, a translation for all this technical jargon and easy "instructions" (for lack of a better term) to preparing, creating, and coding a MUD. Something like an Idiot's Guide to MUD Coding.
|