Though it warns me that I've maxed out creating units with properties, it still lets me create some more (although it tells me that I can't create anymore until I've deleted the old).
How do I get pass that problem? I mean... I'm sure I'll be creating more than 128 (or whatever the max is) units with properties...
Though I have some ideas of how to get around the problem, I was wondering if there was an easier way.
My solution is:
For example, I need create units with attributes in location1. So what i'll do is whenever I need to create a creature there, I'll have it created without properties at location2, then:
When Current Player brings at least 1 of Zerg Zergling to location2
Create 1 Zerg Zergling for Current Player at location1;
Remove 1 Zerg Zergling owned by Current Player at Location2.
Then if need, do it on increments of 3's or something to make sure it all happens fast enough
to create more units with properties, just make it so at the beginning of the game, a trigger creates a unit and modifies its properties where it spawns. Will that fix the problem? Your post was confusing at times...
*goes back to working on complex defense*
A little simpler form of what was said above: Create the unit using a normal CREATE UNIT action, then use triggers to modify its properties. Almost all unit properties can be set independently through trigger actions.
Create unit with properties only maxes out in Staredit. You can actually use the same CUP slot for multiple units. Ex: Create hallucinated marine, create hallucinated firebat; These would use up ONE slot. The problem with Staredit is that it creates a slot for every unit, so instead of recycling and using only one, it will use two.
You can use SCMD to change which CUWP slot the unit is using, then use Uberation to change the individual CUWP slots.
When it says you have maxed them it will disable properties for anymore you make. If you click the "Properties" thing it will be all greyed out.