If you relaxed the wiki's password requirement, then playtesters could post questions and suggestions inline within the text. They could post suggesions for new and modified Oracle entries. And since the wiki has a revision history, there is no risk (just minor annoyance) of you losing your work from a wiki troll or defacer.
This is great.
Like Larry, I'd like the category to be included the way it is on Clinton's, but I love the ability to add specific types of things. And, of course, the ability to use it away from the web.
Will you post a text file of the new entries, for use in the "player at top of the We Owe list selects element" part of chapter creation?
Part of me thinks that the full list ought to keep some mystery -- it's cool to be *surprised* by stuff from the story roll -- but given the free-choice part, I guess we have to have a list to look over.
Well, obviously not "have to". It's totally awesome that you're posting this stuff for free, and you don't have to do anything.
In my ideal world, the list is constantly changing and unpredictable, and the list you're choosing from isn't identical to the list you're rolling on, and whenever something cool comes up in play or you end a chapter on a cliffhanger you add it to both the list you roll on and the list you choose from, and all like that.
In one way, the most practical solution would be to put the oracle on cards and include a bunch of blanks. In other ways - important ways involving money - that's the LEAST practical solution.
I wish I were a better programmer. I'd make something AWESOME.
And the answer is, yeah, probably sooner or later I'll get around to putting up the whole current list. It's a pretty low priority.
The ideal Oracle program ought to read elements from some arbitrary number of XML resource files -- a default one that comes with the Oracle, plus one created from play in your game, plus any number of "expansion packs" downloaded from the net. You'd want to be able to consciously subscribe to "Clinton's elements" but not "J's elements", because your set will affect the tone of your game, and you don't want modern urban stuff mixing in with your Arabian Nights style game.
Separating the element list from the executable also means you can have distinct Mac and PC executables that use the same resources.
While we're at it, it would rock to integrate the Story Games random name lists.
I am going to convert what Vincent has - which, by the way, I can't see the interface, so I will make my own - into a Java program (or maybe another language if I feel like it) that takes XML files, so you can make your own. It will be awesome.
Ok, if anyone's still reading this thread, you are a member of the hardcore. I have questions - and Vincent, if you want, tell me to do my polling somewhere else.
In the original source text for these adventure elements, you had a sort of two-container system to hold them in.
type of element (event, person, location, threat) -> arena (rural, urban, magical, military, etc) -> element
In Vincent's new tool, oracle.exe, there's none of this. There are, basically, tags on each element, like so:
"The arrival of honored emissaries from a wealthy, exotic land." --tagged with--> "event group"
In making his tool cross-platform, I'm expanding it to take outside files, so anyone can use this for their own list, if they want. What I'm trying to determine is what people find useful out of the above. Specifically:
(1) Is the arena interesting or necessary? My thought is yes, especially for other projects. It basically lets one file hold many sub-files. My file contains, for example, TSOY adventure seeds, and my arenas could be "Khale" and "Ammeni", allowing people to choose to restrict their adventure elements to one of these.
(2) Are the tags a better way to go? At first, I thought so, but in actually trying to write the XML out, I discovered I liked the constraint of having to pick even more. It's still pretty up in the air, though.
One thing to notice about the arenas is that they aren't really containers for the types. On the original charts, I happened to group the elements by arena then by type; I might just as well have grouped them by type then arena.
- Military characters
- Wilderness characters