Well, good and bad news so far. The good news, it still happens where I first saw it. The bad news, I haven't been able to replicate it outside of that scenario. I think it only happens in a trigger that has several Task Object effects, but so far, all tests have proven negative.
I'll try to explain the process again, and if someone thinks they understand it, feel free to test it out for yourself; something like this would benifit us all.
As best I can remember, I was setting a trigger to keep some siege weapons from wandering off, so I set a trigger, set Effect0 for one weapon to not move, and moved on to the next and did the same. It was with the 3rd effect where it happened.
You know how when you open a new effect, and you get that pull-down menu with the effects. Well, I opened that and selected Task Object, and the menu closed, but there were no options for setting the effect; i.e. only the sub-menu with Task Object highlighted was present. I did it again, same thing happened. So I clicked on the previous effect in the trigger. In doing that I hoped to free up the 'nonresponsive' effect. When I went back to it, here it was set with the settings for the effect I had clicked on. I tried it again, and it worked again. I still don't know how this happened.
ax_man1
Owner of a post 500, 1000, 1500, 2000, and 2500
Not all are in the same thread, but 4 of them are