You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example the SphereWaterInteraction has the private _maxSpeed property. I need to change that depending on the boat speed.
I do it now by hacking into it with reflections.
I see no reason, why a lot of properties are private.
The text was updated successfully, but these errors were encountered:
Hi there, generally the reason is the standard thing of making modular code with minimised surface area/connections to other code. The more code we can keep private the more easily we can change it later.
But I agree the example you gave can be made public without making a significant issue. I can make nearby similar properties public too if they also look fine.
For example the SphereWaterInteraction has the private _maxSpeed property. I need to change that depending on the boat speed.
I do it now by hacking into it with reflections.
I see no reason, why a lot of properties are private.
The text was updated successfully, but these errors were encountered: