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.

Sign up for GitHub

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

Jump to bottom

State should not be kept in ScriptableObject #1

Open
bgk- opened this issue Aug 4, 2024 · 0 comments
Open

State should not be kept in ScriptableObject #1

bgk- opened this issue Aug 4, 2024 · 0 comments

Comments

@bgk-
Copy link
Contributor

bgk- commented Aug 4, 2024

This system was a fun learning experiment, but can't say I really recommend it.

A major issue with this system is that currently, state is kept on the ScriptableObjects (isOpen), which should be avoided. It's better to keep ScriptableObjects as data containers only without any state.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bgk-