Aevyrie

This appears to be broken on `main` again. I've tried a cargo clean and running in release with no luck.

I've put up a PR. My approach there is to provide a simple typed value store in a bevy resource, using `Reflect`. Users of preferences don't need to know anything...

If you want to have multiple instances of a type inside your plugin's namespace, you can, but there should be a single canonical version of your preferences struct for your...

That seems like an implementation detail of a storage backend. There's no reason you can't load preferences into the resource on - or even before - the app starts. Edit:...

Re: https://github.com/bevyengine/bevy/pull/13312#issuecomment-2104132447 I think all of that is worth discussing, but I'd like to table that and keep it out of scope for this initial PR. I think that what...

> I think that this PR is punting on too many things and isn't opinionated enough. The problem with "leaving things up to the developer" is that it risks each...

Yup, I totally agree. 🙂 There is a very clear need for a preferences-like-thing, and the best way to get it moving is to post a prototype so people can...

> Let me offer an alternative proposal for a preferences API: > > * Each preference item is a `Resource`. Something to note that I wasn't aware of until cart...

> Also sadly I think we are absolutely in RFC territory now. No worries, I'm glad we started this discussion. :) I don't have the time to do this justice,...

A simple starting point might be to use a conservative bounding sphere of the longest bone chain to generate an AABB: https://gamedev.stackexchange.com/questions/43986/calculate-an-aabb-for-bone-animated-model