"Scri: Trigger Error in 'gt_RaceSelection_Func': Could not get property from parameter in 'DialogControlGetPropertyAslnt' (value: 18) Near line 343 in gt_RaceSelection_Func() in MapScriptgalaxy"
And it goes in that format with other things as well.
You probably modified the parameters of an action definition without going through each used instance of that definition and making sure everything matched up. That's my best guess, anyway. SC2 was expecting a parameter value but got something invalid instead.
It's hard to tell exactly without seeing the code itself- I would guess you made some type of custom action definition, and then modified something in that action that changed or messed up the parameters. Go to your race selection function, and check over your paramaters to check that they're all the right variable types. Also check your action properties (Make sure nothing is checked you don't need; I occasionally find things checked that I didn't mean to click). Then head to whatever trigger corresponds to line 343 (the debugger should show you the exact line), and make sure the parameters plugged in to the action are correct. If that's not the issue, look for any dialog function involved and make sure it has the correct parameters and should return the correct int.
And it goes in that format with other things as well.
What does it mean?
TY in advance!
You probably modified the parameters of an action definition without going through each used instance of that definition and making sure everything matched up. That's my best guess, anyway. SC2 was expecting a parameter value but got something invalid instead.
@MoDTassadar: Go
It's hard to tell exactly without seeing the code itself- I would guess you made some type of custom action definition, and then modified something in that action that changed or messed up the parameters. Go to your race selection function, and check over your paramaters to check that they're all the right variable types. Also check your action properties (Make sure nothing is checked you don't need; I occasionally find things checked that I didn't mean to click). Then head to whatever trigger corresponds to line 343 (the debugger should show you the exact line), and make sure the parameters plugged in to the action are correct. If that's not the issue, look for any dialog function involved and make sure it has the correct parameters and should return the correct int.