Howdy folks,
I've been playing with ROM now for about 2 months, and been working on learning C (by playing with ROM), for about the same amount of time. I am quickly gaining insight to this whole coding business, but am no where near good yet.
I got ROM a while back and have all sorts of good plans for it. However, these plans include junking the whole current class format, and drastically changing the level structure. My goal is to have a classless mud with 'Specializations' that can be chosen later in character progression. (Similar to Lensmoor.org for those familiar) I also want to change the level structure to one that has mortals from lvl 1 to 100ish, then able to remort back to level 1 and go back to level 100ish from there. (again similar to Lensmoor)
My question is: Would it be easier to edit stock code to fit my needs (noob-coder) or to start from scratch using stock as a guide?
Any suggestions would be greatly appreciated!
Long live Nick Gammon!
Brendo <3 Mush
It may be easier to use to stock and just rework it to what you want, otherwise without enough codding skill, you'll end up with ALOT of problems. I've had a similar idea with SMAUG, but redoing what is there to start will be alot easier.
Either way, this will be a very large task. That being said, you're better off keeping the existing code base. It's at least something to work off of. Don't forget that MUD servers, while not huge programs, aren't something to shake a stick at, either.
Actually, what I'd really recommend doing is starting with something simpler. Any 'drastic' change is probably best left till later. Start small and build up. The bane of a beginning programmer is to set his/her sights too high, and then get frustrated and never finish anything. (Been there, done that)
That being said, if you really feel up to it, then by all means give it a go. But don't be afraid to throw stuff away if you make mistakes. It's probable that your first try will 'almost work' but will have some fundamental problem somewhere that makes it buggy, hard to program in, etc. This is only natural: you can't predict from day 1 what your real problems will be on day 80. It happens all the time in the industry. The best coder is the one who recognizes that sometimes, you just have to restart something.
Thanks guys. I am halfway through 'Absolute beginners guide to C', and 1/4 the way through 'C Programming' *yes doing both simultanously to make sure any extras are caught*. Once I finish with those, I will pick up my 'Mud Programming' book from Barnes and Noble and start with that. My goal isn't to have some monster MUD right away. My goal is to learn to program while learning to code at the same time. (I know they seem like the same, but may be considered different by others like me) I did a little bit of both suggestions, and feel like I am learning more and more each time I sit down to work.
I have decided, however, that the small changes bit by bit is much easier to start out with. :)
Thanks again,
Brent
Glad to hear that things are working out for you!
Out of curiosity, what difference are you making between 'coding' and 'progrmaming'? :)
Being a new recruit to both categories (if there is such a distinction), my terminology tends to cause confusion amongst even the most veteran of nearly any trade. By 'coder' I am referring to the actual coding of MUDs. While this may not be any different from 'programmer', in my mind I have seperated the two. 'Coder' = MUDS, 'Programmer' = other software. If these two titles are one in the same, I will refrain from using them as I have.
Thanks for any clarification. :)
Brent
A coder is somebody who writes code; a programmer is somebody who programs. Since programming is, basically, writing code, there is really no difference between the two. :)
Good point. As I said, I'm still novice to this whole 'industry' and am just getting assimilated to the titles and technicalities. Thanks again.
Brent