[HeresOtis]

Say if this is my .ini file:

CODE

[Vehicle] Infernus Sultan Oceanic Admiral

How do I store each of those vehicles in a string and then check if the player is driving one of those vehicles?

[Bad.boy!]

You'd better use id numbers instead, because the game doesn't recognise "Infernus" or any other car as something.
About reading from ini, no idea.

[fastman92]

@Bad.boy why not?
Just use the getModelIndexByName
http://gtag.gtagaming.com/forums/index.php...3572&#entry3572
Its little complex especially for beginers.

[Deji]

QUOTE (HeresOtis @ Friday, Apr 20 2012, 21:33)

Say if this is my .ini file: CODE [Vehicle] Infernus Sultan Oceanic Admiral How do I store each of those vehicles in a string and then check if the player is driving one of those vehicles?

It depends how you code it. CLEO 4's ink opcodes work via the following formats:

CODE

[section] valueName=value

[HeresOtis]

I just decided to use integers (the vehicle's ID). It works for me.

CODE

:isPlayerDrivingAppropriateVehicle // if //    0AB1: call_scm_func @isPlayerDrivingAppropriateVehicle 0 // then if    0AAB:  file_exists "CLEO\PoliceDB.ini" then    0AF0: 1@ = get_int_from_ini_file PoliceDB section "Vehicles" key "1"    0AF0: 2@ = get_int_from_ini_file PoliceDB section "Vehicles" key "2"    0AF0: 3@ = get_int_from_ini_file PoliceDB section "Vehicles" key "3"    0AF0: 4@ = get_int_from_ini_file PoliceDB section "Vehicles" key "4"    0AF0: 5@ = get_int_from_ini_file PoliceDB section "Vehicles" key "5"    if or        Actor.DrivingVehicleType($PLAYER_ACTOR, 1@)        Actor.DrivingVehicleType($PLAYER_ACTOR, 2@)        Actor.DrivingVehicleType($PLAYER_ACTOR, 3@)        Actor.DrivingVehicleType($PLAYER_ACTOR, 4@)        Actor.DrivingVehicleType($PLAYER_ACTOR, 5@)    then        0485: return_true    else        jump @DrivingPolice    end else    :DrivingPolice    if        Actor.DrivingPoliceVehicle($PLAYER_ACTOR)    then        0485: return_true    else            059A: return_false    end end 0AB2: ret 0

[Link2012]

I recommend you to check if player is in police vehicle, first, not later.
One condition will take less time than five conditions + ini reader.

[Deji]

And to optimise even further...

CODE

:isPlayerDrivingAppropriateVehicle // if //    0AB1: call_scm_func @isPlayerDrivingAppropriateVehicle 0 // then if    Actor.DrivingPoliceVehicle($PLAYER_ACTOR) then else    if       0AAB:   file_exists "CLEO\PoliceDB.ini"    then        0AF0: 1@ = get_int_from_ini_file PoliceDB section "Vehicles" key "1"        0AF0: 2@ = get_int_from_ini_file PoliceDB section "Vehicles" key "2"        0AF0: 3@ = get_int_from_ini_file PoliceDB section "Vehicles" key "3"        0AF0: 4@ = get_int_from_ini_file PoliceDB section "Vehicles" key "4"        0AF0: 5@ = get_int_from_ini_file PoliceDB section "Vehicles" key "5"        if or            Actor.DrivingVehicleType($PLAYER_ACTOR, 1@)            Actor.DrivingVehicleType($PLAYER_ACTOR, 2@)            Actor.DrivingVehicleType($PLAYER_ACTOR, 3@)            Actor.DrivingVehicleType($PLAYER_ACTOR, 4@)            Actor.DrivingVehicleType($PLAYER_ACTOR, 5@)        then        end    end end 0AB2: ret 0

0485 and 059A don't do anything but return true and false respectively. They may have been commands which used to actually perform a proper check, but were removed at some point and replaced to just return a default value. So while the name is valid, it can be misleading. A good way to show this:

CODE

// this statement is false if and    0485:   return_true    059A:   return_false then end // this statement is true if or    0485:   return_true    859A:   not return_false then end

So they're just conditional commands which we use to forcefully set the condition result to make SCM Functions act like they can be used as conditions as a coding trick. Any other conditional command will also work, hence the reason the optimised code above works just as well.

It could be optimised more by using low-constructs (and thus, not having an empty "then" block). There's always a point, though, where a tiny bit of optimisation isn't worth making the code less neat.

This post has been edited by Deji on Saturday, Apr 21 2012, 02:54

[HeresOtis]

How can I use

CODE

0AF4: 0@v = read_string_from_ini_file "cleo\config.ini" section "SectionName" key "stringKey"

to get the next "stringKey" in the same SectionName?

And what's difference between 0@v and 0@s?

This post has been edited by HeresOtis on Saturday, Apr 21 2012, 03:47

[SilentPL]

0@v can handle up to 15 characters, and occupies 4 vars (in this case 0@, 1@, 2@ and 3@ are used). 0@s handles up to 7 chars and uses 2 variables (in this case, 0@ and 1@).

I think you can't make multiple keys with the same name in the same section though. At least, this opcode doesn't support that (manual file reading would handle it though).

[Wesser]

To be more accurate, SCM string variables are respectively 8-byte and 16-byte long. They're usually one character less because of the null-terminator, which gives to the string a proper end as the next variable (or bytes) may be not null and so the string can be longer.

[HeresOtis]

Can I use the opcode above to read a random key in the .ini?

[HeresOtis]

What's the difference:

CODE

06D2: 5@v = "John Stockton" // @v = string   <--- This one uses "" 06D2: 5@v = 'John Stockton' // @v = string //  <--- This one uses '' 0AD0: show_formatted_text_lowpriority "Name: %s" time 2000 5@v

And if I use 5@v, can I use 6@ or 7@ to store the handle of a car or whatever I want to use those variables for?

[Link2012]

QUOTE

What's the difference: CODE 06D2: 5@v = "John Stockton" // @v = string   <--- This one uses "" 06D2: 5@v = 'John Stockton' // @v = string //  <--- This one uses '' 0AD0: show_formatted_text_lowpriority "Name: %s" time 2000 5@v

The basic difference between " and ' is:
" can hold up to 128 chars, ' can hold up to 16 chars in San Andreas, and 8 chars in III/VC.
" only exists in SA

QUOTE

And if I use 5@v, can I use 6@ or 7@ to store the handle of a car or whatever I want to use those variables for?

If you do this, you will lose the string.