I’m trying to think if there’s a real world use case where you’d use say BlueprintReadWrite and not EditAnywhere (or vice versa).
I also wanted to say that I think this lecture was done very well, the graph he showed really helped demonstrate the distinction between the various types.
Thanks!
Jason
When you don’t want to give blueprint access. For example; just because I want designers to be able to set the starting health doesn’t mean I want them to develop code around it which could introduce bugs as the C++ didn’t expect it to be modified externally.
Ah, that makes sense! I keep thinking in the narrow scope of a sole developer and not necessarily as being part of a team where you might have a separation of responsibilities between developer and designers.
Thank you for the insight!
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.