A guide for using Dosemu2 to play Door Games on Mystic BBS

The final step is to configure the link in Mystic and is rather textbook.

Enter the sysop menu, enter the menu editor and scroll down to Doors.  On a default install there will be two sample links, we will edit the first

• Change the display text to say “Darkness”
• Press [TAB] to access the Action List
• Select DD for Exec external program
• And enter the following into the Data section

doors/rundoor.sh %3 dark 1

The parameters are as such:

• $1 is the node number and assigned by mystic,
• $2 is our door identifier and needs to match what we set in the rundoor.sh,
• $3 is a left over from the deadbeatz config that isn’t needed. I kept it around to remind myself of the drop file requirements. (door/chain/etc..)

Note: if you need to debug your door there are two steps.  First is to remove “1>/dev/null  2>&1” from the command line in rundoor.sh.  Next, disable the page refresh for the door in the menu editor.

Bonus Note: make sure everything in the “/home/mystic” has the right permissions, eg: mystic:mystic

sudo chown -R mystic:mystic /home/mystic/

Open up Mystic, login and select the Darkness door.  With any luck the program will load.

As of this article there are only certain apps that can be Doors on a BBS.  Unlike normal PC games the output needs to be routed over a serial connection.  That is what the FOSSIL driver is for and the Door App/Game etc..  needs to support this.

A good example of this is Operation Overkill II.  The base game has been designed to run with FOSSIL drivers, supports Mulit Node operation (ideally you can have more than one player on the same map) and is easy to setup.

However, it has an app designed to setup the game config which I have never been able to make work through a Door.  Instead I have to log into the console and run it through Dosemu2.