Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You can certainly use a scripting language to handle dialogue. Basically a script might look like this:</p> <pre><code>ShowMessage("Hello " + hero.name + ", how can I help you?") choices = { "Open the door for me", "Tell me about yourself", "Nevermind" } chosen = ShowChoices(choices) if chosen == 0 if hero.inventory["gold key"] &gt; 0 ShowMessage("You have the key! I'll open the door for you!") isGateOpen = true else ShowMessage("I'm sorry, but you need the gold key") end if else if chosen == 1 if isGateOpen ShowMessage("I'm the gate keeper, and the gate is open") else ShowMessage("I'm the gate keeper and you need gold key to pass") end if else ShowMessage("Okay, tell me if you need anything") end if </code></pre> <p>This is fine for most games. The scripting language can be simple and you can write more complicated logical branches. Your engine will have some representation of the world that is exposed to the scripting language. In this example, this means the name of the hero and the items in the inventory, but you could expose anything you like. You also define functions that could be called by scripts to do things like show a message or play some sound effect. You need to keep track of some global data that is shared between scripts, such as whether a door is open or a quest is done (perhaps as part of the map and quest classes).</p> <p>In some games however, scripting could get tedious, especially if the dialogue is more dynamic and depends on many conditions (say, character mood and stats, npc knowledge, weather, items, etc.) Here it is possible to store your dialogue tree in some format that allows easily specifying preconditions and outcomes. I don't know if this is the way to do it, but I've once asked a <a href="https://stackoverflow.com/questions/372915/game-logic-in-xml-files">question about storing game logic in XML files</a>. I've found this approach to be effective for my game (in which dialogue is heavily dependent on many factors). In particular, in the future I could easily make a simple dialogue editor that doesn't require much scripting and allow you to simply define dialogue and branches with a graphical user interface.</p>
    singulars
    1. This table or related slice is empty.
    1. PORPG dialogue engine / structure
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USFiras Assaad
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThis is a great and very useful comment, along with the link you posted. I've thought about doing this in XML and the example you gave seems quite logical. I guess this could also be done in json? Also, you give a great idea about having a GUI to simply define dialogue and branches
      singulars
      1. PO
      1. USmac_55
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload