This HTML5 document contains 18 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Subject Item

n17:

n18:wikiPageDisambiguates

n2:

Subject Item

n2:

rdf:type

n24:

rdfs:label

Bloomfield Space Center design document/Sid dialogue

rdfs:comment

This is a draft of dialogue for the character Sid which was included in the Bloomfield Space Center design document for Van Buren, the canceled Fallout 3 by Black Isle Studios. __TOC__ Example Dialogue Name: 02 Porter Example Creature Name: 02Porter 'ere's probably the most-commonly-used check script: GetTotalSkill (PCSpeaker(),SKILL) You might want to set up an autocorrect option in word so you don'have to type out the whole thing (I have mine set up so if I type gett it spits out the above check with an ==1 at the end of it).

dcterms:subject

n13:

n6:wikiPageUsesTemplate

n7: n8: n14: n16: n19:

n23:

15

n22:

2005-10-01

n10:

n11:

n20:

n21:

n9:

.doc file

n15:

71

n4:

n5:

n18:abstract

This is a draft of dialogue for the character Sid which was included in the Bloomfield Space Center design document for Van Buren, the canceled Fallout 3 by Black Isle Studios. __TOC__ Example Dialogue Name: 02 Porter Example Creature Name: 02Porter 'ere's probably the most-commonly-used check script: GetTotalSkill (PCSpeaker(),SKILL) You might want to set up an autocorrect option in word so you don'have to type out the whole thing (I have mine set up so if I type gett it spits out the above check with an ==1 at the end of it). Try using "Avellone-style" node numbering. That's w'ere you give the node a "number" that's actually a unique word, such as TELLABOUTSELF: for a node w'ere the PC has asked an NPC to tell about himself. Just refer to that word with your Goto statements (like Goto TELLABOUTSELF: ) an' when you're all done with the dialogue you can do a global replace for that word with a real number. Doing this means that you can group nodes by topic in the dialogue file an' not have to worry about renumbering if you have to insert another node later. If you use this method, be sure to make the word something that is unique an' won't accidentally be used in other parts of the dialogue; ASSHOLEINSULT is a good word, just ASSHOLE isn't because if a node has a character actually saying "asshole" the global search would catch that, too. You can also use a colon character at the end of the unique word like I did in the TELLABOUTSELF: example, above. Whatever you do, don'use a number all by itself as a placeholder like this … I learned the hard way that some numbers pop up everyw'ere an' doing a global replace on them totally screws up your dialogue! For an example of this method, check out the Avellone_Dialogue_Example_Ordor.doc file in Tools/Design/Documents on sourcesafe (the same place you find this dialogue template file).