home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1994 #1
/
monster.zip
/
monster
/
BBS_UTIL
/
VTC203SW.ZIP
/
VTC.DOC
< prev
next >
Wrap
Text File
|
1994-02-10
|
42KB
|
1,259 lines
Virtual Teleconference (VTC) Version 2.03
Copyright (C)1993 Justin Randall & Dan Newcomer
Portions of the code Copyright (C) Roland De Graaf 1992
Licensed to: Dan Newcomer
SPECIAL OFFER:
I am now running OS/2. I will start on an OS/2 version of this
program soon after Feb. 15, 1994.
VTC REGISTRATION
This is a DEMO version of the Virtual Teleconference,
copyright (c) 1993 Justin Randall and Dan Newcomer and distributed
by Newcomer Technologies. VTC is not Public Domain software or
Freeware, it is Shareware. You may use an unregistered VTC for evaluation
purposes only for no more than fourty-five (45) days. After this period
you must register VTC or discontinue usage. On registering,
you enter into a License Agreement with Newcomer Technologies
for continued usage of the program. Before ordering, please read
the License Agreement.
Now you can register the DOS version of VTC for US $49.00
Or you can register BOTH the DOS and OS/2 versions!
For US$80.00 you get two programs! VTC-DOS and VTC-OS/2
Mark on the order form that you want to be added to the OS/2 list when
you send in your order!
We have chosen the "drop dead" method of enforcement.
There are NO restricted or crippled features in VTC
This version drops dead on Mar. 28, 1994
NOTE:
. Registration of either version of VTC above is for lifetime
and entitles you to access upgrades of the specific version
registered.
Newcomer Technologies encourages each of you to register VBBS!
There are now 2 main ways to register VTC!
A. Send me the check or money order! :)
B. CREDIT CARDS: Visa and MasterCard accepted
A. Send me the check or money order! :)
1.) Send a check for $49.00 U.S. Dollars to
Dan Newcomer
6320 Holbrook Dr
Huber Heights, Oh 45424-3560
a.) My favorite way to get you a registered copy:
Log me onto your BBS as VTC Author
use the above info
Send me a password with your check or money order
I will log on and upload your registered copy.
b.) My 2nd favorite way:
I will create an account for you on my BBS and e-mail you when you can pick
up your file attatched copy.
c.) Least favorite way :
State the size disk you need.
We will include:
1) Latest registered copy.
2) Latest Shareware Copy
Note: The above applies to high density diskettes only. On low density
diskettes (360 and 720K) we can only fit the registered version of the
software.
Form NEWCOMER TECHNOLOGIES
VTC-1 6320 Holbrook Dr.
Huber Heights, Oh 45424
Name ____________________________
Company ____________________________ Voice Phone (___)___-____
Title ____________________________ Data Phone (___)___-____
Address ____________________________ Fax Number (___)___-____
City ____________________________ State/Province ___________
Country ____________________________ Zip/Postal Code___________
Shipping Address(if different) ________________________________
_______________________________________________________________
E-Mail Address _____________________ BBS Name _________________
Version of VTC desired (DOS or OS/2)
B.) CREDIT CARDS: Visa and MasterCard accepted
VOICE ORDERS: Contact Virtual Technologies (210) 787-2443
The Voice Order Line is open Mon.-Fri 9:00 AM to 6:30 PM CST.
This telephone number is for CREDIT CARD ORDERS ONLY.
Credit Card Orders Offer The FASTEST Registration Available.
FAX ORDERS: (210)787-2443 (210)787-8974
Purchase Orders accepted
ONLINE CREDIT CARD REGISTRATION:
Please call The Business Board at (210)787-8974 14.4 v32bis
. Prices, terms, availability and specifications subject to
change without notice.
. NO Surcharge for credit card purchases. Sorry, we currently
accept only VISA and MasterCard credit cards.
. Any product refunds are in the form of store credit only.
. Returns require prior authorization. No return on used or
mis-ordered products.
. Naturally, we do not charge your credit card account until
the product is ready to ship.
. Due to copyright laws, opened software is non-returnable.
. Sorry, we cannot guarantee hardware or software compatibility.
. For your protection, we check for stolen credit cards.
. Other Charges: Add 6% for orders outside of North America.
There are no additional or hidden charges. No CODs accepted.
Form VIRTUAL TECHNOLOGIES Fax:
1093 P.O. BOX 1423 210-787-2443
ALAMO - TX 78516 210-787-8974
Name ____________________________ Purchase Order ___________
Company ____________________________ Voice Phone (___)___-____
Title ____________________________ Data Phone (___)___-____
Address ____________________________ Fax Number (___)___-____
City ____________________________ State/Province ___________
Country ____________________________ Zip/Postal Code___________
Shipping Address(if different) ________________________________
_______________________________________________________________
E-Mail Address _____________________ BBS Name _________________
LICENSE AGREEMENT
TERM
This license is effective until terminated. You may terminate it
at any time by destroying all copies of the Software covered by
this Agreement. It will also terminate upon conditions set forth
elsewhere in this Agreement or if you fail to comply with any
term or condition of this Agreement. You agree upon such termination
to destroy this Software, including all copies, functionally-equivalent
derivatives, and all portions and modifications thereof in any form.
LIMITED WARRANTY
This Software is provided 'as is' without warranty of any kind, either
expressed or implied, including, but not limited to, the implied
warranties of merchantability, and fitness for a particular purpose.
The entire risk as to the quality and performance of this Software
is with you, should the Software prove defective, you (not Newcomer
Technologies) assume the entire cost of all necessary servicing,
repair, or correction. Newcomer Technologies does not warrant that
the functions contained in the Software will meet your requirements
or that the operation of the Software will be uninterrupted or
error free. However, Newcomer Technologies does warrant the
diskette on which the Software is furnished to be free from defects in
materials and workmanship under normal use for a period of ninety
(90) days from the date of purchase. Newcomer Technologies entire
liability and your exclusive remedy shall the replacement of any
diskette not meeting Newcomer Technlogies "Limited Warranty" and
which is returned to Newcomer Technologies. In no event will
Newcomer Technologies be liable to you for any damages, including
any lost profits, lost savings or other incidental or consequential
damages arising out of the use or inability to use the Software
even if Newcomer Technologies or its authorized representative has
been advised of the possibility of such damages, or for any claim
by any other party. Some states do not allow the limitation or
exclusion of liability for incidental or consequential damages, so the
above limitation or exclusion may not apply to you. This warranty
gives you specific rights and you may also have other rights which
vary from state to state or within foreign countries.
GENERAL
You may not sublicense, assign, or otherwise transfer this License
or Software except as expressly provided in this Agreement. Any
attempt to otherwise sublicense, assign, or transfer any of the
rights, duties or obligations hereunder is expressly prohibited
and will terminate this Agreement. All Agreements covering this
Software (including but not limited to any and all updates,
upgrades, and enhancements to this Software or any portion thereof,
bearing the same registration number) shall be deemed to be
counterparts of one and the same License Agreement instrument.
By installing or using this software, you acknowledge that you have
read this agreement, understand it, and agree to be bound by its
terms and conditions. You further agree that it is the complete
exclusive statement of this Agreement between us, which supercedes
any proposal or prior agreement, oral or written, and any other
communications betrween us relating to the subject matter of this
Agreement.
This Agreement shall be governed by the laws of the state of
Ohio.
Section 1 - Overview
The Virtual Teleconference (hereafter referred to as VTC) has been designed
to place Virtual BBS where it should be - on top in every BBS category.
Roland De Graaf has done an exceptional job of making Virtual BBS the most
configurable BBS in the market - the message and network handling is
definately the best in the world. It's only short-coming WAS it's
teleconference. VBBS could not compete with Galicticom's Major BBS
or DLX -- it's TC was just a little too weak.
Virtual Teleconference takes TC's even further, with RIP support, greater
configurability, and minimal SysOp maintainance.
The tables have turned.
1.01 - Features:
- Dynamic "Room" creation from the command line or from the teleconference!
- Easy Installation!
- Room security
- User's "own" and configure their own room
- RIP supported!
- Detailed logging
- A TrueChat mode for remote users
- Configurable ACTION commands
- Intelligent ACTION commands (VTC knows when to personalize)
- Configurable internal commands
- Script support
- Interprocess functions (users can affect each others' sessions)!
- Shrinks out of memory to run external programs!
2.00 Installation
2.01 To install Virtual Teleconference follow these simple steps:
a) Unarchive VTCxxx.zip into your main VBBS directory.
b) Change your Start.FB and File.FB to read:
Z 001 4 PROCESS.EXE %1 /fMAINTC /nMain /o1
IMPORTANT ** User number 1 must be the first person to enter the VTC
The first time VTC is run it will create two sub-directories:
TC and V. They are located off of your data directory.
Also several files are created in the TC sub-directory.
See section 8 for an explanation of the file names and extensions.
***********************************************************************
It is highly encouraged that NO OTHER USER be online while installing
this program. That you turn off your HD catche before you install VTC.
Leave off your HD Catche until after you have entered then exited VTC
for the first time.
*********************************************************************
Files in the archive:
VTC.exe
Process.exe
About.rip
TCmenu.rip
Install.doc
Readme.doc <----only if there are last minute changes
Register.txt
Support.doc
VTC.doc
Suggest.txt
2.02 You can run VTeleocon as a door, from a menu, or from scripts.
The command line paramaters are:
PROCESS.EXE %1 /fMAINTC /nMain /o1
^^^^^^
|______MUST BE A LEGAL DOS FILE NAME
ALL OTHER ROOMS MAY BE CALLED ANYTHING. THE MAIN ROOM MUST BE
A LEGAL DOS FILENAME!!!!!!!!!!!!!!
/F - the filename for the room
/N - the long name of the room
/O - the user who shall own the room
VTelecon first checks to see if the file specified in the /F parameter
exists. If it does not, it creates a room with name <room name> and owner
<owner number>.
If the file already exists, the other parameters are ignored.
When a user enters the teleconference for the first time, a special room
is created for him to use. The name is "<UserName>'s Private Room".
3 - VTC Security
3.01 User Level
There are 3 security levels for the Virtual Teleconference. The user level,
room owner level, and operator level. The users are entirely at the mercy
of the room owners and teleconference operators. What commands they may
use, which rooms they may enter, or whether they are even allowed into the
teleconference is under the control of Room and TC Operators. The basic user
is basically a peon in most rooms he will enter.
3.02 Room Owner
Every room has an owner. The room owner designs nearly every aspect of his
room, from what commands may be accessed by the general user population, to
the color schemes, to which commands and scripts will be run automatically
for certain events. (See Edit Room and other related commands)
Each user owns at least one room --their private room. They may give their
rooms away to other users, delete their rooms, or configure them to their
liking.
As a sysop, you know that everyone likes to be a little creative, and feel
that they are on the "inside" of what's going on. Rooms are a creative outlet
for your users to mold their corner of cyberspace to their liking, without
violating YOUR rules.
3.03 Teleconference Operators
The guru of teleconferencing is the TC Operator. There is one MAIN operator
who can do anything and go anywhere. He is god in the teleconference, able to
create and destroy cyberspace on a whim (and a few keystrokes). The MAIN
operator is BBS User #1 (the SysOp). He can assign his legion of TC demi-gods
(other TC Operators) and restrict some of their actions.
3.04 Room Defaults
Take a few minutes to set up the MAIN room. It will serve as the
template for the rooms created thereafter.
All of the main room's defaults will be used by each room as it's defaults.
We recommend you take the time to /EDIT ROOM before you allow
anyone else to use the VTC.
If you want a log of everyones actions, now would be a good time to type
/tclog on
4.00 User Input
4.01 All input is preceded by a / key.
There are two types of user input: COMMANDS and ACTIONS
4.02 Commands are things that are done by the user or to the user
by the system. I.E. /GO PRIVATE takes the user to his/her
private room.
Some COMMANDS are restricted to the SysOp or the TC operator.
4.03 Command Listing -
HIDE
Usage: HIDE
HIDE will hide you from everyone but the sysop until you re-enter the VTC.
You will be exited immediatly from the VTC.
----------------------------------------------------------------------------
LDOS
Usage: LDOS
The LDOS command is a secure, local, DOS shell. It loads COMMAND.COM and
allows the TCO (user #1) to run a DOS session locally. No one other than
user #1 can use this command, and the sysop MUST be local, otherwise the
command will not even execute.
----------------------------------------------------------------------------
CLS
Usage: CLS
CLS is identical to DOS's CLS command. It clears the local and remote
screens.
----------------------------------------------------------------------------
TCRLOG
Usage: TCRLOG [DETAIL|OFF|ON]
TCRLOG sets or views the logging attributes for the current teleconference
room.
Options:
DETAIL - Sets the detail for the log 1 = lowest, 3 = highest.
OFF - Disables logging for the current room.
ON - Enables logging for the current room.
If no parameters are passed to TCRLOG, then the DETAIL and ON or OFF
settings will be displayed.
*Note: The ON and DETAIL switches cannot supersede the TCLOG settings. If
the TCLOG is OFF, then toggling the TCRLOG ON will have no effect. Similarly,
if the TCLOG DETAIL is set to 2, setting the TCRLOG to any value higher than
2 has no effect.
----------------------------------------------------------------------------
TCLOG
Usage: TCLOG [DETAIL|OFF|ON]
TCLOG sets or displays the settings for the teleconference log. The settings
for the TCLOG define the limits for each room's log status. If the TCLOG is
toggled OFF, then no room may log activities. If it is ON, any room may
have its TCRLOG toggled OFF. No room may have its DETAIL set higher than
TCLOG.
Options:
DETAIL - Sets the detail for logging 1 = Lowest, 3 = Highest
OFF - Toggles ALL logging off
ON - Enables logging for those rooms who have their TCRLOG ON and
DETAIL set greater than 0.
If no parameters are passed to TCLOG, then the DETAIL and ON or OFF status
will be displayed.
----------------------------------------------------------------------------
LIST
Usage: LIST ROOMS|ACTIONS|COMMANDS|FILTER|LINKS
Options:
ROOMS - Lists all rooms accessable by the user.
ACTIONS - Lists all actions the user may perform.
COMMANDS - Lists all commands the user may access.
FILTER - Lists all words and phrases contained in the PROFANITY FILTER.
LINKS - Lists all exits to other rooms from the current room.
----------------------------------------------------------------------------
UNLOCK
Usage: UNLOCK <user name>
UNLOCK reverses the effect of the LOCK command.
----------------------------------------------------------------------------
LOCK
Usage: LOCK <user name>
The LOCK command terminates <user name>'s session and LOCKs his account.
<user name> may not return to the teleconference until his 'L' flag has
been toggled OFF either by the UNLOCK command, or through EDIT USER.
----------------------------------------------------------------------------
SENDFILE
Usage: SENDFILE [drive:][path\]<file name> <user name>
The SENDFILE command sends a text file to another process. <user name>
will view the file in its entirety with no pausing/page-breaks. Pressing
the SPACEBAR will terminate the file transmission.
Example: SENDFILE C:\VBBS\VTC.DOC Dan
- Dan, who is in the same room with you, views the VTC.DOC file.
----------------------------------------------------------------------------
SENDFILEP
Usage: SENDFILEP [drive:][path\]<file name> <user name>
SENDFILEP behaves exactly the same as SENDFILE, except pagebreaks/pausing
is ACTIVE.
----------------------------------------------------------------------------
COMMAND
Usage: COMMAND <teleconference command> @<user name>
COMMAND causes <user name>'s process to execute <teleconference command>.
The commands available are those in the room's command list, and only
commands the user has access to.
----------------------------------------------------------------------------
SENDRIP
Usage:
SENDRIP <rip file> <user name>
SENDRIP displays a RIP graphics file to another process. If the process
does not have RIP graphics active, the command is ignored.
An example usage may be RIP Actions.
----------------------------------------------------------------------------
VIEWRIP
Usage: VIEWRIP <rip file>
VIEWRIP sends a rip file to the user activating VIEWRIP. If the user does
not have RIP graphics, the command is ignored.
----------------------------------------------------------------------------
EVICT
Usage: EVICT <user name>
A room owner, Teleconference Sub-Operator, or the Teleconference Operator
may evict a user from the current room. The user is sent to either
the first room created, or his private room.
----------------------------------------------------------------------------
KILL
Usage: KILL <user name>
The command terminates <user names>'s session. It does not toggle the user's
'L' flag, so his account LOCK status is unchanged by a KILL.
----------------------------------------------------------------------------
CREATE
Usage: CREATE <room name>
The Teleconference Operator, or a Sub-Operator with either flags 'Z' or 'O'
set may create new rooms with this command. The room's owner is the
creator of the room by default, and is named <room name>.
----------------------------------------------------------------------------
UNINVITE
Usage: UNINVITE <user name>
A room owner or Operator may UNINVITE users from a private room. These users
will no longer have access to the room. The exceptions are Operators with
the 'Z' flag set. These users can enter most rooms.
----------------------------------------------------------------------------
INVITE
Usage: INVITE <user name>
Users do not have access to private rooms by default. To enter a private
room, they must first by INVITEd by the room's owner (or an operator with
access to the room).
----------------------------------------------------------------------------
?
H
HELP
Usage: H|?|HELP <teleconference command>
All three of these commands accomplish the same thing. They display the
detailed help text for the <teleconference command> specified. Help by
itself displays the <roomfilename>.HLG text file --a generic help file
for the current room.
Example: /? HELP
This command displays help for help.
----------------------------------------------------------------------------
JOIN
GO
Usage: GO P|MY ROOM|<room name>|<user name>
This is one of the most powerfull commands in the teleconference. A user
travels from room to room with the GO or JOIN command (the two are
synonamous). What room he JOINs depends on the parameter passed to a JOIN
or GO.
Options:
P - GOes to the user's Private Room.
MY ROOM - GOes to the user's Private Room.
<room name> - Sends a user to a room named <room name> (if he has access).
<user name> - Takes a user to the same room that <user name> is occupying
(again, he must have access to the room).
----------------------------------------------------------------------------
CHAT
Usage: CHAT <user name>
The CHAT command initiates or responds to a CHAT request. When a CHAT is
issued, the user enters a two-way TRUE-CHAT mode with <user name>. Both
users must issue a CHAT command to start the two-way TRUECHAT.
----------------------------------------------------------------------------
VIEW
Usage: VIEW TCLOG|CHALKBOARD|MENU|NEWS
The VIEW command displays various teleconference files depending on the
parameter it is passed.
Options:
TCLOG - Views the teleconference LOG file. The detail an Operator
may view is idicated by his W,X or Y flags, where
W = Detail Level 1, X = Detail Level 2 and
Y =Detail Level 3.
CHALKBOARD - Views the current room's chalkboard (if active).
MENU - Views the teleconference opening MENU.
NEWS - Views the teleconference NEWS file (if active).
----------------------------------------------------------------------------
IGNORE
Usage: IGNORE <user name>
The teleconferene will block any broadcasts by <user name> to the user
that issues an IGNORE.
----------------------------------------------------------------------------
UNIGNORE
Usage: UNIGNORE <user name>
Reverses the effects of an IGNORE.
----------------------------------------------------------------------------
WHO
W
Usage: W|WHO
Displays users both on the BBS, and users in the room with the user
issuing WHO.
----------------------------------------------------------------------------
QUIT
Q
X
Usage: QUIT|Q|X
Terminates the teleconference session.
----------------------------------------------------------------------------
ACTIONS
Usage: ACTIONS
Lists actions for the current room.
----------------------------------------------------------------------------
USEREDIT
Usage: USEREDIT <user name>
USEREDIT edits a user's account. This is where the main Teleconference
Operator assigns Sub-Operators.
----------------------------------------------------------------------------
EDIT
Usage: EDIT ACTIONS|COMMANDS|NEWS|CHALKBOARD|ROOM|DEFAULTS|FILTER
The EDIT command edits the settings indicated by the parameter it is passed.
Options:
ACTIONS - Edits the ACTION file for the current room (room owners,
Teleconference Sub-Operators and the Teleconference Operator
only).
COMMANDS - Edits the COMMANDS for the current room. Same security
restrictions as ACTIONS.
NEWS - Edits the room's NEWS file.
CHALKBOARD - Edits the rooms CHALKBOARD.
ROOM - Edits the rooms various settings. Same security as ACTIONS
and COMMANDS.
DEFAULTS - Edits the user's default settings: Default room, entrance
and exit messages, RIP Graphics, etc...
FILTER - Edits the room's Profanity filter.
----------------------------------------------------------------------------
FILTER
Usage: FILTER [ON|OFF]
The filter toggles or displays the filtering status for the current room.
Only Room Owners, TC Sub-Operators and the TC-Operator may issue this
command in a room.
Options:
ON - Toggles the room's profanity filter ON.
OFF - Toggles the room's profanity filter OFF.
No parameters displays the FILTER's current setting.
----------------------------------------------------------------------------
RIP
Usage: RIP [ON|OFF]
The RIP command toggles or displays a users RIP graphics status.
Options:
ON - Toggles RIP graphics ON.
OFF - Toggles RIP graphics OFF.
No parameters displays the user's current RIP status.
----------------------------------------------------------------------------
RLINK
Usage: RLINK
The RLINK command LINKs the current room to the main teleconference
pool. All LINKed rooms have exits to all other LINKed rooms.
(See the section regarding LINKs for a more detailed description of how
LINKs work).
----------------------------------------------------------------------------
RUNLINK
Usage: RUNLINK
UNLINKs a room from the main teleconference pool. The only exits from an
UNLINKed room are to rooms that are connected via a LINKTO.
(See the section regarding LINKs for a more detailed description of how
LINKs work).
----------------------------------------------------------------------------
RLINKTO
Usage: RLINKTO <room name>
RLINKTO establishes a LINKTO to another room. This is a one-way link,
meaning that if a user GOes or JOINs a room with a LINKTO, he cannot return
unless there is another LINKTO from the room he enters to the room he left.
(See the section regarding LINKs for a more detailed description of how
LINKs work).
----------------------------------------------------------------------------
RUNLINKTO
Usage: RUNLINKTO <room name>
RUNLINKTO breaks a LINKTO to another room.
(See the section regarding LINKs for a more detailed description of how
LINKs work).
----------------------------------------------------------------------------
WAITKEY
Usage: WAITKEY
WAITKEY pauses until any key is pressed
See SENDS for an example.
-----------------------------------------------------------------------------
SENDS
Usage: SENDS <text string>
SENDS is used primarly with WAITKEY to send a text string to the terminal
an example would be :
SENDS "Press any key to continue"
WAITKEY
-----------------------------------------------------------------------------
PAGE
Usage: PAGE <user> <message>
The PAGE command sends an online <message> to <user>.
Example:
/PAGE Justin Hello!
-----------------------------------------------------------------------------
4.04 ADDING COMMANDS
Not all of the commands listed above are listed when a user does a
/LIST COMMANDS. Some of the above commands are more script
orientated.
The TC operator, SysOp, or ROOM Owner may add COMMANDS to the list
available with the /list commands function.
Once added they may be used according to the internal security of
the command.
To add an internal command to the VTC command list do the following:
Type
/edit commands
The VTC will respond with
[A] add a command, [R] remove or [X] Exit:
Type A
The VTC will respond with
Example command syntax:
Command name: ZAP <- All caps, command name
Command: KILL <-This terminates a user's session
Is this a [C] Command, [S] Script or [X] Exit:
It can be a command if you want to do only one function.
It needs to be a script if you want to do multiple functions.
NOTE - The script needs to already exist in your VBBS\DATA\TC\V
directory. (see the section on scripts)
4.10 ACTIONS
VTC supports configurable action files. These files can be edited from
within the teleconference, or the SysOp may edit them from any ASCII text
editor.
The teleconference 'actions' are so users may add some emotion to their
discussion. Actions may be performed on one or more other users in the
teleconference. To use an action, type a '/' (do not include qutoes) and
the action name, followed by the user(s) you would like to do the action to.
e.g.:
/<action> [<user name> [[,|AND] <user name>]...]
If you would like to KICK a user named Justin, then the command would look
like:
/KICK JUSTIN
or
/KICK JU - partial names are allowed.
If you would like to kick three users named Justin, Dan and Melissa, the
command would look like:
/KICK JUSTIN, DAN AND MELISSA
or
/KICK JU, DA, MEL
If you would like to kick everyone in the teleconference (having a real
bad day), the command would look like:
/KICK ALL
Sometimes you may want to say something only to one user in the room with
you. You can 'whisper' a message to them by typing a '/' and their name
followed by the message.
E.g.:
/<user name> <message>
If you would like to whisper a message to Justin, the command would be:
/Justin Hello Justin!
or
/Ju Hello Justin!
The format of ACTION commands is as follows:
@USER1@ - the user doing the action.
@USER2@ - the user getting the action.
<text> - the action itself.
There are 3 lines for each commad:
<ACTION> - all caps
<broadcast to teleconference>
<broadcast to the user doing the action>
example:
KICK
@USER1@ is kicking the heck out of @USER2@!
You kick the heck out of @USER2@!
Any argument can be omitted. If you don't want do display a line, simple
place a - on the line.
JUMP
@USER1@ is jumping up and down!
-
4.20 Default Actions
KICK
@USER1@ is kicking the heck out of @USER2@!
You kick the heck out of @USER2@!
HANDSHAKE
@USER1@ is shaking hands with @USER2@.
Shake, shake... @USER2@'s arm rattles about.
SMILE
@USER1@ is smiling at @USER2@.
Look at those pearly whites! :)
CRY
Tears stream down @USER1@'s face blaming @USER2@ for his troubles!
What a guilt trip!
TISSUE
@USER1@ hands @USER2@ a tissue.
How nice of you.
TIME
@USER1@ asks @USER2@ what time it is.
Maybe @USER2@ will tell you!
LAUGH
@USER1@ is laughing at @USER2@!
Hahahahahahahah!
WAVE
@USER1@ is waving at @USER2@.
Wave, wave.
TICKLE
@USER1@ is tickling @USER2@!
Hehehehehhehehe.
KISS
@USER1@ gives @USER2@ a big wet kiss!
Smoooch!
SMACK
@USER1@ smacks @USER2@!
Whap! Ouch!
HUG
@USER1@ gives @USER2@ a big hug.
Awwww!
NOD
@USER1@ nods at @USER2@
Nod, nod.
SLAP
@USER1@ slaps @USER2@... hard!
Ouch!
GRIN
@USER1@ is grinning at @USER2@.
:>
WINK
@USER1@ winks at @USER2@.
;)
POKE
@USER1@ is poking @USER2@.
Poke. Watch where ya point that thing!
TAG
@USER1@ tags @USER2@!
Gotcha!
JUMP
@USER1@ is jumping up and down.
Having fun?
5. LINKS - ADVANCED CONCEPTS AND POWER!
The Virtual Teleconference contains a VERY powerfull feature: Room Linking.
Room Links allow the sysop to create entire teleconference sub-systems on
his BBS, with strengthened security. A well LINKed teleconference can look
VERY large. Some adventurous SysOps may even create interactive, multi-user
role-playing worlds with labyrinths, portals, taverns, etc... by utilizing
the power of LINKs and LINKTOs.
Business Boards can create secure environments for their users to interact
and share information. If the LINKs are properly made, not even teleconference
Sub-Operators may wander into restricted areas.
Here is an example of a small linking scenario of a small BBS operator.
His BBS contains 6 teleconference rooms (I said it was small), named
Room A, Room B, Room C, Room D, Room E and Room F.
Room A----Room B
|\ /|
| \ |<-LINKs
|/ \|
Room C----Room D
|
|<-LINKTO
|
Room E
Room F <- no LINKs
Rooms A-D are all LINKed, meaning that they are part of the Main
Teleconference "pool". Every room in the pool has access via GO or JOIN to
every other room in the pool. Note that JOIN and GO have their own security
restrictions. Lets say that User #2, a co-sysop named Joe, is also a
Teleconference Sub-Operator. He may access ANY rooms linked to the room
he is currently in. Lets also assume that Joe enters the teleconference
in Room A. From Room A he may enter Rooms B, C and D. Room D is the
SysOp's Private Room, and only Sub-Ops and invited users may enter the
SysOp's Private Room (Room D). Joe, being a Sub-Op has access. From Room D
he may access Room E, but ONLY froom Room D.
See that little Room F? It has no links whatsoever to any room in the
teleconference. The SysOp uses THIS room for his command center in this
scenario. The SysOp has add commands that he doesn't want Sub-Operators
to have access to in this room.
Unlinked rooms can only be accessed by User #1 (the main teleconference
operator) and/or the room's owner.
Let's take this scenario a step further, and say that the SysOp's BBS is
RPG (Role Playing Game) oriented. A user would like to run an RPG, but
only let participants have access to the game. Here's a map of the
teleconference for the RPG:
Room A----Room B
|\ /|
| \ |<-LINKs
|/ \|
Room C----Room D
|
|<-LINKTO
|
Room E
Room F <- no LINKs
RPG-1-----RPG-2-----RPG-5
\ |
\ |
\ |
\ |
\ |
RPG-3-----RPG-4-----RPG-6
| |
| |
| |
RPG-7--------------RPG-8
It's a small world, but enough for this illustration. Notice that all of the
"RPG" rooms are not linked to ANY room in the main teleconference. There
are 2 ways to access the RPG Rooms: from the BBS on the command line, OR
through one of the RPG rooms.
The Room Owner for the RPG's is User #45, Axis. He sets RPG-1 as Private,
and adds all of the participants to the room's invitation list. Only the
invited users may access any room in his role-playing world, since they
must first enter HIS room to access other "RPG" rooms.
6. SCRIPTS
The VTC scripts are a simple, yet powerful tool to configure
the VTC world.
6.01 You may use ANY of the internal COMMNADS in your script.
A script will be found in your C:\VBBS\DATA\TC\V sub-directory.
6.02 Script Names:
Scripts are named after the ROOMname.x where x = 0 - 999
Therefore you may have up to 1000 scripts in each room.
6.03 Syntax:
Script syntax is one command per line
6.04 Example:
Script Commands Explanation, not part of script
--------------- -------------------------------------
MAINTC.0 <--Name of script (Main room script 0)
CLS <--Clear Screen
VIEWRIP TCMENU.RIP <--Send the main RIP menu for those using RIP
VIEW CHALKBOARD <--Send Chalkboard
WAITKEY <--Wait for a keypress
SENDS "PRESS ANY KEY TO CONTINUE" <-- Tell the user what to do
VIEW NEWS <--Send the News
WAITKEY <--Wait for a keypress
SENDS "PRESS ANY KEY TO CONTINUE" <-- Tell the user what to do
VIEW MENU <-- Sends the non-rip menu
6.05 Running Scripts
Script 0 will run automaticly when the room is entered.
All other scripts may be run as commands.
See the section on adding commands.
7. MENUS
The MAIN room menu is the default menu for each room created there after.
However each ROOM OWNER may create his/her on menu.
VTC supports VBBS color code (HEART ANSI), Normal ANSI, ASCII and RIP.
With RIP support we expect to see lots of RIP characters and objects
created to be displayed.
8. FILES - What are all of these files?
8.01 - File prefixes
Teleconference room's may be named either from the teleconference itself,
or from the command line.
If a new room is created from the command line, the file name prefix is
indicated in the /F parameter.
The file name prefix for rooms created in the Virtual Teleconference are
dependant on the kind of room created.
User's private rooms have a prefix of "TCU<x>" where x is the user number
of the room owner.
Rooms created with the /CREATE command have a slightly more complex prefix.
The file name is actually a time-stamp of the room's creation. The format
is: DDMMHHMM where DD is a 2 digit day of the month, MM is a 2 digit month
of the year, HH is the hour on a 24 hour clock, and MM is the minute.
8.02 File extensions
.ACT
Files ending with the ACT extension are the teleconference's ACTION files.
They contain all of the ACTION and COMMANDS for the associated teleconference
room.
.HLP
This is the COMMAND sensitive help file. The teleconference seeks this file
for the help topic specified in the /HELP <command> command.
The HLG file is an ASCII file. It may be edited with any ASCII based editor
(such as MS-DOS's EDIT.COM).
.HLG
The HLG is the general help file for the Virtual Teleconference. This is the
file that is sent to the user when they type /HELP with no parameters.
The HLG file is an ASCII file. It may be edited with any ASCII based editor
(such as MS-DOS's EDIT.COM).
.INV
INV files are invitation lists for the associated teleconference room. The
INV file is checked only if the room is PRIVATE by default.
This is a RANDOM ACCESS file. It should not be edited with a text editor.
.EXC
This is the EXCLUSION file for a teleconference room. In a public room, all
users in the EXC file are denied access.
This is a RANDOM ACCESS file. It should not be edited with a text editor.
.PF
This extension indicates the PROFANITY filter file. This file contains
words or phrases that are to be intercepted by the teleconference if the
/FILTER is ON.
.PFT
This is the text file that is displayed when an active filter is triggered.
9. The Future
The future for VTC is exciting! Like VBBS it will not stand still!
The world of VTC is unlimited! The only limit to the size of the
VTC world is the amount of HD space you care to delegate to the
program. RPGs and MUDS are a real and active possibility.
10. Support
There are several ways to get support for VTC.
I have started a message base on VNET and HOG called VTC SUPPORT
I have started a FILE base on VNET and HOG called VTC ADD-ONS
The message base will be checked daily Dan Newcomer.
You may E-mail your request for help to :
Dan Newcomer at 1@1513000 VNET or for HOG use 1@5130
Give The Cottage By The Stream a call at (513) 235-2605 (node 1)
I expect to have at least two more call in nodes on line by Jan. 1994
I now have a local node if you want to call and see this program in
action. Just give me a page and I wil get on the other computer.
I would highly suggest you call using RIPterm.
11. Where to get VTC updates?
The latest copy of VTC and any add-on programs will be available
from The Cottage By The Stream at (513) 235-2605 at 14.4 speed.
You may log on using the Guest account. ID = 245 PW = GUEST
You may use Vnet or FIDO FREQ to get a copy of the VTC file
Use the Magic name of VTC. Vnet 1513000, HOG 5130, FIDO 1:110/645
I will also upload VTC to several main Boards around the country.
Including, but not exclusive to, Starfare's Gem, Virtual Tech.,
Business Board, Ceder Republic, Shark's Place, and Authors BBS.
The file is large enough that we cannot honor file attatchment requests.
12. Beta testers
Our thanks go out to the following for Beta testing this product and
sending us bug reports: