| 02-01-2003, 09:11 PM | #1 |
It keeps disabling my conditions randomly - it seems its only the Unit-Type comparison ones, but wtf. ORIGINAL COND: (Unit type of (Triggering unit)) equal to wizard MESSED CON: Value equal to wizard <--Disabled Is this known? It seems like its just happening today, so wtf? UMSWE 3.6 |
| 02-01-2003, 09:41 PM | #2 |
its a normal WE bug, happens if you use the standard once with no enchancesments. Donno what causes it, but it has something to do with editing the unit properties. I have experienced it a few times |
| 02-01-2003, 09:56 PM | #3 |
It's not only limited to the standard WE. I have experienced this even with UMSWE. WE is supposed to keep track of things that you change, and will update triggers when you do such simple things as change the name of a trigger that you call, or even the name of a unit. But for some reason, the condition falls apart when you modify the unit properties of that unit. I have found a slight work around, and that is to close the trigger module before modifying units. I do, however, always check my triggers where a condition compares a unit type just in case. |
| 02-01-2003, 10:07 PM | #4 |
Hmm, strange - man you'd think sicne the popularity of WE that lazy bliz would support it better, they havent released one patch for it. Apparently its too flexible and bliz doesnt want to support non melee games that are very trigger oriented (read on some war3 site, its not quoted but I remember reading somethign like that) |
| 02-02-2003, 12:02 AM | #5 | |
Quote:
Why wouldn't they wanna make it more flexible? If there's a wider variety of custom games then more people will play them and more people will buy the game. Blizzard may not have as many people playing their melee maps but I'm sure they won't care as long as they getting rich, lol It's not that they don't WANT to make it more flexible, it's simply that it's more work than it's worth to them. |
| 02-02-2003, 12:11 AM | #6 |
yet, proving their lazyness. Dont quote me on what my last post said, it was from some war3 site, how they were bitching at lazyness of bliz :D |
| 02-02-2003, 12:57 AM | #7 |
mabey they dont know y it does that, i doubt there lazy mabey they didnt even know(doubt it though). wait for more patches and we see, its not the biggest deal |
| 02-02-2003, 01:11 AM | #8 |
Well, its been said before by others, but ill say it again. If it gets too much more flexible, then we could practicly make complete mods and use them on bnet. I know it seems that why so far, but its not there yet. Dont expect them to open it up to much more, cuz as we have proved on this site, they give us an inch, and we take a mile. |
| 02-02-2003, 01:15 AM | #9 |
True, but isnt the popularity of our creations go towards them? look at all the mods for half life, lots of them are very good and credit is still giving to ValvE for Half-Life, if blizzard opened it up some more we can take that mile alot longer and they still get credit for it. I bet if they started charging for bnet 90% of all players would pay, nto that I'm saying it's a good idea, but paying towards making a great game even better is well worth my money. |
| 02-02-2003, 01:16 AM | #10 |
Guest | The bug is because if you have a trigger action or condition selected, then you modify somehting in the unit editor, it will disable random values. Just select a folder in the trigger editor when you go to do somehting else. |
| 02-02-2003, 12:20 PM | #11 |
Guest | sorry but this isnt right. even when u select a folder it can happen or when triggrt module is closed and you SAVE the map. this bug cost me a year of my life |