Idiomatic way to store config values | Bevy | Page 1

wicked sentinel Aug 31, 2023, 5:31 PM

#

I have a third person camera controller component that holds pitch, yaw and distance values. I also need to hold config values like max/min yaw and rotation speed etc. What's the idiomatic way to store that? In the same component or in a separate config component?

quiet geyser Aug 31, 2023, 5:35 PM

#

Seperate config component is better, so then change detection can differentiate

#

Being able to check "did the config change" is a reasonable question, and so is "did the camera position change"

wicked sentinel Aug 31, 2023, 5:37 PM

#

Ok, thanks. I do have a config component now but my queries go very long so it got me wondering

quiet geyser Aug 31, 2023, 5:38 PM

#

The WorldQuery and SystemParam derive macros can be really handy 🙂

wicked sentinel Aug 31, 2023, 5:39 PM

#

Another similar question; Should the camera controller components be on the same player entity where the mesh etc is? Or in their own entity?

quiet geyser Aug 31, 2023, 5:40 PM

#

I tend to like having them on the same player entity

#

Just to avoid accidental desyncs

#Idiomatic way to store config values