Announcement

**mapfi** · October 7, 2002, 13:25

1.Local variables
It's clear to every programmer that a global variable is available to all parts of the code and always retains it's value. Local variable are only available in the code bit they are declared within. In SLIC such a local variable in a eventhandler will keep its value though. This means that next time the code fires up, the value is still there. So always make sure you reset it if your code doesn't overwrite it in the beginning for sure!

Discovered here: http://apolyton.net/forums/showthrea...threadid=59742

**mapfi** · October 7, 2002, 13:27

2.Calculations
Since SLIC only knows integers one has to be careful with division that will return a double. The available guides will tell you that no rounding takes place but digits are simply cut off. So 5/2 will give you 2, so will 4*7/10. Now when you work with variables a SLIC oddity will finish the last one off. Lets say a=4 and b=10, you'd assume that a*7/b will give you 2 as well. It doesn't! SLIC calculates variable first so you get a/b=0.4 which is 0, and then 0*7, still 0! So make sure you write (a*7)/b, which will return 2.

Discovered here: http://apolyton.net/forums/showthrea...0&pagenumber=3

**mapfi** · October 7, 2002, 13:28

3.Random numbers
While I wonder of what kind and what the period of SLIC's random number generator is (I might spend time on finding out someday) there's a something simple that is easily misunderstood because it defies logic: random(x); returns an integer starting at/with 0 and ending at/with x-1!
(You're not alone on this if you have believed otherwise for years...)

Discovered here: http://apolyton.net/forums/showthrea...0&pagenumber=3

**mapfi** · October 7, 2002, 13:28

4.built-in player[] array
Players and integers are more or less the same with the important difference that the built-in player variable allows you to access strings like player[0].civ_name_singular, very useful for messages. Known events use player[0] and player[1], some hidden events or unfinished diplomacy stuff might use player[2] so anything else is save. The array has unlimited size.
Now if you want to use this for a message the following restriction applies:
Immeadetly after assigning player[3] a value you have to send the message. Any additional line of code will render the value inaccessable. So unfortunately you can't have a message using two of those player[] array values. The moment you assign the second one the first one is lost, no matter that you're using a different index.
Unless in the following situation: The event uses player[0]. In that case you can first assign the index 0 and then the a different one and both will be available for the following message.

Discovered here: http://apolyton.net/forums/showthrea...threadid=63901

**mapfi** · October 11, 2002, 18:43

5a.AlertBox
An AlertBox effectively halts the game until a user input (klicking a button) - that's what the documentation says.
However, even though the human player receives the message more or less immedeately, the game unfortunately doesn't stop till the beginning of his turn.

5b.Messages
To have messages appearing on the screen you need the line show() in your code. However sometimes this still doesn't work. The frustarting thing in this case is that you usually miss what change in the code caused the fault or fixed it.
IW suggested it to be the case that this happens when two messages fire at the same time (read here: http://apolyton.net/forums/showthrea...threadid=63142). I hope this is the only case. Thanks IW.
Another cause can be what Pedrunn describes in the following post, I've experienced the same but just couldn't pin it down.

**Pedrunn** · October 13, 2002, 07:01

6. Showing Numbers in messages

If you want to have a number from a variable showing up in the messages. As usual you write the variable between {} in the message field. But you must be aware that this variable has to be a global variable otherwise the message although it will be in the message tab it not only wont show up but it wont open when you click on it in the message tab.

This is from my experience. Dont know any thread about it.

**ahenobarb** · October 14, 2002, 15:04

6b. Message Duration Command

SLIC documentation says:

VOID Duration(turns)
Kill this message automatically in n turns.

However, this command does not work. Duration should say how long a message remains in the message box before it can be deleted. however, it does not do this at all, the message stays turn after turn unless you left click it.

**mapfi** · October 18, 2002, 07:06

7. Functions, accessing variable members
In some cases, using members of unit, army, city, and location variables that are function parameters may not always work as expected. There is, however, a workaround. Copy the function parameter to a local variable and use that variable instead. Example:

Code:

// This version may fail sometimes!
int_f DoesAHumanOwnThisUnit(unit_t theUnit) {
    if(IsHumanPlayer(theUnit.owner)) {
        return 1;
    }
    return 0;
}

// This version should always work
int_f DoesAHumanOwnThisUnit(unit_t theUnit) {
unit_t copiedUnit;
    copiedUnit = theUnit;
    if(IsHumanPlayer(copiedUnit.owner)) {
        return 1;
    }
    return 0;
}

Ok, this has been known from start but it's easily forgotten

Apolyton Civilization Site

http://apolyton.net/ctp2/modification/activision/slic.shtml

**Locutus** · November 16, 2002, 19:56

Not really an oddity but something that probably few people know about or will find out on their own, so I decided to just add it here:

If you want to start a on new line in a text message (i.e. you would like to hit 'Enter'), use '\n'. The next sign will be placed on a new line. Tab is also available: \t.

Announcement

SLIC oddities

SLIC oddities

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment