home *** CD-ROM | disk | FTP | other *** search
- ADDHINT for Game Hint Pro v1.2
- Written by James R. Davis
- (C) Copyright 1995 - All Rights Reserved
-
- This is a quick and handy utility for creating a file called GAMEHINT.ADD to
- be submitted for adding hints to the Game Hint Database. It is in NO WAY a
- complete and bug free program. It is a simple program written to take alot of
- the work out of typing in your game hint. It places information into the
- format given below in the GAMEHINT.ADD file.
-
- The format of the GAMEHINT.ADD file is as follows:
-
- 1: ***
- 2: GAME TITLE
- 3: MAJOR INDEX SEARCH
- 4: 3 Letter System Code (See Below)
- 5: Date Hint was Written
-
- ...
-
- 6: ---
- 7: Hints Origination
-
- Line 1: This is the game hint identifier (***). Each hint must begin with
- this line.
-
- Line 2: The Game's Title - This is a string that can contain any text, but
- cannot be over 40 characters long and must be in UPPER CASE.
-
- Line 3: Index Search String - This is like the above line, only contains more
- information about the game other then just the title. This can
- remain blank, but we urge some short descriptive. For example: If
- the game is a FOOTBALL game, your would enter on this line "SPORTS
- FOOTBALL"
-
- Line 4: This contains the 3 letter code for the system that the game is for.
- It can be one of the following:
-
- Code System Type
- ---- --------------------
- NG* - Nintendo Game Genie
- SN* - Super NES Game Genie
- SG* - Sega Game Genie
- GB* - Game Boy Game Genie
- GG* - Game Gear Game Genie
- NIN - Nintendo 8 Bit
- SN - Super Nintendo
- SG - Sega Genesis
- GB - Game Boy
- GG - Game Gear
- SCD - Sega CD
- 3DO - 3DO
- JAG - Atari Jaguar
- ARC - Arcade
- 32X - Sega 32X
- PC - Personal Computer
- T16 - Turbo Grafix 16
- LNX - Atari Lynx
- SAT - Sega Saturn
-
- Line 5: This line contains the date the hint was written in the format of
- MM-DD-YY.
-
- Anything between lines 5-6 is considered the body of the hint. We like to
- maintain a standard format for this area which is this:
-
- A short description line ending with a Colon at the beginning, then the rest
- of the hint body indented 2 spaces and not exceeding 72 characters in
- length.
-
- Line 6: This line contains the End of Hint identifier (---).
-
- Line 7: This contains the name/city of the origination of the hint. It can
- contain any information as long as it does not exceed 40 characters
- in length.
-
- Additional Hints:
-
- Some games contain more then 1 hint, in such cases, after the first hint is
- entered, you can continue on with another hint by using a continuation
- identifier (@@@) on a line by itself and enter the next hint in the same way
- as you would continuing from Line 5.
-
- Special Note:
-
- We advise using a ASCII text editor to create you GAMEHINT.ADD file. The
- ADDHINT program does contain some slight bugs if not used correctly and we
- are working on it, but if used properly it performs pretty well, but I would
- not depend on it. When submitting hints, check the program's database first
- to see if the hint already exists. If it does... don't even bother
- sumitting it again... it won't be considered!
-
- Submitting Hints:
-
- All GAMEHINT.ADD files to be submitted should be ZIPped in a file using the
- following naming convention:
-
- GHAxxxx.yyy
-
- Where "xxxx" is the last 4 digits of your Home phone number, and "yyy" is
- the area code of your Home phone number. When you upload the application,
- do not ZIP or archive the file. Make it a private upload by placing a "/"
- in front of the description you give the file before uploading (please be
- descriptive when giving the file a description or it may be ignored). Again,
- thank you for your interest in DavisWARE!
-
- IMPORTANT NOTE: Any hints received that do not follow these rules will not be
- considered. So please, follow the above guidelines carefully.
-
- -=> James "The Garf!" Davis! <=-
-
-