ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ
ABOUT JMOD AND THE JMOD FORMAT

John Rohner                             Difficulty: Û±±±±±±±±±

Milwaukee, Wisconsin                    Affected:  <nothing>
Immortality (414-643-1576)                         *no programming necessary*
rohner@csd.uwm.edu

Description:

   This provides a general description of the JMOD file format and
   information about what these files are.

ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

For each release, on Immortality I will maintain JMODxxyy.ZIP.  "xx" is the
BBS release number, "yy" is the JMOD version number.  Example: JMOD0901.ZIP

Roughly each month (between releases) I will create a new JMOD.  It contains
any bug fixes/enhancements I've been doing to the software since release.  
As well as JDR_BBS related stuff others do.

At the time the next version of Juggernaut is released, any code modifications
will be absorbed into the program itself--with a UNIX-like credit line for
those submitted modifications at the top of the altered modules.

For those modifications/files that cannot be incorporated into the program,
they will continue and be a part of the next JMOD series.

You should put each modification in a text file of similar format as this one.

For additional files, you should ZIP them into a .ZIP the same name as your
modification text file.

For simple code alternations, you should mention the module name (eg. 
USER_IO.BAS), the routine name (eg. GetDesc), and use the following format
for the code changes:

    |  K = 100
    |  K0 = 110
    -  IF K <> K0 _
    +  IF K > K0 _
    |    THEN K$ = "TEST" _
    |    ELSE K$ = "TEST2"

Thus, "|" means stays the same, "-" means remove it, "+" means insert it.

But to keep it from getting unreadable:

    |  K = 100
    |  K0 = 110
    -  IF K <> K0 _
    -    THEN K$ = "TEST" _
    -    ELSE K$ = "TEST2"
    +  IF K > K0
    +    THEN K$ = "TEST" _
    +    ELSE K$ = "TEST3"
    |  K1 = 200

Thus, one must strive for a happy (readable) balance when deciding on -/+'s.

Also, remember that there aren't just code change possibilities: you can do
protocols, new contents listings output formats (headers and body), more
"other BBS styles", your own styles, etc.

Also, pretty much anything you do for the first time can be a mod: telling how
to convert a WWIV bundle to .PKT format for importing, routing your phone
calls via your place-of-work's Unix system, setting up specific CD's, etc.

ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ