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

Settle on an opinionated data model for rooms #5

Open
aeturnum opened this issue Dec 21, 2020 · 0 comments
Open

Settle on an opinionated data model for rooms #5

aeturnum opened this issue Dec 21, 2020 · 0 comments

Comments

@aeturnum
Copy link
Owner

aeturnum commented Dec 21, 2020

Right now I've been adding state to rooms over time as needed for the little demos I'm putting together. At some point, a more holistic and opinionated model for what data a room should have needs to be written.

Rooms are turing complete - they can save arbitrary data into the scene / adventure / room object, so all behavior is possible now, but what are the common features that rooms would want to know? Should designers always have paths available? Always have room counts available? Should we track how often the player has returned to this room? Do we want to make navigation information (sounds recorded, numbers pressed, etc) to a room? Etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant