Frequently Asked Questions:

A: Connecting to the Mudhaven servers is really easy. Follow the steps below:

1. Open the Putty application.
2. In the hostname input, put: mudhaven.net(See Example #1 Below).
3. Make sure port is set to 22 and ssh is clicked also.
4. Click the open button and you should see a screen pop up.(See Example #2 Below)
5. Enter your username and hit enter.
6. Enter your password and hit enter.(Note: password will not be shown while typing for security reasons.)

A: Connecting is easy. Just follow the steps below. For my example, I will be using coreFTP.

1. Open the CoreFTP application.
2. Where you see Site Name, put Mudhaven
3. Where you see Host/IP/URL put mudhaven.net
4. Where you see port put 22.
5. Where you see connection, select SSH/SFTP.

A: There could be a variety of reasons. I will list a couple common ones below.

1. If you haven't logged into your account via putty at least once, the ftp client will not connect.
2. If your account is pending or has an expired password FTP clients won't connect. Login via putty and update your password.
3. Make sure your username, password, hostname, port, and connection type are set correctly.

A: Follow the steps below:

1. In your main directory, type wget byond_version_link
• Make sure you get the Linux links.
• For the rest of this example, I will be using: 514.1552
• 
2. Hit Enter, byond will start to download, and once it is done type ls and you should see:
• 
3. Now we see the filename ends in a .zip. So lets unzip it. Type unzip filename.zip
• For my example I'd type unzip 514.1552_byond_linux.zip (See Example Below if you done it correctly.):
• 
4. Alright now that we unziped byond, lets make sure its made its directory. Type ls
• If it unzipped correctly, you should see a blue folder called byond(Example Below):
• 
5. Lets move directories. Type cd byond
6. Now that we are in the byond directory. Type make If done correctly you should see this:
• 
7. Alright since we are installing byond for personal use, type make here
8. If done successfully you should see this:
• 
9. Now type source /home/*/byond/bin/byondsetup
• Replace the * with your username
• You won't see any output, if done correctly.
10. Now we want byond to run everytime we login, so type cd
• cd stands for change directory. When you type it by itself, it takes you to your user directory.
11. Type pico .bashrc and go to the end of the file and add: source /home/*/byond/bin/byondsetup
    • Remember to replace the * with your username. It should look like the example below:
    • 
12. Now hit ctrl + x and then y when asked to save the file.
13. You have successfully installed byond to your account. If you want to install a new version of byond simply follow steps 1 - 9.

A: Follow the steps below:

1. Upload your .dmb, .rsc, and other files needed to run your game to the server.
• Note: To help with clutter, you can create a folder to upload your files to. To make a folder or directory type mkdir foldername
2. Create a file called start.sh in the same location where you uploaded your .dmb and .rsc files.
• Note: You can create the start.sh file by typing pico start.sh
3. Open your start.sh and copy and edit one if the following below:
• DreamDaemon yourfile.dmb yourport -options &
• DreamDaemon "your filename".dmb yourport -options &

You can use the following below for the -options:

• -cd path
  • Use the specified path as the working directory. The default is the directory containing the world file.
• -cgi
  • Run in CGI mode. This is normaly compiled directly into the .dmb by setting world.executor, which in turn is normally done automatically by including Dantom.CGI.
• -core
  • Produce a core dump if DreamDaemon crashes.
• -home path
  • Use the specified path as the top safe directory. The default is the directory containing the world file.
• -invisible
  • Don't broadcast the world to the BYOND hub.
• -log logfile
  • Send stderr to the specified file.
• -logself
  • Send stderr to world.log, where world is the name of the .dmb file (minus the .dmb).
• -once
  • Shutdown after users log out.
• -params var=value
  • Any number of parameter assignments may be made or a single form-url-encoded string may be provided that includes multiple assignments. These parameters are made avail‐ able to the DM program in world.params.
• -ports range
  • Specify a range of ports that may be used when a specific port is not specified. This also applies to any child worlds spawned by the startup() DM instruction, which is used by host servers to dynamically execute worlds when they are requested by users. See PORTS for more options. The syntax for range is a comma separated list of numbers or ranges of numbers. Example:
    
    -ports 1234,1236,1240-1250
• -quiet
  • Generate less noise in the log file. The main difference is that the world does not advertise when it starts up.
• -safe
  • Allow access to files and subdirectories in the same location as the world file. Shell commands may not be executed. This is the default if the world file is in a safe directory. A safe directory is one with the same name as the world file. A file called MyWorld.dmb would run in safe mode by default if it existed in a directory called MyWorld. This comparison is not sensitive to case.
• -trace
  • Output a debug trace-log file to help the developers track bugs.
• -trusted
  • Allow access to any part of the filesystem and permit execution of shell commands. Note that allowing DreamDaemon to try accessing any file does not mean the operating system will actually allow the operation. Normal system security is in no way compromised by running in -trusted mode.
• -ultrasafe
  • Disallow all file access and forbid the .dmb program from executing any shell commands. This is the default if the world file is not in a safe directory. (See -safe.)
• -unsafe_diag
  • Don't block SIGUSR2 during lengthy I/O operations: useful if you want a backtrace via kill -USR2 and DreamDaemon is ignoring it due to I/O or infinite loop, but may be dangerous if a system call is interrupted.
• -version
  • Output the BYOND version and then exit.
4. Once you have setup your start.sh file type ./start.sh &
• If you get permission denied when you try to run start.sh, see "Why am I getting permission denied when I try to run start.sh
• If you see the message below, it means your game is up and running.

• If you see no message or any output it means your game is crashing. This is usually because you are missing a file needed to run the game or bad code that is causing the game to crash.

A: When you get the permission denied message its quite easy to fix, simple type: chmod 755 filename. If you want a better explanation of chmod this site can help you.

A: You can close the game with two commands ps ux and kill.

1. Type ps ux and you should have something like this below pop up:

2. Now find the PID. In my ps ux screen shot, my PID would be 26963. You get this PID because its the line with DreamDaemon command.
3. Now simply type kill -9 PID. So for my example it would be: kill -9 26943. That will kill your game from the server.

A: Users will be sent their invoice on 4th of each month. They will have a 7 day window to pay. If the user doesn't pay their account will be set to the free tier.

A: Users that are considered inactive will be purged on the 4th of each month. What is considered an inactive account? Below are what put you in the inactive account status:

• You haven't logged in for a full 30 days.
• After you haven't logged in for a full 30 days, I will check to see if your account is hosting anything. If not I will continue to the third step.
• I will reach out to you and if I do not hear anything within 48 hours, I will purge your account.