modifying .ARE files - region/trigger naming

[subtledoctor]

Can travel triggers in different .ARE files have the same name? Or should they be globally unique?

I notice that, for instance, in the Forest of Wyrms in SoD, the spider cave has an exit trigger named "TranBD7200" while the dragon cave has an exit trigger named "Tran_BD7200." This makes me thing they must be unique?

Corollary: Can I assume from those two names that the name can be more than 8 characters?

[lynx]

No need to be unique; that would only cause problems if it was the same area and you wanted to work with them with scripts/opcodes that can target by name. Which can be 32 chars long as with other names.

[jmerry]

The name field for triggers, containers, actors, and basically all of the ARE substructures is a 32-byte text field (Not necessarily the same thing as 32 characters, if you go into the Unicode weeds). Plenty of room there. No global uniqueness required on anything, and no real way to check that. Local uniqueness is recommended, mostly for the sake of scripts interacting with those objects. If you want to activate or deactivate a region or spawn point or whatever by script, you want it to be the only one with that name in the region.

[subtledoctor]

Cool, thanks. Weird that Beamdog gave those two travel triggers on different maps unique names - I guess I read too much into it. I went with unique names anyway - easy with 32 bytes to use - and everything is working.