| 09-27-2008, 09:27 AM | #2 |
Does that dummy Stormbolt have a mana cost AND the dummy unit have no mana? That's usually the case. |
| 09-27-2008, 09:46 AM | #3 |
ahahahahaha. oh god now i feel like such a tool. yeah that was the problem cheers +rep. |
| 09-28-2008, 03:49 AM | #4 |
| 09-28-2008, 04:30 AM | #5 |
yeah i was considering doing it that way but the only problem was that it either picks too many units or it misses some. But i guess i cant be too picky about it =/. i really wish blizzard would just let you pick units between two points, would make alot of lives easier. Back on topic, is there a way to make that trigger not leak? do i need to set a variable which selects every unit with 50 units of a given point. and then null it at the end. im a little n00b when it comes to memory leaks is there a guide that can help me how to null/delete variables? |
| 09-28-2008, 06:21 AM | #6 |
Of course there is, just check the tutorials section, like this guide. Of course there are more so check it out when you can. |
| 09-29-2008, 07:03 AM | #7 |
i used your example tide but for some reason its not quite doin what i was expecting it to. i did a leak free version of it where i made a unit group variable and then destroyed it after the trigger was finished and done with. its meant to make 50 small points along my line and having each point select units within its 50 radius. my only problem is that sometimes it will damage those in the line but sometimes it wont. its really unpredictable. do you think you could check what's wrong with my trigger? |
