Staredit Network

I'm not talking about two seperate triggers. Example:

CONDITIONS:
Always

ACTIONS:
Create 1 Marine at Location X
Create 1 Marine at Location Y

There IS a wait between the marine being created at location X and the marine being created at Location Y. I was playing with grids and you can see it becuase on the right hallucination death the cursor switches from red to green.

You mean wait between actions?
But what about non-graphic actions?
Like adding death counts...

I am willing to bet that there are waits between non-graphic actions too. But, you really can't test this easily. Can anyone (Dk aren't you good at stuff like this?) think of a way to test this?

rexy, this is a bit off topic but how do you change the thread name because it sais thanks to lw for spelling and he asid it after you made the thread. if you cant then i feel stupid .

ontopc- is there a way to detect how much the wait is?

Just edit your first post =P.

And thats half the reason I made this thread, for any ideas how to detect that extremly small wait. Any ideas?

You could have it constantly create a unit and then add to a deathcount or a score, then have it going for a few frames or something, then subtract the amount that would be caused by the amount of time for the frame? I doubt it will work, but it's worth a shot. I think there isn't mush of a wait at all, it is just StarCraft stoppin itself from getting confused by placing 2 units in the same place at the same time or something.

Actually I think it's only doing that becuase that's one location. That one location is hopping all over the place in that map. So I guess that's why =P.

I don't think the wait can be detected through any means thus far because in order for our second trigger to "count" the time, our first trigger is already done running. SC Engine can only run 1 trigger action at a time so it has to go down the list 1 at a time at an extraordinarily fast speed.
I don't see how this tiny wait truely affects map making...

You can't detect it because there is no space between them. You can't have another trigger running internally of a trigger.

Ever time in a trigger when it fires it will start the very top action and go down from the list till its max or end, I belive it is about a 100 millisecond for each action to fire. Now since thats a very fast time we don't notice it unless you stare at it n clock it!

Hey Rexy I was working on my goldeneye map, and when doing revives I tested a new way to make random revives. I had a player constantly going from 1-10 minerals, and with no waits, and it NEVER landed on anything other than one, so I figure that there is no wait time, and if there is it isn't significant enough to have other things occur during the time.

Moose, you can have other triggers be affected by things going on in another trigger. An example would be if you said
Condition : always
Action : Create a zergling at location one for player 1
Action : Wait 1000 milliseconds
Action : Remove all zergling at location one
Action : Preserve trigger

then you had another trigger saying

Condition : Player 1 brings one zergling to location one
Action : End scenario in defeat for current player

The game would end in defeat, due to the wait, even though later in the trigger the unit is removed. So what they mean is, when you don't add a wait, is there a significant wait between actions anyways? I say depends on the action.

Rexy, there ARE no waits between actions. It is simply the order they are executed in. It is completely IMPOSSIBLE to get two actions to occur at the exact same time. They are read in a linear format. One right after the other, and there is no noticable wait.

What he said...
I would have said the same thing, just maybe not as complex as that.
Example:

"Duh! Dont you read english? Left to right, top to bottom, no space in between"
*ub3rn3wb looks like a total by saying that

So that's why hyper triggers work sorta?

I actually don't know why hyper triggers work. :/
It just works.

Uh, I have a question that relates to this, when you have a wait in a trigger, what exactly happens? Doesn't it go through all the other triggers or something like that?

Or you could...
Conditions-
Always
Actions-
Create 1 marine at location A
Create 1 marine at location B
Create 1 marine at location C
Create 1 marine at location D
Create 1 marine at location E
Create 1 marine at location F
and so on untill its long enough, and if there is time in between the first and last one than there is a wait in between actions

thats pretty long. I dont think it is that long.
They run in order, I cannot imagine how you could use the time inbetween anyway.

yea i totaly agree, it wouldnt take that long

That won't accomplish anything. You'll see them all suddenly appear.

How hypers and wait blocks work:
When a wait executes, it checks the conditions of all the other triggers to see if any of them are fulfilled. If they are, it will execute that trigger before finishing the first trigger with the wait in it. Hyper triggers are just massive amounts of wait triggers running within each other. Wait blocks occur because they have to check the other triggers and run the other waits before finishing their first one.

[center]Sory, Rexy, but there is no wait between actions. Try putting hyper triggers on the same player that does a Create1, create1, wait, preserve. Only the wait will be affected, and there will be no wait between the first Create1, and the second.[/center]

Yes, I realize that now. It was the fact that it was one location doing all those movements that makes it seem as if there was a wait.