| Description | We've talked about this on the forums a lot, and it's definitely vital behavior. That said, I don't think it's been tracked yet, and it appears not to work currently.
When an item is duplicated or prefabbed, the entity names and links need to be smartly incremented. For a simple example, open torchtest.map (in the repository).
light_candleflame_moving_2 binds to candle_1
However, if you duplicate (or prefab) the item,
light_candleflame_moving_2 and light_candleflame_moving_3 now BOTH bind to candle_1
and it no longer would work correctly. The mapper would manually have to update the bind to match the new base (see also a duplication selection bug to be entered shortly, which plays a small role in this).
Considerations that come to mind are:
-incrementing properly so as to not clobber existing items (if light_11 is to be duplicated, but light_12 already exists, light_13 must be the duplicate name)
-the 'bind' property (source and destination names both)
-more?
Important note: This may be important for more than just "bind", I don't know. For example, I imagine this would also be needed for path nodes (or any logical link). |
|---|
