I am starting a MUD called Star Wars Destiny and need a full staff. (coders, pr, admins, builders, etc.) I am only a builder. I have a codebase and my application for hosting it is being reviewed by a host. I have many snippets to be added into the mud (coder) and after they are all in it will be awesome! E-mail me at RojanQDel@aol.com or AIM - RojanQDel or ICQ# 59987546, or just post here if you are interested.
Need SW MUD Staff
Posted by RojanQDel on Sun 12 Jan 2003 01:01 PM — 11 posts, 37,787 views.
Don't be disappointed, but I believe you are going to have a hard time convincing anyone to join you. Builders are normally hard to come by as it is, yet you're even asking for a coder. *shrug* Try as you might, I don't think you'll get far.
Actually, the fact that it is a SW based mud will draw some just because theyre scifi junkies at heart. The rest will fall into place from there. Actually my biggest problem with working on this particular project is that I consider SMAUG a halfstep removed from hell for coders.
Guess I need to add "scifi junkie" to my sig sometime :)
Guess I need to add "scifi junkie" to my sig sometime :)
SW is a good category, but I have yet to play a Mu* that has captured the feeling of the books or films. Good luck with your mud.
Well, it'll be one of the best muds out there once I get a coder to add my snippets, I'll try to keep it as close to the books and movies as possible, but I wish there were more coders... :-(
You sound almost like me when I started out making my MUD. I too started out as a builder for SWR when I made my MUD. I based it using Swr, and trust me play one swr based MUD and advertise. I got loads of builders, but I fired all of them for being corrupt and using their power for evil purposes. Anyways, Meerclar and Boborak are right. Building can be no problem depending on how many people play, but coders (and ones that acually try to do the job and not screw you over for no real reason) are really hard to come by. After my first incident with a coder I said I would not be hiring any more Immortals for my MUD ever again, and to this day I haven't. But the easiest way to resolve all of these problems are to learn to code. It takes a while, and can be frustrating, but once you get the hang of it its smooth sailing from there. Just take your codebase and unzip it to a directory you aren't going to use and screw around with it, change things. If it gets to screwed up, try and figure out what you did, or if its to much work, just unzip it again. Thats really how I learned. Anyways, good luck, if I catch a break from my MUD perhaps I'll come and try and help you some time.
I'm inclined to agree with that. Sure, it takes time to learn to code, but does it take as much time as you will eventually spend arguing with your coders? If you are unlucky you end up spending hours firing emails backwards and forwards clarifying points, resolving disputes, working out what was said and what was meant - those hours could be usefully spent learning C and doing your own coding. :)
Of course there are good coders out there, but if you don't know coding yourself you won't be sure when you find one, and also won't be able to fix problems if they half do the job and then leave.
Of course there are good coders out there, but if you don't know coding yourself you won't be sure when you find one, and also won't be able to fix problems if they half do the job and then leave.
I agree with that too now... Where can I learn to code? Documentation?
Pay any better bookstore a visit (I recommend Barnes&Noble). Head over to their computer books section, grab the "C for Dummies" or another entry level C programming book and grab a seat somewhere for some extended reading. Repeat as necessary until you find a book that actually helps you enough to buy and take home to work with, or note the useful titles and see if someone has em on the web somewhere in ebook format.
Any online documentations?
A classic book, which is also thin which means it is nice and compact, is "The C Programming Language", by Brian Kernighan and Dennis Ritchie. Published by Prentice-Hall.
It is pretty meaty, that is each page covers quite a bit. Maybe a beginners' book would be better but it is a good reference to have around.
As example code you might want to download and browse my "tiny mud server" and "tiny mud client" both of which are quite small (server: 880 lines, client: 286 lines). These give you the essence of coding MUDs without cluttering it up with heaps of stuff that isn't relevant to beginners.
Then maybe move on to a smaller "real" server. Also try doing lots of small examples (eg. from the book) using gcc as a nice easy-to-use compiler under Cygwin or Unix.
It is pretty meaty, that is each page covers quite a bit. Maybe a beginners' book would be better but it is a good reference to have around.
As example code you might want to download and browse my "tiny mud server" and "tiny mud client" both of which are quite small (server: 880 lines, client: 286 lines). These give you the essence of coding MUDs without cluttering it up with heaps of stuff that isn't relevant to beginners.
Then maybe move on to a smaller "real" server. Also try doing lots of small examples (eg. from the book) using gcc as a nice easy-to-use compiler under Cygwin or Unix.