[Solved] Warning: Entity reported ENTITY_CHANGE_NONE but property changed

Dragokas · **Author**

Hi,
do you know what could causing this and how to reproduce, under what circumstances?

Code:

Entity 315 (class 'infected') reported ENTITY_CHANGE_NONE but 'm_nWaterLevel' changed.
Entity 262 (class 'infected') reported ENTITY_CHANGE_NONE but 'm_clientLookatTarget' changed.

BHaType · *Last edited by BHaType; 05-15-2022 at 20:23.*

Quote:

Originally Posted by Dragokas

Code:

Entity 315 (class 'infected') reported ENTITY_CHANGE_NONE but 'm_nWaterLevel' changed.
Entity 262 (class 'infected') reported ENTITY_CHANGE_NONE but 'm_clientLookatTarget' changed.

Usually you see this warning when you use SetEntData for netprops and forgot to call ChangeEdictState

Dragokas

Ok, I know, but under which circumstances entities require a call to ChangeEdictState?
Usually, you just call SetEntProp and forget.

BHaType · *Last edited by BHaType; 05-16-2022 at 07:08.*

ChangeEdictState need to be used only with SetEntData or anything else that can change prop value like StoreToAddress. ChangeEdictState marks entire edict or some prop to be replicated to clients so it should be only used for networked props.

The reason why no one calls it along with SetEntProp is because SetEntProp marks prop as changed for you
click

Prop_Send - networked props that are replicated to client
Prop_Data - server sided props that client have no idea about

Dragokas

Understand. Thank you.