Subj : Re: Doors and .cfg files
To   : Cozmo
From : Wall E. Weasel
Date : Wed Jun 09 2021 09:13 pm

 Co> I'm trying to get an old door to work . It uses  filename.exe
 Co> filename.cfg in the menu command. I need to have a .cfg file for each
 Co> node. How do I get Mystic to recognize which .cfg file to use based on
 Co> whatever node the user has logged in on?  The .cfg file won't accept
 Co> the temp%1  for the directory. So I can't use the same .cfg file for
 Co> all the nodes, it has to be temp1, temp2 in the .cfg file etc.

Let Windows parse the node information from within the game's batch file.  Name
each of the config files with the node number as part of the filename, such as
node1.cfg, node2.cfg, and so on.  Have Mystic call the game's batch file with
the node number as a parameter.  The menu data for the door command (assuming
you're using NetFoss again) would look like:

C:\MYSTIC\NETFOSS\NF.BAT /N%N /H%H C:\DOORS\GAME\GAME.BAT %N

The NetFoss batch file would then call GAME.BAT with the node number as
parameter %1.  GAME.BAT then converts that parameter as the configuration
filename:

C:
CD \DOORS\GAME
GAME.EXE node%1.cfg

Windows replaces %1 with the first parameter of the batch file, so it actually
calls GAME.EXE with the parameter node1.cfg, node2.cfg, and so on.

 
--- MultiMail/Win v0.52
 * Origin: The Basement Theory - Sciotoville, Ohio USA (21:2/121)

.