I want to create a unit with proporties in scmdraft2 via the visual trigger editor. I've only used 6 of the CWUP slots [sic?], and the properties I set are saved, and are still there when I pull the map back of later, but the map basically just does it like "create unit". Specifically, I need to make a unit spawn with half hp, and no - creating it then making another trigger that modifies hp of units at location isn't an option. What's going on?

Using another editor will make the map unstable.

Posting your map/triggers would help, you know...

Are you sure you don't have another trigger for "set unit hitpoints" somewhere?

You also should just use the text editor and Ctrl+F.

I know the map, there isn't. And if you knew about the text trigger for create unit /w properties, then you'd know the parameter it uses for the unit's properties cant be interpreted just by looking at it even if I did post it. If you've never even heard of this problem I don't think you can help.

There's several possible reasons:
- You've already used all CUWP slots.
- Another trigger sets the hp immediately after it's been created. Try other properties to make sure.
- Another trigger counteracts your first. For example by removing/recreating the unit. Delete all other triggers to make sure.
- The trigger isn't even running, but another in its stead. Add a unique action to that trigger to make sure.
- You are hosting the wrong map.
- You are not saving your changes.

EDIT:
Maybe it's because of TinyMap2?

1.) ensure the CUWP slot is correct by changing it to make it invincible as well.
2.) do it with text trigedit.

See that tab called "Unit Properties" in TrigEdit? Yeah, you CLICK ON THAT.

ah, cool. Where can I manually edit the cuwp slots?
well I don't understand how the parameters work with cuwp. All I really know so far is 4 = invincible.... most of the time.

Well there's your problem. You have 64 CUWP slots. The number you see refers to that particular slot. You can also use uberation to edit slots. Just fyi, this is the same way strings are referenced in other things like trigger duplicator (the string is located in the string section, then called back by a number in the actual trigger.

Wow that was eye opening. I should be able to beat this now.

Crap! I never knew about that either. Jeeze, that would've saved me a lot of time. Now I'll need to go through and check that my CUWP slots are as efficient as possible. I'm sure they are (after my tedious manual checks), but this'll help confirm it.