GTA: Modification Area

A website for the GTA modding scene


Display results as :

Rechercher Advanced Search

Latest topics
» {Windows 7 Activator All Versions
Fri Oct 02, 2015 2:56 am by reygyquitem

» A-pdf-restrictions-remover-1.7.0-serial.rar
Fri Sep 25, 2015 3:35 am by reygyquitem

» Teleatlas Europa Ford Nx 2011
Wed Sep 16, 2015 8:47 am by reygyquitem

» (4) World Of Computer Music .htm
Fri Aug 21, 2015 4:01 pm by reygyquitem

» Beautiful Girl With Big Bouncing Boobs 2
Mon Aug 10, 2015 11:17 am by reygyquitem

» Mario Party 2 Vc Region Free Rar
Fri Jul 03, 2015 12:12 pm by reygyquitem

» Mia Khalifa Pops A Fan's Cherry
Mon Jun 01, 2015 7:19 pm by reygyquitem

» Mia Khalifa Pops A Fan's Cherry
Mon Jun 01, 2015 7:17 pm by reygyquitem

» Big-game starts raising Schneider's profile
Sun Mar 04, 2012 2:28 am by lavivi














----- Русский -----

Если ваш сайт содержит большую коллекцию SCM/CLEO-скриптов (больше 16), напишите на мой e-mail, и я добавлю его в список. Приветствуются скрипты, которые не встречаются на других сайтах ... Спасибо. ))))

----- English -----

If your website has a big enough collection of SCM/CLEO scripts (more than 16) notify me by e-mail
, and I will add it to the list. The unique scripts are preferable ... Thank you. ))))

Log in

I forgot my password

December 2015

Calendar Calendar

You are not connected. Please login or register

Global and Local Variables

View previous topic View next topic Go down  Message [Page 1 of 1]

1 Global and Local Variables on Fri Feb 06, 2009 5:14 am

Global and Local Variables:

Local Variables:

Local Variables are denoted by a @
Their values are available only within the current thread.
Scripts and external scripts have a setback of 0@ to 33@ in San Andreas. 32@ and 33@ are denoted as local timers have should NOT be used or anything

San Andreas missions have a much bigger setback than it's threads. SA missions uses locals in range of 0@ to 1023@

Global Variables:

Global Variables are denoted by a $ sign (dollar)
Their values are available from any place of a code. You must NOT use them for different things in main.scm

In CLEO scripts Global Variables can make crashes, or bugs. The only ones which should(can) be used are:



Beware that these Globals below have the same meaning as what they are pointing too! So be careful you do not use them for anything else.


$409 -> $ONMISSION

Also if you're using these in normal main be careful that you do NOT use one which is used for something else. Check first!

CLEO 3 Rules:


1: No Globals other than the ones I spoke about above(and ones from the CustomVariables.txt).
2: Use 0A93: to end a CLEO thread not 004E: ( 0A93 =-> 0A93: end_custom_thread, 004E =-> 004E: end_thread )
3: In a mission script do not use 0A93: to end the mission, you must use 004E: like normal.
4: To compile a CLEO script as *.cs (custom script) use -> {$CLEO} or -> {$CLEO .cs}

5: To compile a CLEO mission script *.cm (custom mission) use -> {$CLEO .cm}
The starter pack of the mission you must start the mission with 0A94: (starter pack is normal thread so it should be a *.cs file)

Write the name of the *.cm you want to start *.cm is not needed as the opcode will search for the file with the extant.
Missions are not recommended for newbies.

View user profile

View previous topic View next topic Back to top  Message [Page 1 of 1]

Permissions in this forum:
You cannot reply to topics in this forum