Report, edit, etc...Posted by White-Fire on 2004-12-08 at 17:49:51
how od i get units to appear at a spot on the map.. this is for my insane comp map.. like say 10 zerg units to appear in the zerg base at say 5 mins ..
idk how to do that O.o
idk how to do that O.o
Report, edit, etc...Posted by ChaosRyder on 2004-12-08 at 17:57:41
This is how you do it:
#1 Create a location where you units will apear. Mine will be *Zerglines Apear*
#2 Create this trigger:
and that should be all.... Oh and play the map!
#1 Create a location where you units will apear. Mine will be *Zerglines Apear*
#2 Create this trigger:
| Trigger |
| Players: |
| ¤ The player for which to units are going to apear |
| Conditions: |
| ¤ Current player accumulated at least 5 mineral. |
| Actions: |
| ¤ Substract 5 mineral for current player. |
| ¤ Create x zerglines at Zerglines Apear for current player. |
| ¤ Preserve Trigger |
and that should be all.... Oh and play the map!
Report, edit, etc...Posted by Screwed on 2004-12-08 at 17:57:55
You set the condition,
Then if you want them to spawn every 5 minutes, do this.
Wait 300000 milliseconds.
Create 10 Zerg _____ at location for player X.
Preserve Trigger.
I didn't go into Death counters to replace waits since i assume those are not suitable for your level yet.
Edit:
Meh.. i posted at the same time ChoasRyder did - some info are repetitive.
Re-Edit: Since my post is too similar to the one above, I'll just go into death counter to replace waits.
Firstly, make Hyper Triggers like this:
Starcraft checks triggers every 2 seconds or at intervals which there are waits. Therefore first add a trigger like this for a player without any waits.
-Always
~Wait 0 milliseconds.
~Wait 0 milliseconds.
~Wait 0 milliseconds.
~Wait 0 milliseconds.
~Wait 0 milliseconds.
... and so on until you reach 63, then add Preserve Trigger.
Then copy the trigger 3 times.
By doing this, starcraft will check trigger 12.2 times a minute.
Why use death counters?
Waits in your triggers causes a blockage for other triggers to fire. They stack up and some triggers don't run until the wait has finished. Therefore to infiltrate this from happening, we use death counters.
Death Counters are just a method of calculating time using the nature of Starcraft's triggering checking speed and then setting something to happen, you can set/add/subtract deaths directly using the trigger SetDeaths. Then what you do is, you make a trigger like this.
-Always
~Add 1 deaths for Independent Starport (or any unit that don't exist in the game) for Player X.
~Preserve Trigger.
This causes starcraft to continously add deaths to 'Independent Starport' owned by Player X. However, it will not automatically go to infinite, instead as I have mentioned before... with Hyper triggers, Starcraft check triggers 12.2 times a second. So it adds around 12 deaths per second. Using this method - you are able to estimate how many deaths will be added in 3 minutes. (3x60x12.2 = You can work it out yourself
)
After it have obtained that amount of deaths, run an action that creates 10 zerglings at the location.
(After reading ChaosRyder's post, assuming you are not creating units reptitively, I don't think i need to mention how to cycle the death counter)
Then if you want them to spawn every 5 minutes, do this.
Wait 300000 milliseconds.
Create 10 Zerg _____ at location for player X.
Preserve Trigger.
I didn't go into Death counters to replace waits since i assume those are not suitable for your level yet.
Edit:
Meh.. i posted at the same time ChoasRyder did - some info are repetitive.Re-Edit: Since my post is too similar to the one above, I'll just go into death counter to replace waits.
Firstly, make Hyper Triggers like this:
Starcraft checks triggers every 2 seconds or at intervals which there are waits. Therefore first add a trigger like this for a player without any waits.
-Always
~Wait 0 milliseconds.
~Wait 0 milliseconds.
~Wait 0 milliseconds.
~Wait 0 milliseconds.
~Wait 0 milliseconds.
... and so on until you reach 63, then add Preserve Trigger.
Then copy the trigger 3 times.
By doing this, starcraft will check trigger 12.2 times a minute.
Why use death counters?
Waits in your triggers causes a blockage for other triggers to fire. They stack up and some triggers don't run until the wait has finished. Therefore to infiltrate this from happening, we use death counters.
Death Counters are just a method of calculating time using the nature of Starcraft's triggering checking speed and then setting something to happen, you can set/add/subtract deaths directly using the trigger SetDeaths. Then what you do is, you make a trigger like this.
-Always
~Add 1 deaths for Independent Starport (or any unit that don't exist in the game) for Player X.
~Preserve Trigger.
This causes starcraft to continously add deaths to 'Independent Starport' owned by Player X. However, it will not automatically go to infinite, instead as I have mentioned before... with Hyper triggers, Starcraft check triggers 12.2 times a second. So it adds around 12 deaths per second. Using this method - you are able to estimate how many deaths will be added in 3 minutes. (3x60x12.2 = You can work it out yourself
)After it have obtained that amount of deaths, run an action that creates 10 zerglings at the location.
(After reading ChaosRyder's post, assuming you are not creating units reptitively, I don't think i need to mention how to cycle the death counter)
Report, edit, etc...Posted by ChaosRyder on 2004-12-08 at 18:00:16
Yeah... lol. Both of our thecniques are good thought! Hope we answered the question you wanted, and hope it isn't too complicated for you...
Report, edit, etc...Posted by NeoNightmareX on 2004-12-08 at 19:59:10
hes a beginner, not a retard 
, but i'd say use screwed's method with the wait an elapsed time, it is much easier, and i believe that it is a better method, but that is my opinion
, but i'd say use screwed's method with the wait an elapsed time, it is much easier, and i believe that it is a better method, but that is my opinionReport, edit, etc...Posted by LegacyWeapon on 2004-12-08 at 20:04:14
You can also use a countdown timer.
or death counts.
Why don't you play around with Starcraft Campaign Editor (The original Staredit that came with Starcraft) and test out triggers. This will give you a chance to figure out everything. I remember when I just started, I made a Protect the Temple map, and other lame maps. I was quite proud of my work though. I made many maps stupid little maps before getting my hands dirty on those hard things, like bounds and defense games. (Yes bounds are hard to make when you don't know how to make a create + kill trigger. Especially when you're 10 and only done mapmaking for 2 months
)
or death counts.
Why don't you play around with Starcraft Campaign Editor (The original Staredit that came with Starcraft) and test out triggers. This will give you a chance to figure out everything. I remember when I just started, I made a Protect the Temple map, and other lame maps. I was quite proud of my work though. I made many maps stupid little maps before getting my hands dirty on those hard things, like bounds and defense games. (Yes bounds are hard to make when you don't know how to make a create + kill trigger. Especially when you're 10 and only done mapmaking for 2 months
)Report, edit, etc...Posted by SaLaCiouS(U) on 2004-12-08 at 22:15:45
Create units. It's an action. You couldn't have missed it. If you are unable to read the language that StarEdit came with, you may not be able to make maps. Otherwise, please reach an age of 4 before posting again. If you have Autism, do not attempt to come into contact with other people.