![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
A Visit from Murray
Nov. 7th, 2004 11:04 pmSo, Murray came over today and we spent most of the day either talking about The Project, or reminiscing about Buffy and games past.
The Project otherwise known as CAST, or computer-aided story-telling may end up getting it's own web site soon.
I have been stealling ideas from LJ here, and want to concentrate on what we call "the documentation engine" which will record prose descriptions and histories, and textual description of events, places, and persons. Other parts are the "plot engine" (though this might just as easily be called an "event engine") and the "resolution engine"
So far, I believe we have decided that we are going to attempt to do a sort of controlled wiki, one where anyone can edit but all edits are stored as differences (a la CVS) along with the user who edited them, preferably with a histoy and automatic merge option similar to that implemented in J-Buider. By default, in the event of edit contention a merge wil be attempted.
We had quite a discussion over whether any tems would have controlled access, and in the end we decided that by default an item wil be public, though we will seperately track which characters know which information, and users will have the option to either have all text not known by a character hidden from them when logged in as that character, or all text visible, but with text not known by a character marked with a warning to that effect.
However, storytellers may wish to keep future events and text not known to any player secret until they occur or are discovered, and there may be text and info about characters that players wish to keep secret, so there will be the option to mark an item secret. When marked secret the creator of the item will be able to give the item the equivalent of LJ "friends" and these friends wil then have access to the item, and can (because secrets can be spread) give other people access to the item. At some point the original creator of the (or an admin) can decide that an item is no longer secret
There was more, but we'll get to it!
Head's still hurting from the discussion! Great fun though, haven't brainstormed in too long.
Nice tomato and mozzarella panini for lunch and a pretty good chicken tikka masali with pilau, and a Kingfsher, for dinner.
And saw Tibet...
The Project otherwise known as CAST, or computer-aided story-telling may end up getting it's own web site soon.
I have been stealling ideas from LJ here, and want to concentrate on what we call "the documentation engine" which will record prose descriptions and histories, and textual description of events, places, and persons. Other parts are the "plot engine" (though this might just as easily be called an "event engine") and the "resolution engine"
So far, I believe we have decided that we are going to attempt to do a sort of controlled wiki, one where anyone can edit but all edits are stored as differences (a la CVS) along with the user who edited them, preferably with a histoy and automatic merge option similar to that implemented in J-Buider. By default, in the event of edit contention a merge wil be attempted.
We had quite a discussion over whether any tems would have controlled access, and in the end we decided that by default an item wil be public, though we will seperately track which characters know which information, and users will have the option to either have all text not known by a character hidden from them when logged in as that character, or all text visible, but with text not known by a character marked with a warning to that effect.
However, storytellers may wish to keep future events and text not known to any player secret until they occur or are discovered, and there may be text and info about characters that players wish to keep secret, so there will be the option to mark an item secret. When marked secret the creator of the item will be able to give the item the equivalent of LJ "friends" and these friends wil then have access to the item, and can (because secrets can be spread) give other people access to the item. At some point the original creator of the (or an admin) can decide that an item is no longer secret
There was more, but we'll get to it!
Head's still hurting from the discussion! Great fun though, haven't brainstormed in too long.
Nice tomato and mozzarella panini for lunch and a pretty good chicken tikka masali with pilau, and a Kingfsher, for dinner.
And saw Tibet...
