[Rjakegel]

While not exactly a newbie at MUDding (I have been playing a specific MUD for over a year now), and not a total newbie at learning code (I have also done a little bit of building), I am completely new at...creating my very own MUD!
I am looking for someone to make a list of all the downloads I need to create my own MUD. I am not looking to post it on the internet, I only need it to run on my home computer. Also, I am clueless to things such as: Do I have to start with a stock version of GodWars or some other framework; Vocabulary- I don't know much coding lingo.
Please please please somebody help me out...
*points to Terloch*
Besides, I won't play my current MUD any less than I already do.
Thanks for listening,
Waffle

[Rjakegel]

I use windows, but have cygwin (linux emulator).
what comes next?

[Loriel]

Choose your codebase, and download it.

Kyndig has a good selection to choose from ().

I'd recommend putting it into your home directory within your cygwin directories.

Then use 'tar zxf filename' to extract it from the compressed file, and read the instructions - typically in the doc subdirectory.

Normally compiling with cygwin needs some minor modifications, but isn't too difficult.

[Rjakegel]

Thanks for the tip, but I need more than that.
Quickmud isn't downloading as a compressed file (at least that my computer recognizes). Any suggestions?
(Keep in mind that I am not familiar with any of this in the least).
Does anybody know any good FAQ urls for me to look through?

[Rjakegel]

Ok. I am no longer going to make my own MUD.
It is hard and I am stupid.

[Terloch]

You aren't stupid Waffle, but it most definitely IS hard...

[Loriel]

You will probably be downloading a file which is compressed using the *nix tools gzip and tar, resulting in a name like filename.tar.gz or filename.tgz.

Whilst this can be extracted with winzip, you should start cygwin and then use 'tar zxf filename.*'.

[Nostrum]

You are not stupid. The best advice when I first started was given to me by Gareth of the Abandoned Codex...."It is a lot of work and don't stop no matter what". While you are learning, you may get flamed, burned out, or you may even feel the need to throw your computer out the window. Whatever the case may be do not give up now. As an opinion I would download the codebase you have had the most play time in. Find all the documentation on the codebase. If the codebase has a mailing list I recommend that you join it. Read all the threads here and also on the mudconnector. Let your imagination be your guide. Please understand that this is hard at times and very time consuming, but do not be discouraged by failure. Just try again.

[Brody]

[UnKnOwN1205]

ok i downloaded the tar.gz file and i typed
tar zxf mdelight_backup.tar.gz
and it says
gzip: stdin: not in gzip format
tar: Child return status 1
tar: Error exit delayed from previous errors

o yea and i have this in my
D:\cygwin\home\UnKnOwN directory

[UnKnOwN1205]

ok another problem. i downloaded a fresh copy of dystopia gold and extracted it and now it worked... BUT what do i do after i type tar zxf dystopia-gold.tar.gz?
my frend told me to type
cd dystopia
cd src
and then type make
but when i type make, i get a error saying "bash: make: command not found"

[Jenred]

I've personally not tried that codebase, but sometimes you need to run a configure file first that configures the source for your system and THEN produces a makefile. -OR- (if your using cygwin) you didn't get the 'make' file-thing and it simply cannot execute that command.

Either could be the problem, and without actually going and checking out the codebase I don't know.

[UnKnOwN1205]

im just testing stuff out. im not planning to run that codebase but anyways i got the make command to work. i was missing some cygwin stuff. but now wen i type make, i get a bunch of errors.

$ make
gcc -c -Wall -g act_comm.c
In file included from act_comm.c:26:
merc.h:5254: warning: conflicting types for built-in function `logf'
gcc -c -Wall -g act_info.c
In file included from act_info.c:26:
merc.h:5254: warning: conflicting types for built-in function `logf'
act_info.c: In function `do_password':
act_info.c:3231: warning: implicit declaration of function `crypt'
act_info.c:3231: warning: passing arg 1 of `strcmp' makes pointer from integer w
ithout a cast
act_info.c:3248: warning: assignment makes pointer from integer without a cast
gcc -c -Wall -g act_move.c
In file included from act_move.c:25:
merc.h:5254: warning: conflicting types for built-in function `logf'
gcc -c -Wall -g act_obj.c
In file included from act_obj.c:25:
merc.h:5254: warning: conflicting types for built-in function `logf'
gcc -c -Wall -g act_wiz.c
In file included from act_wiz.c:25:
merc.h:5254: warning: conflicting types for built-in function `logf'
act_wiz.c: In function `do_resetpassword':
act_wiz.c:6411: warning: implicit declaration of function `crypt'
act_wiz.c:6411: warning: assignment makes pointer from integer without a cast
gcc -c -Wall -g bit.c
In file included from bit.c:47:
merc.h:5254: warning: conflicting types for built-in function `logf'
gcc -c -Wall -g arena.c
In file included from arena.c:25:
merc.h:5254: warning: conflicting types for built-in function `logf'
gcc -c -Wall -g mccp.c
In file included from mccp.c:41:
merc.h:5254: warning: conflicting types for built-in function `logf'
gcc -c -Wall -g board.c
In file included from board.c:26:
merc.h:5254: warning: conflicting types for built-in function `logf'
gcc -c -Wall -g build.c
In file included from build.c:32:
merc.h:5254: warning: conflicting types for built-in function `logf'
gcc -c -Wall -g clan.c
In file included from clan.c:25:
merc.h:5254: warning: conflicting types for built-in function `logf'
gcc -c -Wall -g comm.c
comm.c:48:48: execinfo.h: No such file or directory
In file included from comm.c:50:
merc.h:5254: warning: conflicting types for built-in function `logf'
comm.c: In function `lookup_address':
comm.c:1142: warning: implicit declaration of function `gethostbyaddr_r'
comm.c: In function `nanny':
comm.c:2357: warning: implicit declaration of function `crypt'
comm.c:2357: warning: passing arg 1 of `strcmp' makes pointer from integer witho
ut a cast
comm.c:2365: warning: passing arg 1 of `strcmp' makes pointer from integer witho
ut a cast
comm.c:2646: warning: assignment makes pointer from integer without a cast
comm.c:2671: warning: passing arg 1 of `strcmp' makes pointer from integer witho
ut a cast
make: *** [comm.o] Error 1

[Jenred]

As you can see from the bottom of what you posted there is actually only 1 error and that is in comm.o around like 2671. Something to do with strcmp... and I may even be reading it wrong and that's not the error.

All that logf stuff are merely WARNINGS. Cygwin (as I've heard) is a high-babying thing. It gives you warnings that other things wouldn't... trying to correct you. Like "warning you typed this and this here and I think its wrong." when it may or may not be... but chances are it is wrong, but not deadly.

Errors however need to be fixxed.

I suggest looking around strcmp, and if its not a vital function (I've seen several sorta useless functions [only useful to very advanced codebases that allow for like music and graphics and all that] in various codebases.) try commenting it out (not deleting) and trying to make again... if anything just keep track of what you comment out and have a coder look into your problems.

[Dre]

I am pretty sure Cygwin or windows don't have a crypt function built in and therefor you have to compile with nocrypt defined (if the codebase is general they'll have checks for it). Just add in the makefile to the lflags -DNOCRYPT.

I don't know what the logf errors/warnings but if it's a standard function from another library it might differ with the one you are using and the one the developers were using.

Btw, if you use gcc compiled under cygwin it's not giving more warnings then on another platform, cause it's the same.

And the error isn't necessarily the last line of output, it might be something else as well. The compiler might just get confused later.

I'd say, get a coder to help you. It's hard to learn it all on yourself.

[UnKnOwN1205]

ok, i ignored the errors. then i type ./startup &
and i got
$ bash: ./startup: /bin/csh: bad interpreter: No such file or directory

i cant boot it up. why? i checked the folder and i see the startup file