i've been wondering about something.
i sometimes have a problem with my anywhere location being named location 63, im wondering what would happen if i already had an existing location 63?

Anywhere IS location 63. You can't create another location that is location 63.

In SCMDraft, you can have multiple locations named the same thing. They are indeed seperate locations still, and if you were to make a trigger and to look for "Location 63", (or whatever name for that matter), you would see two "Location 63"s in the list.

orly?
edit: thought you were saying you could act on two locations simultaneously

No No No...

I just meant that you'd see two of them in the list. To have them both be acted upon, you need 2 actions to do it.
I find it as a rather useful way to ward away people from edting my maps by naming all of the locations "Z".

doesn't help against unprotectors though. They have a feature to revert locations back to their default names "Location 0-255".

then dont protect the map
use a blank comment on every trigger
rename all locations to Z

o.o

You can still unprotect. Or just protect it so you can then use the unprotector function.

Never noticed that feature before on an unprotector--would be useful to save some strings if it let you rename switches as you can't seem to rename those in Scm Draft II...at least not back to there original names.

Or ideally don't be a fag and don't "protect" your maps

You really didn't read the post he was responding to, did you?

What to force a map to have default location names? Yes indeed I did.

He said that as a way to save locations though, not as a way to protect a map. That way, while you are making the map you can call the locations what you want, and when all the triggers involving locations/switches are finished and if you need more strings, you can protect and then unprotect and it will give you back those strings. Then you finish the map with the required strings added.