Click above to get retro games delivered to your door ever month!

     This  chapter  describes  details  about  the implementation of the
     WildCat! 4.x messagebase format in GoldED.

     The WildCat format does not have a quick method of finding  deleted
     messages via the index file. This means that deleted messages  will
     still be visible,  but marked with  the DEL attribute.  When GoldED
     deletes a message, it will at first seem to be gone, but after  the
     next scan, it will be back again, with the DEL attribute.

        WildCat features which are not supported yet:

        - The userbase.
        - The message unread chain.
        - The message from/to title.
        - The message network name.
        - The message internal and external attach.

     There is not yet any AREAFILE WildCat. You must define the areas by
     hand using the AREADEF keyword, like this:

        AREADEF MYTEST "My Test" 0 Echo WCat <path\basename> etc.

     There is a keyword WILDCATUSERNO,  which works just like the  other
     <msgbase>USERNO  keywords.  By  default  GoldED  will use the first
     record in the lastread  file (*.LRD), so if  you are not the  first
     person in  the userbase,  or you  are sharing  the messagebase with
     others, you may  have to change  this user number.  The userbase is
     currently not supported (ie: you can't set the number to -1 to  let
     GoldED find the correct user and lastread automatically).

     NOTE: The WildCat support is currently not very well-tested, so use
     it with caution. In my limited  testing, I have not found it  to be
     damaging the messagebase, but you  should probably test it on  less
     important areas and/or make backups until it is determined that  it
     is safe.

        <sorry - this chapter is not completed yet>