Adding an Actor Component that contains a TMap property to a Blueprint results in unexpected behavior when default elements of the TMap are modified in an instance of the Blueprint in the level:
It would appear that all of these are related, so they were collected in a single ticket. These issues only seem to occur when the TMap property is added to the Actor Component class. The issues were not observed when a TMap property was added directly to an Actor class.
In the first instance above, all default elements are removed from the TMap. In the second instance, every non-modified default element is removed from the TMap. In the third instance, the newly added element is removed from the TMap.
In the first two instances, any unmodified default elements remain in the TMap, and in the third instance the new element can be given the name of one of the default elements that was removed.
Head over to the existingAnswerHub thread and let us know what's up.