To further specify: locations that havn't been placed or those that have been deleted are at coordinates (0,0),(0,0). Placing the location just sets the coordinates.

If you just stop using them, that could cause problems depending on how the location is being used.


By deleted, is there a trigger command to delete a location? Or is that accomplished by telling it to resize and move the location back to 0,0?


Okay, but please understand I am very unfamiliar with triggering. Can triggers create locations dynamically or does each individual location need to be predefined? Can I make a trigger that centers a new, unique location over each CC any player builds?

1. “If player builds CC, center a 2x2 location on it” – So with this it doesn’t matter how many CCs are built (up to 255), each one would have a 2x2 location over it.

2. “If player builds CC, center location A1 on it” – With this, each time a new CC is built, the same location would be moved, preventing the possibility of any sustained effects on more than one CC.

If you stop using it, that means no actions or conditions use it, so the location effects nothing at all ever.

There is no trigger for deleting them, because you are meant to just not use it when you dont need it. But when creating a map in a map editor, if you dont "create" the location, its still there just at (0,0) with width and height of 0, so that could be considered "deleted".




You can predefine the locations, or change their settings whenever you want, its up to you. And your example is possible, its just really hard, and the only way it could be accomplished would be looping through the CC's everytime you check for a new one. The reason that is bad is that to loop through them you have to give the each CC to another owner once its checked, then when all CC's are checked give them all back to their origional owners.

Can locations detect the death of a unit? Going back to the CC example, if I center a location over it but want it to go away if the CC is destroyed, is that possible? Otherwise, if I have triggers that utilize the location with the intention of only having it usable while a CC is present, there would be problems. I suppose the trigger could perhaps check to see if a CC is within the location first, but it seems so messy having unused locations scattered everywhere.


Okay, so locations are predefined. Darn, that definately, at the very least, makes things more challenging, if not outright eliminates some possibilities. Shame there wasn't a way for the program to create location 'groups' that triggers could refer to and thus enable dynamic location creation. (So you might have a custom CC Group that reserves locations 200-255 and creates up to 55 locations for each CC made in the game. Triggers would then refer to Location "CC Group" and the program would apply the trigger conditions to all locations within the CC Group.)

As for your solution, it's a very interesting idea. What would happen to any in-progress units/research during ownership change? How quickly would the game be able to run through the whole process, and thus how noticable would it be to players? Would it botch the AI?

Once again all this does is lets you move, resize, and change the height flags of any location at any time during a game. Anything outside of those is a mapping question, and I'm not an advance mapper.

That's just me acknowledging what you said. Not sure why you repeated your quote beneath it.


Sorry, I'm not trying to monopolize your time with personally-specific questions. Since you suggested a way for one of my examples to work, I was just curious whether you knew anything further about it offhand.

Because the bolded text states that no they are not only predefined. I take "predefined" to mean you set their width height and flags, then they are defined and you can only center them and use them in triggers.

No problem, im just tired.

Out of context, you can infer more meaning behind "predefined", but in this specific case my question pertained to "dynamic creation" vs "predefined creation." As in, the difference between algorithmic and manual settings.

You can have algorithmic settings, thats why parameters are taken from death counters.

How so? (pardon my ignorance)