Keeping configuration variables inside Actor Blueprint vs Data Asset

I was exploring the new Lyra project and I stumbled upon weapon blueprints inside the project. In Lyra, the weapon configuration (Damage, Range, etc…) is stored inside the weapon blueprint itself.
It seemed a little bit sub-optimal to me because I personally think the configuration variables should go into Data Assets. Having them in a separate file will help with source control. It’s also easier to find them.

What has been your experience with this topic? What are pros and cons of storing configurations inside actor’s blueprint?

1 Like