There's a bug with the type checking of the Divide() operation on FLOAT3 in itemScripts (and presumably charScripts):

Code
INIT

ITEM:__Me

EVENTS

EVENT DivideBug
VARS
    FLOAT3:_Direction
ON
    OnItemEvent(__Me,"TestDivide")
ACTIONS
    GetForwardDirection(__Me,_Direction)
    Divide(_Direction,3.0)


This will result in the compiler error "FLOAT3 is written as {number;number;number}", but the second argument does in fact have to be a scalar. Multiply() is handled correctly.

On a related note: the line numbers for errors in item/charScripts are often off by several lines (the error is always shown on a higher line than where the error is occurring). I haven't discovered yet which kind of statements get skipped by the line counting.