i have been trying to work out Requirements for 3 days in a row now pulling my hair out, only to find it wasn't working cos it was in the build abilitie
I spent a good week making a map based around direct fire weapons and using all sorts of complicated angle formulas and functions to build wall deflectors etc only to realize that the angle to direction values I'd been basing it on were off by 90 degrees so I had to rebuild it all :P
I spent an evening trying to make my cinematic work only to realize that 'comments' don't actually do anything and that I simply need to use the other type of 'transmission' to be able to send a normal transmission.
It took me weeks to learn how to let an ability target either a unit or point. My sniper attack was shooting the ground for a long time till I finally figured that out...lol
Rollback Post to RevisionRollBack
Feel free to Send me a PM if you have any questions/concerns!
lol i remembered seeing blizzard comment before each line of their transmission in the campaign.
Yes! Exactly! That's what confused me! The comment information said something about it being used in campaign transmissions - blizzard maps have the text of the transmission listed nowhere but in the comments in their triggers. Hence I came to the conclusion that while comments normally do nothing, they provide the text for a transmission placed above it. I thought it through pretty well, it's just because their stuff is so damn confusing that I was so far off >.>
Just had one of those moments...I've spent the last two days of spare time trying to figure out why my map's triggers keep generating errors. Since I use threads I've been assuming it was a problem with one of their subjects dying prematurely and they being unable to cope with the change of reference so I'd been focusing on thread locks and all kinds of strategies...but I just found the real problem. Turns out some sub function I'd made a few days ago but only started making use of in the main core had some really glaringly obvious problems: There were still some references to the ol default 'triggering unit' where the sub function's parameter's unit should be among its various actions...damnit...well there's like 9 hours I"ll never get back :P
A very special no thanks to the debugging window's utter uselessness when it comes to nested actions/functions....I hate that window so much. If it could actually refer to the sub-function that a problem occurred in rather then just the parent/grand parent or even better the whole chain leading to it like any real debugger this would have been discovered and fixed within 30 seconds...@#$()*&$%(*&.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
i have been trying to work out Requirements for 3 days in a row now pulling my hair out, only to find it wasn't working cos it was in the build abilitie
any of you had some think like this =D
I spent a good week making a map based around direct fire weapons and using all sorts of complicated angle formulas and functions to build wall deflectors etc only to realize that the angle to direction values I'd been basing it on were off by 90 degrees so I had to rebuild it all :P
@BumpInTheNight: Go
omg that suxs bump =S
I spent an evening trying to make my cinematic work only to realize that 'comments' don't actually do anything and that I simply need to use the other type of 'transmission' to be able to send a normal transmission.
@Mozared: Go
lol i remembered seeing blizzard comment before each line of their transmission in the campaign.
It took me weeks to learn how to let an ability target either a unit or point. My sniper attack was shooting the ground for a long time till I finally figured that out...lol
Yes! Exactly! That's what confused me! The comment information said something about it being used in campaign transmissions - blizzard maps have the text of the transmission listed nowhere but in the comments in their triggers. Hence I came to the conclusion that while comments normally do nothing, they provide the text for a transmission placed above it. I thought it through pretty well, it's just because their stuff is so damn confusing that I was so far off >.>
@Mozared: Go
I opened Data Editor....
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Just had one of those moments...I've spent the last two days of spare time trying to figure out why my map's triggers keep generating errors. Since I use threads I've been assuming it was a problem with one of their subjects dying prematurely and they being unable to cope with the change of reference so I'd been focusing on thread locks and all kinds of strategies...but I just found the real problem. Turns out some sub function I'd made a few days ago but only started making use of in the main core had some really glaringly obvious problems: There were still some references to the ol default 'triggering unit' where the sub function's parameter's unit should be among its various actions...damnit...well there's like 9 hours I"ll never get back :P
A very special no thanks to the debugging window's utter uselessness when it comes to nested actions/functions....I hate that window so much. If it could actually refer to the sub-function that a problem occurred in rather then just the parent/grand parent or even better the whole chain leading to it like any real debugger this would have been discovered and fixed within 30 seconds...@#$()*&$%(*&.