Difference between revisions of "AGI/Specifications/Logic"

     assign.v(v50,0);

     assign.v(v50,0);

     program.control();

     program.control();

Multiple commands may be placed on the one line:

Multiple commands may be placed on the one line:

<syntaxhighlight lang="cpp">

<syntaxhighlight lang="cpp">

   reset(f6); reset(f7);

   reset(f6); reset(f7);

Substitutions for the following action commands are available:

Substitutions for the following action commands are available:

     lindirectv(v30,v32);  *v30 = v32;

     lindirectv(v30,v32);  *v30 = v32;

     rindirect(v30,v32);  v30 = *v32;

     rindirect(v30,v32);  v30 = *v32;

===Conditionals and tests===

===Conditionals and tests===

         <action commands>

         <action commands>

     }

     }

or like this :

or like this :

       <more action commands>

       <more action commands>

     }

     }

Multiple commands can be placed in a single line:

Multiple commands can be placed in a single line:

<syntaxhighlight lang="cpp">

<syntaxhighlight lang="cpp">

     if (<test commands>) { <action Commands> } else { <more action commands> }

     if (<test commands>) { <action Commands> } else { <more action commands> }

Test commands are coded like action commands except there is no semicolon. They are separated by && or || for AND or OR.

Test commands are coded like action commands except there is no semicolon. They are separated by && or || for AND or OR.

     if (isset(f5) &&

     if (isset(f5) &&

         greatern(v5,6)) { ......

         greatern(v5,6)) { ......

  Multiple tests can be placed in a single line within the if statement:

  Multiple tests can be placed in a single line within the if statement:

     if (isset(f90) && equalv(v32,v34)

     if (isset(f90) && equalv(v32,v34)

         && greatern(v34,20)) { .......

         && greatern(v34,20)) { .......

A '''!''' placed in front of a command negates its result:

A '''!''' placed in front of a command negates its result:

     if (!isset(f7)) {

     if (!isset(f7)) {

       ......

       ......

Boolean expressions are not necessarily simplified so they must follow the rules set down by the file format. If test commands are to be ORred together, they must be placed in brackets.

Boolean expressions are not necessarily simplified so they must follow the rules set down by the file format. If test commands are to be ORred together, they must be placed in brackets.

     if (isset(1) || (isset(2) && isset(3))) {    // is NOT legal

     if (isset(1) || (isset(2) && isset(3))) {    // is NOT legal

Depending on the compiler, simplification of boolean expressions may be supported, so the above may not apply in all cases (although if these are rules are followed then the logic will work with all compilers).

Depending on the compiler, simplification of boolean expressions may be supported, so the above may not apply in all cases (although if these are rules are followed then the logic will work with all compilers).

     !lessn(v30,4)        v30 >= 4

     !lessn(v30,4)        v30 >= 4

     !lessv(v30,v32)      v30 >= v32

     !lessv(v30,v32)      v30 >= v32

Also, flags can be tested for by just using the name of the flag:

Also, flags can be tested for by just using the name of the flag:

     if (v7 > 0 && !f6) { .....

     if (v7 > 0 && !f6) { .....

===Argument types===

===Argument types===

     move.obj(so4,80,120,2,f66);

     move.obj(so4,80,120,2,f66);

     if (obj.in.box(so2,30,60,120,40)) { .....

     if (obj.in.box(so2,30,60,120,40)) { .....

A complete list of the commands and their argument types is available in [[AGI/Specifications/Resources#Command_list_and_argument_typesas | Command list and argument types table]].

A complete list of the commands and their argument types is available in [[AGI/Specifications/Resources#Command_list_and_argument_typesas | Command list and argument types table]].

     if (has("Jetpack")) { .....

     if (has("Jetpack")) { .....

     if (has(io9)) { .....

     if (has(io9)) { .....

Messages can also be split over multiple lines:

Messages can also be split over multiple lines:

     print("This message is split "

     print("This message is split "

           "over multiple lines.");

           "over multiple lines.");

Quote marks must be used around messages and object names. This is important because some messages or object names may contain brackets or commas, which could confuse the compiler. This is also the case for the '''said''' command which will be described shortly.

Quote marks must be used around messages and object names. This is important because some messages or object names may contain brackets or commas, which could confuse the compiler. This is also the case for the '''said''' command which will be described shortly.

     if (has("Buckazoid(s)")) { .....        // no ambiguity here about where

     if (has("Buckazoid(s)")) { .....        // no ambiguity here about where

                                             // the argument ends

                                             // the argument ends

The '''said''' test command uses different parameters to all the other commands. Where as the others use 8 bit arguments (0--255), '''said''' takes 16 bit arguments (0--65535). Also, the number of arguments in a '''said''' command can vary. The numbers given in the arguments are the word group numbers from the '''words.tok''' file.

The '''said''' test command uses different parameters to all the other commands. Where as the others use 8 bit arguments (0--255), '''said''' takes 16 bit arguments (0--65535). Also, the number of arguments in a '''said''' command can vary. The numbers given in the arguments are the word group numbers from the '''words.tok''' file.

<syntaxhighlight lang="cpp">

<syntaxhighlight lang="cpp">

     if (said(4,80)) { .....

     if (said(4,80)) { .....

Words can also be given in place of the numbers:

Words can also be given in place of the numbers:

     if (said("look")) { .....

     if (said("look")) { .....

     if (said("open","door")) { .....

     if (said("open","door")) { .....

Quote marks must also be used around the words.

Quote marks must also be used around the words.

<syntaxhighlight lang="cpp">

<syntaxhighlight lang="cpp">

     Label1:

     Label1:

The label name can contain letters, numbers, and the characters "_" and ".". No spaces are allowed. The '''goto''' command takes one parameter, the name of a label.

The label name can contain letters, numbers, and the characters "_" and ".". No spaces are allowed. The '''goto''' command takes one parameter, the name of a label.

<syntaxhighlight lang="cpp">

<syntaxhighlight lang="cpp">

     goto(Label1);

     goto(Label1);

===Comments===

===Comments===

     [  Rest of line is ignored

     [  Rest of line is ignored

     /* Text between these are ignored */

     /* Text between these are ignored */

The /*...*/ can be nested:

The /*...*/ can be nested:

       print("Hey!");    // won't be run, still inside comments

       print("Hey!");    // won't be run, still inside comments

     */                  // uncomments

     */                  // uncomments

===Defines===

===Defines===

     #define ego o0

     #define ego o0

     #define room_descr "This is a large hall with tall pillars down each side."

     #define room_descr "This is a large hall with tall pillars down each side."

Then the define name can be used in place of the define value:

Then the define name can be used in place of the define value:

     draw(ego);

     draw(ego);

     print(room_descr);

     print(room_descr);

Define names can only be used in arguments of commands (including gotos and the v0 == 3 type syntax), although some compilers may allow you to use them anywhere.

Define names can only be used in arguments of commands (including gotos and the v0 == 3 type syntax), although some compilers may allow you to use them anywhere.

<syntaxhighlight lang="cpp">

<syntaxhighlight lang="cpp">

     #include "file.txt"

     #include "file.txt"

When the compiler encounters the above line, it will replace it with the contents of file.txt.

When the compiler encounters the above line, it will replace it with the contents of file.txt.

<syntaxhighlight lang="cpp">

<syntaxhighlight lang="cpp">

     #message 4 "You can't do that now."

     #message 4 "You can't do that now."

Then you can give the message number as the parameter in commands:

Then you can give the message number as the parameter in commands:

<syntaxhighlight lang="cpp">

<syntaxhighlight lang="cpp">

     print(m4);

     print(m4);

Or embed the message in commands as normal and the number you assigned to it before will be used:

Or embed the message in commands as normal and the number you assigned to it before will be used:

<syntaxhighlight lang="cpp">

<syntaxhighlight lang="cpp">

     print("You can't do that now.");

     print("You can't do that now.");

#message can be used anywhere in the file, so you do not have to set the message before you use it.

#message can be used anywhere in the file, so you do not have to set the message before you use it.

:If both objects n and m are on the screen, then  

:If both objects n and m are on the screen, then  

, otherwise vd = 255.

, otherwise vd = 255.

     ...

     ...

     show.pic();

     show.pic();

:Any other order may crash the interpreter without any diagnostic messages.

:Any other order may crash the interpreter without any diagnostic messages.

     set.string(s1,"test");

     set.string(s1,"test");

     unknown170(1);

     unknown170(1);

:will automatically load the savegame named "test".

:will automatically load the savegame named "test".

cycle.time(smoke, work);

cycle.time(smoke, work);

draw(smoke);

draw(smoke);

From the game:

From the game:

cycle.time(7, 152);

cycle.time(7, 152);

draw(7);

draw(7);

Opening the door

Opening the door

   }

   }

}

}

From the game:

From the game:

   }

   }

}

}

===Unlocking the door===

===Unlocking the door===

   }

   }

}

}

From the game:

From the game:

   }

   }

}

}

===Knocking on the door===

===Knocking on the door===

   }

   }

}

}

From the game:

From the game:

   }

   }

}

}

===Fall rocks===

===Fall rocks===

   }

   }

}

}

From the game:

From the game:

   }

   }

}

}