Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Serialization strategy? #104

Open
piedoom opened this issue Aug 18, 2024 · 2 comments
Open

Serialization strategy? #104

piedoom opened this issue Aug 18, 2024 · 2 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@piedoom
Copy link
Contributor

piedoom commented Aug 18, 2024

I'm wondering if it's possible/within the scope of this crate to allow serialization (specifically of the data in a ThinkerBuilder). I can see it being useful to persist AI to a save, or prototype quickly by adjusting values. I can think of a few alternatives (mainly writing my own intermediate struct to serialize/deserialize the ThinkerBuilder to) but this seems like the neatest option

@zkat zkat added enhancement New feature or request help wanted Extra attention is needed labels Aug 18, 2024
@zkat
Copy link
Owner

zkat commented Aug 18, 2024

While Thinkers &co are fundamentally stateless, the really good reason for having serializable builders is so you can build up your AI logic using external tools/node-based graphical builders, or even bevy's upcoming scene editor.

I think things are in too much flux to make any real guarantees, but I think it makes sense for this library to have explicit compatibility with bevy's scene definition format once it's ready.

@piedoom
Copy link
Contributor Author

piedoom commented Aug 18, 2024

Makes sense, thanks for the response! I'll rely on some bespoke solutions til Bevy's new scene stuff gets finalized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants