So I was curious if there are hidden repercussions to having trigger errors that I'm not aware about. I have a trigger with 2 events and a few conditions. Some conditions apply to one event firing while some to the other event. Since the events are different in nature the other conditions cause a trigger error. The trigger seems to work just fine for both event scenarios and I don't see anything different from other triggers other than the trigger error caused by the condition checks. Are there any other problems from doing this I'm not aware about? I know I could just copy and paste the trigger actions to a new trigger to get rid of the trigger error but I'd rather not if this doesn't cause any problems.
I think errors aren't displayed on Battle.net by default, but overall unless your trigger misfires because of it, it shouldn't be a problem. Test it alot though, you never know what might go wrong with a condition error.
I don't know of any repercussions. You can also disable any error displaying in the map options.
Some actions even throw trigger errors, if they are working perfectly and are not used wrong, notably when using CatalogFieldValueSet for various fields of Persistent effects. They get modified and the modifications work ingame, but you get an error message that the modification didn't work.
So I was curious if there are hidden repercussions to having trigger errors that I'm not aware about. I have a trigger with 2 events and a few conditions. Some conditions apply to one event firing while some to the other event. Since the events are different in nature the other conditions cause a trigger error. The trigger seems to work just fine for both event scenarios and I don't see anything different from other triggers other than the trigger error caused by the condition checks. Are there any other problems from doing this I'm not aware about? I know I could just copy and paste the trigger actions to a new trigger to get rid of the trigger error but I'd rather not if this doesn't cause any problems.
I think errors aren't displayed on Battle.net by default, but overall unless your trigger misfires because of it, it shouldn't be a problem. Test it alot though, you never know what might go wrong with a condition error.
I don't know of any repercussions. You can also disable any error displaying in the map options.
Some actions even throw trigger errors, if they are working perfectly and are not used wrong, notably when using CatalogFieldValueSet for various fields of Persistent effects. They get modified and the modifications work ingame, but you get an error message that the modification didn't work.
Thank you. Good to know this shouldn't cause any problems. Just looks ugly seeing an error message pop up.