The problem is this: Everytime i try to change lighting with triggers ( Aaction: Set lighting to "Agria sunset", for example), i get this message (Translated from italian) : "Script compilation failed: List of parameters unvalid" and on the trigger editor i find this misterious thing that i have no idea of what it is supposed to mean
The error shown is on some campaign or default library function call. It has nothing to do with lighting as far as I can tell. The error sounds like it is the result of argument type or number mismatch with the function declaration.
You might want to supply the map for further investigation.
I was trying do to this (thanks to AcidDragoon for this tutorial on light edit) http://i.imgur.com/JMyWZhE.jpg . I did this before 3.0, and it alwais worked, i don't know why, maybe is our SC1 Remake mod that is bugged (is an enhanced verion of the mass recall one, even if after all these years is now much different)
I have not permission to post the mod here, the problem is with mod btw, it happens to every map, i will send some PMs if you are willing to help us with this bug, thanks in advance
The problem was caused by presets in dependant mods. The function was being passed them as integer instead of the preset type in GUI. The resulting galaxy seemed to lack the presets (possibly as an optimization? If they are not used as a preset then do not build them) so when the syntax checker tried to parse that function call it was invalid. This applied to 2 presets in a dependant mod.
The solution was to change the function parameter type from integer to the appropriate preset. After this all maps seemed to compile fine without needing to change any other triggers.
EDIT:
The problem with presets seems to be that the game will not inline them if they are declared in a mod/library. If the preset is set to inline this will break because the constant variable name generated will not exist. The solution seems to be using preset type instead of integer and making sure the preset uses constants (a flag you can set) instead of inlining.
The problem is this: Everytime i try to change lighting with triggers ( Aaction: Set lighting to "Agria sunset", for example), i get this message (Translated from italian) : "Script compilation failed: List of parameters unvalid" and on the trigger editor i find this misterious thing that i have no idea of what it is supposed to mean
Mind post the trigger that it's in? I just tried doing it in my editor and it worked. That doesn't look like a lighting action either?
Still alive and kicking, just busy.
My guide to the trigger editor (still a work in progress)
The error shown is on some campaign or default library function call. It has nothing to do with lighting as far as I can tell. The error sounds like it is the result of argument type or number mismatch with the function declaration.
You might want to supply the map for further investigation.
I was trying do to this (thanks to AcidDragoon for this tutorial on light edit) http://i.imgur.com/JMyWZhE.jpg . I did this before 3.0, and it alwais worked, i don't know why, maybe is our SC1 Remake mod that is bugged (is an enhanced verion of the mass recall one, even if after all these years is now much different)
The error shown points at a campaign initialization call which would be unrelated to lighting.
You will need to provide the map (and any required mods if not public) for people to diagnose the exact cause.
I have not permission to post the mod here, the problem is with mod btw, it happens to every map, i will send some PMs if you are willing to help us with this bug, thanks in advance
The problem was caused by presets in dependant mods. The function was being passed them as integer instead of the preset type in GUI. The resulting galaxy seemed to lack the presets (possibly as an optimization? If they are not used as a preset then do not build them) so when the syntax checker tried to parse that function call it was invalid. This applied to 2 presets in a dependant mod.
The solution was to change the function parameter type from integer to the appropriate preset. After this all maps seemed to compile fine without needing to change any other triggers.
EDIT: The problem with presets seems to be that the game will not inline them if they are declared in a mod/library. If the preset is set to inline this will break because the constant variable name generated will not exist. The solution seems to be using preset type instead of integer and making sure the preset uses constants (a flag you can set) instead of inlining.