| 01-23-2006, 07:49 PM | #2 |
In what way does it not work? What is it supposed to do? Can we see the rest of the trigger? Are you sure you don't set your variable array somewhere else? |
| 01-23-2006, 07:56 PM | #3 |
It is supposed to make a floating text with the spell name, and it doesnt. The trigger consists about 8 of these, one for each ability, the Event is A unit begins casting an ability. (Ive also tried change it to "starts a effect" The trigger is really long so I don't want to post it unless I really have to. It was much longer before I added the "For loops". Worked before I added those. ![]() bah anyway, this is the original trigger, the other one is the one I use now EDIT: The trigger is to long for the post (set for bad english but I dont have time to think ) |
| 01-23-2006, 08:02 PM | #4 |
Ok, here's a blind shot, at the end of "then-actions", put a "skip remaining actions". If that doesn't work, post the whole trigger. |
| 01-23-2006, 08:09 PM | #6 |
If that's the case, complain about it in the Site Discussion forum and demand it fixed. Or, just try to post the trigger in 2 parts... or, just try to cut out the parts that repeat themselves, but nothing else and explain exactly what kind of parts were skipped. Anyway, I need to know what the full trigger looks like (and what's it supposed to do) to be able to help you. |
| 01-23-2006, 08:11 PM | #7 | |
Yeah I posted the part that repeats, it just changes the abilities, here comes the end (still original trigger)
|
| 01-23-2006, 08:12 PM | #8 | |
You can se the current repeating trigger on the first post. here comes the end. (Sry for double post, Though It was needed this time)
|
| 01-24-2006, 04:58 PM | #9 |
*bump (seems like no one reply's on posts thats more than 1 days old) |
| 01-27-2006, 01:12 PM | #10 |
*bump again |
| 01-27-2006, 04:28 PM | #11 |
Put all the actions that come at the end in a seperate trigger, then, use the "skip remaining actions" as I suggested before, but before skipping, run that trigger; I *think* the event responses should carry over to the new trigger when run in this way, if not, then we'll think of something else. |
| 01-27-2006, 04:51 PM | #12 |
Meh, Anitarf, there's a better way (or at least an equal way that doesn't involve another trigger :P), just make a local variable and set it to true when you need to (at the end of the then set of statements), and have (localvar = false) as one of the conditions in the if statement. |
| 01-27-2006, 05:17 PM | #13 |
If you do it like that, there's no need for the variable to be local. |
| 01-27-2006, 06:19 PM | #14 |
You're right, I wondered why I said that after I did. Ah, there's always the possibility he has a wait in his trigger :D |
| 01-28-2006, 10:45 AM | #15 |
How can it work just because I skip the other if/then/else? Is it some kind of system overload that causes the problem? And if so why did it work before I added all the "For Loops"? |
