Hey SEN, I'm pretty sure it's possible, and so I was wondering.. How do I spawn units on null terrain?
I've chosen some null tiles from the tileset index in SCMDraft 2, but the ones I've chosen so far wont let me spawn units on them.
Is there a specific tile I need to use?
Also, are there any generic reasons why a map would suddenly stop working?
I have a map that can be started up and played, except the triggers will only fire once, or not at all.
Even when the conditions are being met, some triggers wont work, and others seem to not respond to the preserve trigger action.
Is there any big glitch or reason why this would happen?
Thanks in advance..
None.
If you want to spawn units on null terrain, you need to use walkable null. It's the null tile to the right of the creep in SCMDraft2's tileset index window.
As for why your triggers stop working: are you using hyper triggers? If not, it takes the trigger cycle a couple of seconds to reset. Also, do you have Wait actions in your map? If so, be sure to configure them so as not to encounter
wait blocks, or replace them with an alternate form of timing of your choice (in most situations,
death counters are the best available timing system).
None.
Wow, that was an amazingly fast response...
And thankyou, the null thing saved me a LOT of time.
There are hypertriggers, and I've checked for wait blocks, and don't think there are any.
As for death counters, it's my brothers map and I don't think he wants to delve into that..
But thanks dude, your truly awesome.
None.
There could be any number of reasons why your triggers stop working, usually it's because the conditions aren't being met or you're experiencing wait blocks. If you can't figure it out, you can post the map and we'll tell you what's wrong.
Also, are there any generic reasons why a map would suddenly stop working?
I have a map that can be started up and played, except the triggers will only fire once, or not at all.
Even when the conditions are being met, some triggers wont work, and others seem to not respond to the preserve trigger action.
Is there any big glitch or reason why this would happen?
It sounds like it might be an issue with hyper triggers, if you are using them. If you're using the ones that have Wait(0); copied 63 times, make sure they're at the bottom of the trigger list.