Resolved [1.0.8] Ghost relevancy trigger change filter

Every time when client out and in range of ghost relevancy, every ghost components will retrigger change filter when the ghost entity respawn at client even actually no data changes at those ghost components. I know it's by design of default ecs behavior but at dots netcode I think this behavior should change for ghost relevancy to make it not retrigger change filter when out and in ghost relevancy range and no ghost component data changes.

And also at client when ghost entity is out of range of ghost relevancy and ghost component of the ghost entity changed data then go in range of ghost relevancy again should also not trigger change filter too. I think these two behaviors should be the correct behavior which I think it's bug. Maybe it's good to have 2 ghost component attribute tags to customize these 2 behaviors but I can't think of any concerre use cases that need to keep these 2 behaviors.

 

On the other hand, I disagree. Leaving relevancy results in the entity getting destroyed and re-entering results in a new entity getting spawned.

That should trigger a change filter (or at least an order change filter) since I have a lot of client-side only systems that generate relevant presentation data acting only on chunk changed.

If relevancy does not trigger changed, then the non-synchronized data will not get properly regenerated when the newly relevant entity gets created.

 

I think I really need official to implement ghost component attribute tag called something like SkipRelevancyChangeFilter = true to handle my use case super easy that just solve it with this attribute tag and get best performance since special workaround implementation. Currently I have ghost component to store damage hit by enemy and trigger change filter show at UI but by current netcode design it will keep retrigger UI update even there's no damage hit. Seems like it's really hard to solve this simple problem that I need to implement long u turn ugly workround solution just to make it work and also the solution will bad for performance.

 

Actually I just realized that I need more granularity by specify the "component" behaviour itself (using the GhostComponent attribute) that I need to support both trigger change filter and not trigger change filter use case.
1) When character has top head bar, out and in relevancy should trigger change filter to refresh top head bar value if not will just get zero value which is wrong.
2) When character hit another enemy character will pop up damage UI value but since this ghost component is at character, out and in relevancy will trigger change filter and then pop up damage UI value which is not expected behavior. It should only pop up damage UI value when character damage enemy character.