It is put at the very beginning of the labels, otherwise, for an unknown reason, the script crashes. And Sanny prevents compiling if it is not there, apparently, to prevent bugs.Ī form of the wait keyword with number 0 that has a similar function in the label like the 0000: opcode has in the script. To display classes and keywords press CTRL + Space in Sanny Builder.ĭirectives are places at the beginning of the script in the braces (curly brackets -, in order for script to be able to be compiled. For example the wait keyword will pause the script for the set amount of milliseconds when the script reaches the wait keyword. Keywords can be both checks and procedures. Keywords are for example: IF, THEN, END, shake_camera, key_down, thread, set_weather, etc. Keywords are commands, set bold in Sanny Builder, they operate/function like opcodes. To display classes and keywords press CTRL + Space in Sanny Builder. Example: Actor.Driving($PLAYER_ACTOR) is a check and it will check if player is driving in the IF conditional sentence. followed by a dot (.) after which check, proc and property come. Classes start with a word such as Actor, Player, Car, File, etc. Property is something between proc and check, it is used to get something from something or set something to something. Proc stands for procedure and is used as a consequence of the condition (After THEN, ELSE). Check is used in IF conditional sentence as a condition. In the script any number can be assigned to represent true and/or to represent false.Ĭlass in the script means a category that can be used as check, proc or property. That parameter can be anything: Weapon ID, car ID, text, color, a number, etc.
Anything past the : is either just a piece of text to tell what the opcode does or a parameter that allows the operation code to do what it needs to do. Operation code that starts with 0, has 4 characters and ends with.
Knows how to write/hack any kind of memory without any snippets.Can create a script from scratch without any help.Understands all code from CLEO scripts.Knows how to write/hack memory with the help of snippets.Fully understands CLEO language and all of its dictionary.
Knows how to fully and completely create scripts with all given functions.Understands all the code within CLEO scripts.Can create a script from scratch with minor help.Fully understands CLEO language and most if its dictionary.Knows how to fully create (at least basic) scripts.Understands most of the code from CLEO scripts.Knows how to use snippets only with examples.Understands how CLEO language works and at least half of its dictionary.Knows how to write and create (basic) CLEO scripts (not necessarily fully).Understands the code from CLEO scripts generally.Doesn't fully understand how CLEO language works and its dictionary.Cannot create a script in CLEO without errors/mistakes/bugs.Doesn't understand how CLEO scripts work.