I've just started using Quest, and I'm running through the tutorial game. All is going smoothly, except that after the first couple of verbs I created, every one of them comes up blank! This is very frustrating, considering the fact that the "Value" section for each verb has the appropriate text in it, yet the field to edit it is blank and running through the game and accessing the appropriate commands brings up a blank response. I would be most appreciative for any advice that can be offered.

Please attach your game flle so we can see what's going on.

https://dl.dropboxusercontent.com/u/594 ... Storm.aslx

All right, there it is. The problem with the blank verbs seemed to fix itself, but now I'm having some trouble with the Ask/Tell functions (even though all the code matches up), and whenever I use a custom command, it shows the appropriate text, but it appends "I don't understand your command." My last issue thus far is that when I try to add a verb for changing the TV's channel, it comes up with an error message:

System.NullReferenceException: Object reference not set to an instance of an object.
at TextAdventures.Quest.EditorControls.WFVerbsControl.AddVerb(String selectedPattern, String selectedAttribute)
at TextAdventures.Quest.EditorControls.WFVerbsControl.Add()
at TextAdventures.Quest.EditorControls.WFAttributesControl.cmdAdd_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

I ran into this problem myself once - it's the period in "Mr. Halifax". Quest uses the period to separate commands. So when you select Mr. Halifix and then "Look at", it causes this:

look at Mr. Halifax

Quest turns this into two commands: "look at Mr" and "Halifax".

"look at Mr" matches "Mr. Halifax", so that works. But "Halifax" isn't a valid command, so you get "I don't understand..."

Bottom line: remove the period from the name (e.g. make it "Mr Halifax") and it will work better.

Many thanks! I changed the owner's alias to Mister Halifax, and tried just typing in "halifax" for the command. It works just fine. I also figured out why the error pops up when you use the defibrillator. Turns out my blind self forgot to change the set flag option to "object" instead of "expression".

I also managed to trick the system by creating the "change channel" verb to "switch channel", then changing it to include "change channel".

I really appreciate the help!