I'm interested in setting up a small MU* server on my own computer just to learn and get a greater appreciation of what the admins do.
That said, I'm following the tutorial at www.gammon.com.au/pennmush/installingpennmush.htm but once I download and extract the files, I have no databases to manipulate or write to.
Specifically, there is no minimal.db.z file, or any other similar file, and my data folder just contains the readme file.
My laptop is running Win7 Ultimate x64, if that's any help.
Thanks and I appreciate any help! I've noticed that there are very few posts from this year, so hopefully I'll be able to get some help.
I'm actually using that guide in conjunction with the one on this website to try and set up the server. It does indeed mention the databases but it also says there is a file called minimal.db.z or minimal.db that would contain:
The minimal database, containing 3 objects: #0 (Limbo, the start room), #1 (One aka God, the SuperWizard), and #2 (the Master Room)
But I don't have that file in my archive that is unzipped.
Are there any other guides available on this install? Perhaps I'm missing something?
*EDIT*
I double-clicked the pennmush.exe file and afterwards I noticed I did indeed have a PANIC.db file in the /game/data folder. Then, I don't recall exactly what I did, but I now have an 'indb' file in that folder as well.
I'm OK with making mistakes and messing stuff up, because this is all a learning process, but I really don't understand what step in the process I'm doing incorrectly. It definitely isn't my first rodeo, and I consider myself rather tech-savvy, so it shouldn't be too difficult. I'm sure it'll be something stupid...
*EDIT 2*
So, I was able to get it working. I do not recall my exact steps but I somehow got a maildb, PANIC.db, chatdb, and outdb. At some point, I ran the server and it generated an indb which worked as well. I tried using the minimal.db posted on these forums, but the server errored out while loading and didn't recognize it as valid (it is drastically different than the indb that was generated and I'm currently using).
Once I got past the issue with the databases, I just followed the tutorial on this website to configure the mush.cnf file and was able to get everything else loaded and running.
My next question now, is how to allow incoming connections to my computer so others can connect to the MUSH. I'm going to set up the server on my desktop at home and try to connect from work and see how that goes...
Quote: My next question now, is how to allow incoming connections to my computer so others can connect to the MUSH. I'm going to set up the server on my desktop at home and try to connect from work and see how that goes...
Perfect, I already know how to forward ports so I should be OK with that. I'd imagine I update the appropriate port in my mush.cnf file that I forward and then give that port as part of the MUSH's address?
I guess the other question then is what is the address of my MUSH? Is it just <My.ip.address:port>? I have Dyanmic DNS on my router, and don't know if I could just give out that address as the MUD's address?
*EDIT* I suppose I forgot to ask...what program on portforward.com am I looking to emulate in its' settings? Obviously "custom MUSH server" isn't a choice :P
You want to give out your external IP, you can find it here: http://www.whatismyip.com/
Don't pick a program, those are just aliases to ports. There should be a custom port option, if not just pick anything and replace the port with the port your MUD is running on.
Just a quick post to clarify the databases. If they don't exist, PennMUSH will create them automatically. Indb is read in when the server is started and written to when the server is shut down and/or rebooted, outdb is written to as a backup when the server is @dump'd. Maildb stores mail to players and chatdb stores @channel information and buffers.
It's important to note that none of these files are actively accessed WHILE the game is running. PennMUSH runs almost completely from active memory. The databases and config files are only there to provide backups and a starting point for when you start up your server. Therefore, it's a good idea to set an automated @dump every few hours or so, so if the server crashes, you don't lose much, if anything.
Basically, the server is set up to create the minimal database if no database already exists, and so loading the 'minimal' database from a file is unnecessary.