Staredit Network

I think you do need to constantly enable the buildings, At least to the gateway.
Without the pylon, it will automatically revert back to disabled.

sckor, you're not understanding the problem. We're not even trying to enable the gateways!

I'll say it again: Protoss buildings will stay enabled until you create, build, move, give, or lose another building that uses or creates power. The bank triggers were interfering with the cannon triggers because in order to iterate over the banks they were giving the banks to another player.

oh, i wasnt sure about that heimdal, i thought it was just the give trigger in general :/ thanks for clearing that up

Not the top left, The Left Most unit would be the one effected. If there happens to be more than one unit that are the furthest to the left the LOWER one is selected.

No, it goes by unit order. Depending how you placed 2 buildings with the same X position, it will select either the top one or bottom one based on the order you placed them in.

Bolt was basically saying it works off right to left , bottom to top.

But it doesn't go bottom to top.

It doesn't really matter. The point was that the doodad state action only chooses one unit in the area, so you need to iterate over all of them once the state of a building has been changed.

Here is the fixed map with everything you wanted. I made most of the triggers with Starforge so you should either import the sprites from the other version into this one or just keep using Starforge. All of the triggers are activated by "current player" and I'm using players 11 and 12 to maintain the visited state of the banks and turrets. Therefore you could make this map 4v4 without any additional triggers.

Locations: 5
Triggers: 13

[attachmentid=7395]

I was using Gateways as an example.
I'll test that map.

NVM, Sorry Heimdal.
You only need to enable it once...

Here is the order.

Disproval.scx doesn't think so.
[attachmentid=7419]

Bolt is saying, if there are multiple units tied for farthest left, then it will go from bottom to top.

And DK just posted a map where that doesn't happen.

I think it depends on the action and the type of unit.

For all units, the actions "move location", "remove unit at location", "kill unit at location" and "set doodad state" apply to the leftmost units.

For a grid system using dropships, a location will move to the bottom left of a rectangle of dropships. But the first unit to be removed will be the top left one.
For a grid system using mutalisks, a location will center on the top left one in a rectangle, and the first to be removed is also the top left one. But the second to be removed is the bottom left one - so there doesn't seem to be a rigorous pattern.
So it may change according to the action and the unit.
But in all cases, the leftmost unit is affected first.

Addendum:
Gj DK! that was a cool demonstration.

No, it has nothing to do with unit types or action. It just has to do with when the units were created or placed, that determines which it will pick. In the map, all the pylons are placed on the same X position, I just placed them in a different order, not just starting from the top going to the bottom.

Then why does a dropship grid center location on the bottom one, but remove the top one?

So is there a way of giving someone the freedom to put the cannon wherever they want and still crystalize it?

Excuse me ? AcidYoshi ??



Because the top one moved left? The bottom one moved right? May I ask why you're using an unreliable system?

DK, I'm questioning your statement earlier by giving a counterexample:
The last time i tried it, I made the trigger:

- Create 6 dropship for player1
- Remove 1 dropship for player1

And the top one was removed. But this trigger:

- Create 6 dropship for player1
- Center "location" on dropship "anywhere" owned by player1

Centers the location on the bottom one.

That doesn't seem consistent with what you've said.

It's completely consistant with what I've said. They are created "differently". Depending which way the dropship is facing alters its X position. If you packed those triggers into one, it should do the stuff on the same dropship. You could use the same action and it would affect a different dropship. I thought you meant they were in the same trigger so I was wondering how it would do that.

I wouldn't use air units to test this theory - they drift.

Those were only part of the triggers that I actually used - the triggers in full were more like this (I was experimenting with a mobile grid system):

- Create 6 Dropship at "location1" for player1
- Center location on dropship owned by player1 at "anywhere"
- Kill all dropship for player1
- Center view for player 1 at "location1"
- Preserve

That trigger moved the screen down constantly, so the location must have been centering on the bottom one.
As opposed to:

- Create 6 Dropship at "location1" for player1
- Remove 1 dropship owned by player1 at "anywhere"
- Center location on dropship owned by player1 at "anywhere"
- Kill all dropship for player1
- Center view for player 1 at "location1"
- Preserve

Which also moved the screen down constantly, even though you wouldn't expect it to, because this trigger removes a dropship first. By looking at the explosion pattern, I deduced that the top one, not the bottom one, was being removed.

That's really strange, because the first trigger demonstrates that the location is centered on the bottom one, but the second trigger demonstrates that the first to be removed is not the bottom one but the top one.

Also notice that this is a consistent pattern, so is unlikely to be the effect of the random facing of the dropships, and that the dropships are killed immediately, so there is no "drift" occurring.

btw heimdal, the map you posted was still glitched..

It wouldnt work when there was more than 1 player.

I fixed it... using deathcounters

P.S. (why were we talking about dropships...?)

thats just the unit they decided to use for proving their theorys.

Well these six dropships end up doing the same thing with both actions.
[attachmentid=7673]