5.2. multi_manager expansion
This behavior makes it possible to add more than 16 targets to a multi_manager. It also enables support for target patterns, and it cooperates with the multi-target pattern by merging them into its own list of targets.
It works by automatically generating additional multi_managers and distributing the extra targets across them. Because the target with the highest delay is added to the 'main' multi_manager, the resulting entity setup has the same single-threaded behavior as a single multi_manager - that is, it can only be triggered again after it has triggered its last target.
Configuration
The following globals (defined in mess.config) can be used to control this behavior:
| global | effect |
|---|---|
MTL_MULTIMANAGER_MAX_TARGETS = 16 | Amulti_manager will be split up when it contains more than this number of targets. |
MTL_IGNORE_TARGET_PREDICATE = name => name.match('^(?:_tb_)') | AnMScript function that is called for every property. If it returns true, then the property will be omitted. For example, the function name => name.match('^(?:_tb_)') returns true if the given name starts with _tb_, which causes TrenchBroom-specific properties to be ignored. |