COND_InitialOnly properties can be resent when an actor becomes relevant to a client again. However, if the property is push based and it was never replicated the first time the actor was created on the client, the initial only property will not be replicated when the actor becomes relevant again, even if the value has changed.
If the property is not using push model or if it does get replicated the first time, then the property's latest value will be replicated as expected when the actor becomes relevant again.

Steps to Reproduce

Create a replicated actor with a push based, COND_InitialOnly replicated property.
When the actor is first spawned on the server, don't change this property from the default value.
After the initial replication, change the property (marking it as dirty) and have the actor become irrelevant to the client.
Once the actor has been destroyed on the client, have the actor become relevant again.

Expected: the actor will be recreated on the client, with the initial only property having the updated value from the server
Actual: the actor will be recreated on the client, but the property will still have the default value

See linked UDN for more info.

Have Comments or More Details?

There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-156251 in the post.

Login to Vote

ComponentUE - Networking
Affects Versions5.0
Target Fix5.1
Fix Commit20897795
Main Commit20901776
CreatedJun 9, 2022
ResolvedJul 5, 2022
UpdatedJul 11, 2022
View Jira Issue