You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: