I can't help to notice that there are a lot of posts asking for advice on how to start a MUD
what server to use, how to compile servers. I rarely see anyone bring up the real issues
and the questions that you should be asking your self. Usually if you ask these questions
to yourself, you might find out that you know the answer already.
1. Do I have time to run a MUD?
2. Do I have the mentality to run a MUD?
3. Do I have the experience to run a MUD?
Some people seem to be under the misconception that MUDs are easy to run. This is far from
the truth. It takes a lot of time and dedication. Being a Implementer is a way of life. Constant
hassle, grief, and heart ache. Anyone who is even thinking about running a mud is crazy. I
know, This isn't the case with you. You have a fresh Idea, you're smart, and you are going
to make a MUD like no other. It is going to be the #1
MUD in the whole MUD universe.
Reality check: 90% of all the MUD in existence will fail.
90% of the implementers of those MUDs had the same visions.
80% of those implementers failed before they started.
Some naive persons think that all they have to do is pay for hosting. They
Hire staff and they want to sit back and have everything done for them.
They don't realize that the are going to have to listen to every problem everyone
Has, that everyone expects the implementer to treat his or her problem as the priority,
And they are the ones who have to answer to the players for the behavior of the staff.
How is the Best way to start a MUD? By playing of course. Search for your codebase
by testing them out. Once you have found a decent codebase, that you enjoy, play
with that codebase for at least 3 months or until you have learned the codebase from
a players perspective. Then see if that MUD is hiring. If they are, apply for a building
position. DO NOT go to 20 different MUDs. Stick with only one. Once you have building down,
request another position. You should be in that MUD's staff for at least a year. Work your
way to the top, learning everything from your staffs' point of view.This will allow you to
make more sound decisions as an Implementer. After everything, You should have had at
least a year of Staff experience on a productive MUD with a decent sized pbase. If you
can't accomplish this then chances are that you are not ready to run your own MUD.
Don’t let this post discourage you. This is my opinion. This is just something to
think about before you start investing a lot of time and effort into making a
vision that you may have come to life. Running a MUD takes a level of maturity
along with determination and patience. If you don’t have these qualities you
may see your vision go down in flames. Don’t fret, these qualities may come
with time.
what server to use, how to compile servers. I rarely see anyone bring up the real issues
and the questions that you should be asking your self. Usually if you ask these questions
to yourself, you might find out that you know the answer already.
1. Do I have time to run a MUD?
2. Do I have the mentality to run a MUD?
3. Do I have the experience to run a MUD?
Some people seem to be under the misconception that MUDs are easy to run. This is far from
the truth. It takes a lot of time and dedication. Being a Implementer is a way of life. Constant
hassle, grief, and heart ache. Anyone who is even thinking about running a mud is crazy. I
know, This isn't the case with you. You have a fresh Idea, you're smart, and you are going
to make a MUD like no other. It is going to be the #1
MUD in the whole MUD universe.
Reality check: 90% of all the MUD in existence will fail.
90% of the implementers of those MUDs had the same visions.
80% of those implementers failed before they started.
Some naive persons think that all they have to do is pay for hosting. They
Hire staff and they want to sit back and have everything done for them.
They don't realize that the are going to have to listen to every problem everyone
Has, that everyone expects the implementer to treat his or her problem as the priority,
And they are the ones who have to answer to the players for the behavior of the staff.
How is the Best way to start a MUD? By playing of course. Search for your codebase
by testing them out. Once you have found a decent codebase, that you enjoy, play
with that codebase for at least 3 months or until you have learned the codebase from
a players perspective. Then see if that MUD is hiring. If they are, apply for a building
position. DO NOT go to 20 different MUDs. Stick with only one. Once you have building down,
request another position. You should be in that MUD's staff for at least a year. Work your
way to the top, learning everything from your staffs' point of view.This will allow you to
make more sound decisions as an Implementer. After everything, You should have had at
least a year of Staff experience on a productive MUD with a decent sized pbase. If you
can't accomplish this then chances are that you are not ready to run your own MUD.
Don’t let this post discourage you. This is my opinion. This is just something to
think about before you start investing a lot of time and effort into making a
vision that you may have come to life. Running a MUD takes a level of maturity
along with determination and patience. If you don’t have these qualities you
may see your vision go down in flames. Don’t fret, these qualities may come
with time.