-
Notifications
You must be signed in to change notification settings - Fork 4
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
IE-0010: Concepts #10
Conversation
Hi, |
Just copying these comments from #12 across:
|
This does affect any existing source code that uses non-thing objects (without The current state of affairs, where "visible" means "every, in or out of scope, in or out of play" and "touchable" means in scope plus one of: a room, a region, or an actually touchable thing, is highly confusing and a routine problem point for new users. Adding another exception to track, that I think a better choice would be to leave And I take it Edited to add: never mind the reference to |
If a story has a dialogue section, both the dialogue and concepts language elements are automatically activated. Would it be possible to automatically activate concepts if a story (that doesn't have a dialogue section) creates a concept? Or was this deliberately avoided so as not to conflict with any stories that might have created their own "concept" kind? It seems like the only way to activate it otherwise is with project_metadata.json, which is somewhat cumbersome (though I'd assume it'll be just a click-a-checkbox affair for IDE users, and if it would be a fuss to implement auto-activation, I think CLI users can cope with maintaining a project_metadata.json file). |
Summary
A new top-level kind of object,
concept
, useful for representing abstract concepts like "forgiveness" or "Italian cookery" which have no physical existence in the world model.