| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Door game commands |
On Thu, 21 May 2015, Roger Shays wrote to All:
RS> separate nodes to still be using the My Name I logged in one
RS> client as me and one client as my wife and when I went into say
RS> clans it showed me as user on both nodes in the game
each node has to have its own dropfile... they have to have different names
(eg: dorinfo1.def, dorinfo2.def) or they have to be in different
directories where the door can find them (eg: node1/door.sys,
node2/door.sys)...
hopefully TG has a macro that can be placed in the command line for the
door which gives the node number... if so, then that may be able to be used
in the bat file for the door to tell it where to look...
as an example, on my RA system, *N is the node number macro... my node
directories are named Nx where 'x' is the node number so node1 is running
from bbs/n1 and node2 is running from bbs/n2... then in the bat file i use
%1 if the *N is the first parameter of the command line calling the bat
file...
eg: thisdoor.bat *N *M
then in thisdoor.bat i have
{at}echo off
cd this_door_directory
runthisdoor /node=%1 dropfile=\bbs\n%1\door.sys
the above is all pure example but it should help you get going... you'll
need to see what your door uses if it is even multinode aware or multinode
capable... some doors are not and you have to block access to other nodes
while someone is playing...
)\/(ark
* Origin: (1:3634/12)SEEN-BY: 19/33 34/999 90/1 116/18 120/331 123/500 128/187 135/364 140/1 SEEN-BY: 218/700 222/2 226/0 160 230/150 261/38 100 266/404 267/155 280/1027 SEEN-BY: 282/1031 1056 292/907 908 320/119 340/400 396/45 633/0 267 280 281 SEEN-BY: 712/620 848 770/1 801/161 @PATH: 3634/12 123/500 261/38 712/848 633/280 267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.