Getting Started

This document will help you get started with the Demo JASS Syntax Checker.

1. Download the latest version. If you are running Windows, also download and install a Java Runtime Environment if you do not already have one.

2. Double-click JassDemo.exe if you are running Windows, or JassDemo if you are running Mac OS X.

3. If you want to check an entire script file, then click Browse and select the script you want to perform a syntax check on.

4. If you want to check a small fragment of code, click Code Fragment. Then enter your code fragment into the text box. For example, you can copy and paste the text from a custom text trigger here (make sure to select Map Script if that is the case). ^*

5. If the script is an AI Script, select AI Script; if it is a map trigger script (war3map.j), select Map Script; if it is a custom common.ai or Blizzard.j, check Library.

6. Click Check to perform the syntax check.

7. You will either receive a message that there were no errors or a list of the syntax errors found.

^* If you check a fragment of code like a single custom text trigger, note that the syntax checker will still complain that your global variables are undefined because it does not know about the globals block that the World Editor generates later. You can just ignore these warnings since it will find all the other errors anyway.

Reporting Bugs

This is still alpha software, so there are bound to be bugs. If you find one, please report it in the following manner:

• If the checker crashes or otherwise behaves badly, try to tell me how to reproduce it.
• If the checker finds no errors in your script, but it does not work in Warcraft III, first make sure it is being loaded (e.g., put a known good script in its place and make sure that works), second try to narrow down where the problem is in your script (i.e., remove as much as you can from your script so that it still passes the checker but does not work in Warcraft III), or better yet, figure the problem the checker isn't catching yourself. :) Send me the narrowed down script or code fragment and an explanation of what you think the problem might be.
• If the checker finds errors in your script but it works fine in Warcraft III, then send me the script (or a narrowed down version of it that still exibits the error). NOTE: There is an error in Blizzard.j on line 6481 involving a return value that does not conform to the declared type of the function. This is indeed an error but it is allowed by Warcraft III's type checker. Blizzard has (unofficially) indicated that this will probably be fixed in the expansion.

Report bugs to jeffpang+jasstools@cs.cmu.edu.