General EQWatcher Concepts > The Basics > EQWatcher Commands
EQWatcher Advanced runs off of two different types of information. The first type is game input. The only way EQWatcher receives input from the game itself is through the chat log. Everything you see in the chat window while playing is sent to this log, if you have logging turned on. Each line from this log is compared to all applicable triggers in search for useful information (for example, your location, or combat). The second type of information EQWatcher gathers is user input. This is simply commands given by you, the user, to EQWatcher. Each line of this information is compared to all applicable aliases. This type of information is gathered in 3 ways -- the EQ notes file, the EQWatcher Advanced window, and command files.
For the most part, the commands you give to EQWatcher directly will be through the EQ notes file. To send EQWatcher a command within EQ, you first type "/note ", then the command. This instructs EQ to leave a "note" in a file called "notes.txt", which is in your EQ directory. EQWatcher will recognize commands given this way. This is the ONLY time you will use "/note " associated with EQWatcher commands.
Most of the commands you want EQWatcher to automatically run either on startup or as you log in or out, will be done through the use of command files. You may visit that section for more information.
Probably used the least is the method of giving commands through the EQWatcher Advanced window. To enter a command, pull down the Command menu, and select Execute Command. You type your command in here and either hit enter, or click the button you see. It is fairly straightforward and fool proof.
Most EQWatcher Advanced commands have associated sounds that may be used to determine if your command was entered correctly. If you hear no sound, you can generally assume that the command was entered incorrectly. All EQWatcher commands are case sensitive, so "Play" is different than "play". You must be sure to enter the command exactly as it is shown in the documentation, or it will not work correctly. To disable these sounds (for use in a command file, for example), the command is "quiet". To enable them again, the command is "verbose".