aaah syntax error!

[Ellie Oddenfen]

I'm very new to  scripting. I'm trying to make a script that will have the object become fullbright when you step on it, and then go back to normal when you're not stepping on it. So this is what I have:

default
{
    state_entry()
    {
        //do nothing...
    }

    collision_start(integer x) //when bumped
    {
        llSetPrimitiveParams([
            llSetPrimitiveParams
            ([PRIM_FULLBRIGHT,ALL_SIDES,TRUE]);
           
            }
    collision_end(integer x)
    {
       
        llSetPrimitiveParams([
            ([PRIM_FULLBRIGHT,ALL_SIDES,FALSE]);
     }
}


And when I try to save it it always says (11, 46) : ERROR : SYNTAX ERROR

What the heck is a syntax error and how do I fix it?

[Osprey Therian]

default
{
    state_entry()
    {
        //do nothing...
    }

    collision_start(integer x) //when bumped
    {
        llSetPrimitiveParams
       
            ([PRIM_FULLBRIGHT,ALL_SIDES,TRUE]);
          
            }
    collision_end(integer x)
    {
      
        llSetPrimitiveParams(
           [PRIM_FULLBRIGHT,ALL_SIDES,FALSE]);
     }
}

[Osprey Therian]

*Puts on her Scripting Dunce pointy hat*

I just took out that double '  llSetPrimitiveParams'.

I have a nerve even pretending to help anyone == but that fixed it.

[Ellie Oddenfen]

Well. I am an idiot. Thanks for helping.

[Rolig Loon]

It's easier to see the error if you don't split a statement in the middle so that it ends up on separate lines. Here's a more compact version of the corrected script that Osprey just posted.....

default{    collision_start(integer x) //when bumped    {        llSetPrimitiveParams([PRIM_FULLBRIGHT,ALL_SIDES,TRUE]);    }    collision_end(integer x)    {        llSetPrimitiveParams([PRIM_FULLBRIGHT,ALL_SIDES,FALSE]);    }}

 Notice that the state_entry event is no longer there too.  You don't really need it unless you are actually doing something when you enter the state.

In general, a syntax error means that you have mistyped something .... misspelled a word, failed to capitalize something, forgotten to put a semicolon at the end of a statement, miscounted } brackets or parens ......  Unfortunately, the message is too vague to be helpful, which is why it makes sense to do scripting in a good offline editor that has more informative error messages. 

[Acheron Gloom]

It will even give you errors that are lines ahead of where your actual fault was, for example if you leave the end off a vector or rotation.